How to Apply Cross-Arrangement Coupling Analysis

Status: Methodological guide. Captures the analytical pattern developed across to sessions in operationalizable form for future analyses.

Purpose: Cross-arrangement coupling is a paper-grade analytical move that didn't exist in operationalized form before this session arc. This document explains what it is, when to use it, how to author the data, how to render the analysis, and how to interpret the results. It is intentionally instructional rather than findings-focused — those live in methodology-coupling.md, cross-landscape-coupling.md, and the checkpoint.

1. The pattern in one sentence

Every system, methodology, or artifact has TWO structurally coordinated positions — one in its primary arrangement (analytical structure) and one in the cognition arrangement (cultural artifact in collective use). Pairing them and rendering them together on a coupling plane reveals the depth-vs-reach trade-off, the layering-trap pattern, and the arrangement's primary depth-cost mechanism.

2. When to use it

Use cross-arrangement coupling analysis when:

• You have multiple instances of something (≥5 ideally, ≥10 better) all in the same primary arrangement.
• Each instance has a cultural existence outside its analytical role — adoption, training, citations, deployment count, user community, etc.
• You want to ask: what's the relationship between analytical depth and cultural reach across this set?
• Or: why do some instances dominate adoption while others remain niche?
• Or: what mechanism penalizes depth in this arrangement — uniform cognitive cost, architectural walls, or something else?

Don't use it when:

• You have only one instance (no comparison).
• The "instances" don't have meaningful cultural-artifact existence (e.g., individual chemical reactions don't usually have cultural-ecosystem positions).
• You want a Sc=4 single-event analysis (use cross-arrangement coupling at Sc=4 instead — different schema shape).

3. The schema convention

Each instance becomes a PAIR of manifestations:

data/manifestations/<instance-name>.v1.json                      ← primary arrangement
data/manifestations/<instance-name>-cultural-artifact.v1.json    ← cognition arrangement

The primary-arrangement Mn uses arrangement_ref: data/arrangements/<primary>.v1.json and positions the instance across the primary arrangement's chain levels. Per-chain-level positions, primitive-by-primitive levels, evidence per chain level. Standard manifestation.v1 shape.

The cultural-artifact Mn uses arrangement_ref: data/arrangements/cognition.v1.json and positions the instance in TWO chain levels:

• cultural-ecosystem (Pr/Ex/Tr/Dv/Cd/Gv/Te/Sc/Ct) — adoption / production / transmission / specialization / coordination / governance / territorial spread / inter-generational succession / connectivity
• cognitive-architecture (Kw/Sk/Dc/Pl/Co/Jd/Cr/Si/Id) — cognitive demand the instance imposes on its user

Each cultural-artifact Mn declares an ls (landscape) field with the family name (e.g., ["strategic-analysis-methodologies-cultural-artifacts"] or ["entity-systems-cultural-artifacts"]).

Both Mns at meta.sc=3 (instance scope).

4. The level-scoring discipline

For cultural-ecosystem positions:

For cognitive-architecture positions:

Author levels with brief evidence per chain level. For methodologies and technology systems, evidence is typically ~1-3 sentences citing the canonical source (book, citation count, certification body, deployment count).

5. The analysis

Once paired Mns exist for ≥5 instances:

Step 1: Compute three metrics per instance

• Analytical depth: total rank summed over the primary-arrangement Mn's positions.
• Cultural adoption: total rank summed over the cultural-artifact Mn's cultural-ecosystem chain level.
• Cognitive demand: total rank summed over the cultural-artifact Mn's cognitive-architecture chain level.

For depth, often the SUBSTRATE-only rank (not total rank) is more diagnostic — total rank can be polluted by chain levels that overlap with adoption (e.g., entity-arrangement's digital-ecosystem chain level overlaps semantically with cognition-arrangement's cultural-ecosystem).

Step 2: Plot depth × adoption

Scatter plot. Each instance is one point. Compute Pearson r and Spearman ρ. Annotate the regression line.

Step 3: Identify the three structural zones

• Mass-adoption zone: depth ≤ ~⅓ of max, adoption ≥ ~⅔ of max. Example anchors: SWOT in methodology landscape, Git in entity landscape.
• Specialized zone: depth in mid-range, adoption in mid-range. Example: Cynefin/OODA in methodology, Nostr/AT Protocol in entity.
• Depth-over-reach zone: depth ≥ ~⅔ of max, adoption ≤ ~⅓ of max. Example: SPA in methodology, Holochain/Urbit in entity.

Step 4: Interpret the correlation strength

• Strong inverse (r ≤ −0.5): suggests a SMOOTH GRADIENT mechanism — depth uniformly imposes a cost (cognitive demand or other) that suppresses adoption proportional to depth.
• Weak inverse (−0.5 < r ≤ −0.1): suggests BIMODAL or threshold mechanism — depth doesn't uniformly cost; specific architectural commitments (walls) cap adoption discontinuously.
• No correlation (|r| ≤ 0.1): depth and adoption are independent in this arrangement; depth doesn't penalize adoption.
• Positive correlation (r ≥ 0.1): adoption REQUIRES depth — usually means the chain-level definitions overlap (e.g., counting the digital-ecosystem chain in entity-arrangement total rank).

Step 5: Identify cultural-ecosystem accretion strategies

Look for distinct mechanisms among the high-adoption instances. In the methodology landscape: certification ecosystem (DMAIC's Six Sigma belts), academic legitimization (Porter Five Forces), popularizer-driven (OKRs via Doerr book), novel-format (TOC via The Goal). In the entity landscape: platform effects (GitHub), academic-database lock-in (Postgres), financial-economic integration (Bitcoin), federated-protocol-with-flagship-app (AT Protocol via Bluesky).

Each accretion strategy is structurally distinct and load-bearing for that instance's adoption.

6. Cross-landscape comparison

When you have ≥2 different landscapes analyzed, the cross-arrangement-coupling analysis can be compared:

• Z-score depth and adoption within each landscape before combining (different landscapes have different depth ranges).
• Plot all instances together on the z-scored plane with different markers per landscape.
• Compute combined Pearson r to see if the inverse pattern is shared.
• Compare the THREE-ZONE CLUSTERING — does each landscape have all three zones populated? Are the zones similarly anchored (highest-depth instance at depth-over-reach extreme)?

Per the empirical findings: the three-zone clustering pattern transfers across landscapes; the LINEAR correlation strength does not. This is itself diagnostic — it tells you whether the arrangement's depth-cost mechanism is gradient or bimodal-walls.

7. Interpreting differences across arrangements

When the linear correlation differs substantially across landscapes (e.g., methodology r = −0.710 vs entity r = −0.250), three structural explanations to consider:

1. Sample-size and depth-range artifacts: a smaller sample or narrower depth range can weaken correlation even if the underlying relationship is real.
2. Multiple high-adoption attractors at distinct depths: per Paper 6's attractor analysis, an arrangement may have several stable attractor states at different depth values, each admitting mass adoption. This SPREADS high-adoption across depth ranges and weakens the linear inverse.
3. Different depth-cost mechanism: gradient (uniform cognitive demand → smooth correlation) vs walls (architectural commitment that blocks adoption regardless of substrate elegance → bimodal pattern).

Mechanism 3 is structurally the most interesting. The methodology arrangement appears to penalize depth via uniform cognitive demand. The entity arrangement penalizes depth via architectural walls (Holochain DNA, Urbit Nock/Hoon). The two arrangements produce different shapes on the coupling plane for principled reasons.

8. What's NOT covered yet

This pattern is currently scoped to: the artifact-as-cultural-presence form of Sc=3 sustained coupling. The original sketch-sc3-sustained-coupling.md identified a SECOND form: shared-instance-evolving-in-multiple-arrangements-over-time (e.g., a developer's career as a coupled biology + cognition + entity trajectory across decades). This second form requires authoring TRAJECTORIES across multiple arrangements with coupling annotations between snapshots. Schema is feasible but not built. Future work.

9. Worked examples to study

10. The compute scripts as templates

Two reusable templates exist:

• compute/scripts/plot_methodology_coupling.py — pairs of methodology Mns + cognition cultural-artifact Mns; renders 2-panel figure (depth × adoption + depth × cog demand).
• compute/scripts/plot_entity_coupling.py — pairs of entity Mns + cognition cultural-artifact Mns; renders 3-panel figure (substrate-depth × adoption + total-rank × adoption + cross-landscape z-scored).

To author a new coupling analysis: copy one of these scripts, update the PAIRS list, update axis labels, run.

11. Discipline rules

When using cross-arrangement coupling analysis:

• R1: Always pair manifestations. Don't put cultural-artifact positions in the same Mn as analytical structure. Two arrangements → two Mns. The pairing convention <artifact> + <artifact>-cultural-artifact is canonical.
• R2: Author cultural levels with evidence. Each level claim needs ~1-3 sentences citing source (book, citation count, certification body, deployment count). No ungrounded levels.
• R3: Choose substrate-only or total-rank deliberately. Total rank can pollute the analysis when the primary arrangement has chain levels that overlap semantically with adoption. Substrate-only is cleaner for cross-landscape comparison.
• R4: Report Pearson AND Spearman. Pearson is sensitive to outliers (e.g., SPA in methodology landscape). Spearman is rank-only and more robust. Reporting both surfaces the difference.
• R5: Look for the three zones. Always.
• R6: Identify accretion strategies for high-adoption instances. What mechanism gave each high-adoption instance its cultural-ecosystem position? The strategies are themselves structurally distinct and worth cataloguing.
• R7: When correlations differ across arrangements, look for mechanism difference. The linear-correlation strength varying is informative — don't paper it over with combined-landscape statistics.

What the pattern accomplishes (executive read)

Cross-arrangement coupling is the analytical move that takes "system X is in arrangement Y" and makes it "system X has structurally-coordinated positions in arrangements Y AND Z, and the relationship between those positions is itself diagnostic." It transforms a single-arrangement analysis into a paired analysis that surfaces the depth-vs-reach trade-off as a load-bearing structural property rather than an external observation.

For the project: this is the second of two paper-grade analytical innovations developed during the methodology-computation effort. The first was the X-genesis trajectory regime taxonomy (3 confirmed regimes + 1 candidate). The second is cross-arrangement coupling. Together they let Paper 11 make empirical claims about cross-domain structural patterns rather than purely methodological claims about how to do analysis.