Applied Analysis: Domain Analysis (Layer 4)

Status: Full 12-step analysis. Revised: originally found 6 primitives; the 3/3b iteration loop (triggered by persistent confusion about physics and abstraction levels during the critical review and Layer 5 exploration) surfaced Scope (Sc) as a 7th primitive. The revision stabilizes the primitive set and resolves all encountered confusions. Domain kind (R1): Operational/tool domain. Applied analysis uses structural knowledge to characterize entities in their contexts. Neither substrate nor surface nor ecosystem — it's the methodology's contact with reality. Builds on: methodology.md §7, exploration-synthesis-and-unified-manifestation.md, analysis-unified-manifestations-software.md, analysis-digital-context.md, analysis-context-domain.md, explore/exploration-cross-chain-interaction.md, all trajectory analyses Revision history: review-applied-analysis-critical.md (confirmed 6 primitives stable), exploration-layer5-and-methodology-dynamics.md (no Layer 5 but identified coupling path / joint manifestation issues), exploration-specificity-and-the-universal-particular-distinction.md (identified scope as missing dimension), synthesis-layer4-session-review.md (confirmed Scope as 7th primitive)

Step 1 — Information Gathering

1.1 What we're analyzing

The analytical operations performed when you take the abstract structural knowledge from Layers 1-3 (domain primitives, edge types, graph patterns) and use it to analyze an entity in a context at a chosen level of specificity. This is what we've been DOING — positioning Git across 73 dimensions, identifying the entity system's bottleneck as Co2-3, mapping how a developer couples to software across three levels, tracing computing through 8 epochs.

The question: do these operations form a coherent domain with its own irreducible primitives?

1.2 What instances of applied analysis exist

From our methodology work:

• 9 unified manifestations of software systems (Git, Postgres, Bitcoin, Instagram, etc.) — all at universal scope (categories)
• Entity system checkpoint (~28/60 on app architecture, Co2-3 bottleneck) — at class/configuration scope
• Computing epochs (8 epochs mapped to primitive transitions) — at universal scope, sweeping time
• Git temporal evolution (5 epochs, substrate frozen in 2 weeks) — at class scope, sweeping time
• Cross-chain coupling analysis (human using software at 3 levels) — at event scope (tracing a keypress)
• SDK convergence analysis (converged operations across implementations) — at configuration scope

From other analytical traditions:

• Technology positioning (Gartner quadrants, ThoughtWorks radar) — universal/class scope
• Competitive analysis (Porter's Five Forces, SWOT) — class scope
• Phylogenetic analysis (organism placement in evolutionary trees) — universal scope
• Clinical diagnosis (patient characterization) — instance scope
• Technology assessment (TRL levels) — universal scope, single axis

1.3 What recurs across all instances

Every instance of applied analysis involves:

1. A structural framework for interpretation
2. A specific entity being characterized
3. A chosen level of specificity (is this the category "Git" or a specific Git installation?)
4. External conditions constraining the entity
5. Other entities in the same space for comparison
6. Cross-system interaction beyond the entity's own chain
7. Temporal dimension — where it was, is, and is going

These seven elements recur independently of analytical tradition. They are candidate primitives.

Step 2 — Landscape Analysis

2.1 Analytical traditions as instances

2.2 What the landscape reveals

Every tradition implicitly chooses a scope level. TRL analyzes technologies as categories (Sc0). Clinical diagnosis analyzes individual patients (Sc3). Porter analyzes industries at the class level (Sc1). None formalize this choice — it's implicit in the tradition's design.

Our methodology operates at ALL scope levels — and that's what caused confusion when scope wasn't explicit. The same vocabulary was being used for "Git the category" (Sc0) and "this keypress event" (Sc4) without acknowledging the difference.

Seven operations recur:

1. Interpret using a framework → requires Framework
2. Position the entity → requires Manifestation
3. Scope the analysis → requires choosing a specificity level
4. Constrain by external conditions → requires Context
5. Compare to peers → requires Landscape
6. Connect to other chains → requires Coupling
7. Trace over time → requires Trajectory

Step 3/3b — Primitives and Partial Levels

3.1 Primitive extraction

Seven candidates, tested against the three criteria:

1. Framework (Fw) — The structural knowledge from L1-L3 used as analytical lens.

• Structural minimality: without a framework, positioning is impossible — no coordinate system. ✓
• Compositional productivity: Fw + Mn = structural characterization. Fw + Tj = phase transition identification. Fw + Sc = scope-aware analysis (vs naive observation). ✓
• Empirical recurrence: every tradition uses one — our lattices, Porter's forces, phylogenetic trees. ✓

2. Manifestation (Mn) — An entity occupying positions across connected lattices. The structural identity of the thing being analyzed. Can be a category (universal) or a specific instance (particular), depending on Scope.

• Structural minimality: without a manifestation, there is nothing to analyze. ✓
• Compositional productivity: Mn + Cx = constrained feasibility. Mn + Ls = competitive positioning. Mn + Sc = scoped entity (category vs instance). ✓
• Empirical recurrence: Git, E. coli, Instagram, the entity system — every applied analysis. ✓

3. Scope (Sc) — The level of specificity at which the analysis operates. Determines how many dimensions of the manifestation are fixed (constrained to specific values) vs free (varying across instances). Scope determines what Mn captures, what Cx covers, and whether coupling is abstract or physical.

• Structural minimality: without scope, the analysis can't distinguish "Git" (category — all instances share this position) from "this Git process" (instance — specific physical entity). The methodology oscillates between abstract and concrete claims without vocabulary to notice the difference. THIS confusion is what triggered the 3/3b revision. ✓
• Compositional productivity: Sc + Mn = entity at chosen specificity. Sc + Cx = context at matching locality (era vs room). Sc + Cp = coupling character (structural vs physical). Sc + Ls = landscape character (categories vs instances). ✓
• Empirical recurrence: every applied analysis chooses a scope. Our 9 unified manifestations: Sc0. Entity checkpoint: Sc1-2. Keypress trace: Sc4. TRL: Sc0. Clinical diagnosis: Sc3. ✓

4. Context (Cx) — External operating conditions constraining what the manifestation can achieve. Independent root. Context locality co-varies with Scope — at Sc0 it's era-level, at Sc3 it's local.

• Structural minimality: without context, can position but can't explain outcomes or predict feasibility. ✓
• Compositional productivity: Cx + Mn = bottleneck identification. Cx + Sc = scoped context (the Mn-Cx boundary shifts with scope). ✓
• Empirical recurrence: digital context, cognitive context, biology environment — every tradition. ✓

5. Landscape (Ls) — The population of other manifestations in the same analytical space. At low Scope: a set of categories. At high Scope: a network of coupled instances.

• Structural minimality: without landscape, the entity is analyzed in isolation — no comparison, no competitive assessment. ✓
• Compositional productivity: Ls + Mn = comparative positioning. Ls + Cx = landscape explanation. ✓
• Empirical recurrence: 14-system entity analysis landscape, Porter's industry, ecological communities. ✓

6. Coupling (Cp) — Cross-arrangement interaction. At low Scope: structural relationship between categories. At high Scope: physically or conceptually mediated interaction between instances.

• Structural minimality: without coupling, cross-chain interaction invisible. ✓
• Compositional productivity: Cp + Mn = coupling profile. Cp + Sc = coupling character. ✓
• Empirical recurrence: human-software coupling, organism-environment coupling, market-producer coupling. ✓

7. Trajectory (Tj) — Path through the lattice over time. At low Scope: evolutionary epochs. At high Scope: specific development timeline.

• Structural minimality: without trajectory, analysis is static — no prediction, no planning. ✓
• Compositional productivity: Tj + Mn = development roadmap. Tj + Cx = trajectory prediction. ✓
• Empirical recurrence: computing epochs, Git evolution, application lifecycles. ✓

3.2 The 3/3b iteration loop

Round 1 (initial session): 6 candidates.

The original analysis found {Fw, Mn, Cx, Ls, Cp, Tj}. Agency and Event were tested and correctly excluded (agency is domain-specific; events are Trajectory's atoms).

Round 2 (triggered by critical review): Scope surfaced.

During the critical review and Layer 5 exploration, persistent confusion about physics and abstraction levels emerged:

• "Physics is ambient ground" → corrected: "manifestations can be pure abstractions"
• "All coupling is physical" → corrected: "coupling can be conceptual"
• "The Mn-Cx boundary shifts" → but the analysis didn't capture WHY

The confusion pattern was diagnostic: the same vocabulary was being used for fundamentally different levels of specificity. "Git" (universal, physics-free) and "this Git process" (particular, physically realized) were both called "manifestations" with no distinction.

This is the 3/3b signal: a claimed primitive (Manifestation) was actually BUNDLING two things — the entity's POSITION (which dimensions it occupies) and the entity's SCOPE (how many dimensions are fixed vs free). When these were separated, the confusion resolved.

Round 2 checks:

Context and Landscape — still separate (states vs entities, different dynamics). ✓ Stable.

Framework — still unified (L1+L2+L3 as single lens). ✓ Stable.

Scope and Manifestation — genuinely distinct. Mn is WHAT you're analyzing. Sc is HOW SPECIFICALLY. A manifestation at Sc0 is a category; the same manifestation at Sc3 is an instance. Same position, different scope. Neither reduces to the other. ✓ Separate.

Primitive set stable at 7: {Fw, Mn, Sc, Cx, Ls, Cp, Tj}.

3.3 Partial levels

Framework (Fw):

Phase transition: Fw2→Fw3. Below: independent coordinates. Above: dependencies, pairs, phase transitions. Transition from "description" to "structural analysis."

Manifestation (Mn):

Mn describes analytical BREADTH — how many domains included. Scope (Sc) describes SPECIFICITY — how constrained. These are orthogonal.

Phase transition: Mn1→Mn2. Single-domain → multi-domain. Bridge constraints become visible.

Scope (Sc):

Phase transition: Sc0→Sc1. Domain-specific constraints enter. Below: pure structural claims. Above: era/platform constraints bind.

Phase transition: Sc2→Sc3. For physically-grounded domains, physics becomes load-bearing. Below: the analysis applies to many possible instances. Above: specific physical realization. For NON-physical domains (pure math, abstract structure): Sc3+ may not apply — there are no "specific instances" of abstract categories.

Scope determines the character of ALL other primitives simultaneously:

• Mn at Sc0 = category; Mn at Sc3 = instance
• Cx at Sc0 = era; Cx at Sc3 = local conditions
• Ls at Sc0 = categories; Ls at Sc3 = instance network
• Cp at Sc0 = structural relationship; Cp at Sc3+ = mediated interaction (physical for physical domains, conceptual for abstract domains)
• Tj at Sc0 = epochs; Tj at Sc3 = specific timeline

Context (Cx):

Phase transition: Cx2→Cx3. Context becomes ACTIONABLE — specific levels gate specific moves.

Note: Cx locality co-varies with Sc. At Sc0, Cx describes era-level conditions. At Sc3, Cx describes local physical environment. The Mn-Cx boundary (what's "inside" the entity vs "outside" as environment) shifts with Scope.

Landscape (Ls):

Phase transition: Ls2→Ls3. Below: you know where peers are. Above: you know WHY.

At Sc0-Sc2, Ls is a set of categories. At Sc3+, Ls becomes a network of coupled instances — who's connected to whom through what mediation.

Coupling (Cp):

Phase transition: Cp2→Cp3. Below: coupling categorized. Above: specific primitives connected.

At Sc0, coupling is a structural relationship between categories (no physical mediation needed). At Sc3+, coupling may involve physical mediation paths for physically-grounded domains, or conceptual/logical connections for abstract domains.

Trajectory (Tj):

Phase transition: Tj2→Tj3. Descriptive → predictive.

Step 4 — Dependencies

Fw → Mn  (positioning requires framework)
Fw → Sc  (scope requires framework to define fixable dimensions)
Mn → Ls  (landscape requires manifestations)
Mn → Cp  (coupling requires manifestations)
Mn → Tj  (trajectory requires manifestation)
Cx: independent root

Sc and Mn are siblings — both depend on Fw, neither depends on the other. You can set scope before choosing an entity, and you can position an entity with scope defaulting to Sc0.

      Fw
     / | \
    Sc Mn  
       | \
       |  → {Ls, Cp, Tj}
   Cx (independent)

Filter calculation

2^7 = 128 total subsets. Cx is free (can be added to any coherent subset).

Without Cx, coherent subsets require: Mn → Fw, Sc → Fw, {Ls,Cp,Tj} → Mn → Fw.

Without Cx:

• Size 0: {} = 1
• Size 1: {Fw} = 1
• Size 2: {Fw,Sc}, {Fw,Mn} = 2
• Size 3: {Fw,Sc,Mn}, {Fw,Mn,Ls}, {Fw,Mn,Cp}, {Fw,Mn,Tj} = 4
• Size 4: {Fw,Sc,Mn,Ls}, {Fw,Sc,Mn,Cp}, {Fw,Sc,Mn,Tj}, {Fw,Mn,Ls,Cp}, {Fw,Mn,Ls,Tj}, {Fw,Mn,Cp,Tj} = 6
• Size 5: {Fw,Sc,Mn,Ls,Cp}, {Fw,Sc,Mn,Ls,Tj}, {Fw,Sc,Mn,Cp,Tj}, {Fw,Mn,Ls,Cp,Tj} = 4
• Size 6: {Fw,Sc,Mn,Ls,Cp,Tj} = 1

Total without Cx: 19. With Cx: 38.

(R2) Filter: 38/128 = 29.7%. Matches Layer 1 exactly. The addition of Scope tightened the filter from 31.25% to 29.7%, adding another Fw dependency.

Step 5 — Pair Enumeration

C(7,2) = 21 pairs.

Step 6 — Load Classification

Summary:

• Heavy: 8 (Fw-Mn, Mn-Sc, Mn-Cx, Mn-Ls, Mn-Tj, Cx-Sc, Cx-Ls, Cx-Tj)
• Medium-Heavy: 2 (Fw-Sc, Fw-Tj)
• Medium: 10 (Fw-Cx, Fw-Ls, Fw-Cp, Mn-Cp, Cx-Cp, Ls-Sc, Ls-Tj, Cp-Sc, Cp-Tj, Tj-Sc)
• Light: 1 (Ls-Cp)

Heavy: 8/21 = 38%.

Hubs:

• Mn: 5 heavy (Fw-Mn, Mn-Sc, Mn-Cx, Mn-Ls, Mn-Tj) — strongest hub
• Cx: 4 heavy (Mn-Cx, Cx-Sc, Cx-Ls, Cx-Tj) — co-hub
• Sc: 2 heavy (Mn-Sc, Cx-Sc) + 4 medium — well-connected

Anchor pair: Mn-Cx — entity-in-context. The irreducible core of all applied analysis.

Step 7 — Coherent Sub-Lattice

38 coherent subsets out of 128 = 29.7%. See Step 4 for enumeration.

Step 8 — Hasse Diagram Walks

Path α — Strategic Assessment

{} → {Fw} → {Fw,Sc} → {Fw,Sc,Mn} → {Fw,Sc,Mn,Cx} → {Fw,Sc,Mn,Cx,Ls} → {Fw,Sc,Mn,Cx,Ls,Tj} → Full

"Establish framework. Set scope (Sc0 strategic). Position the entity. Add context. Map landscape. Trace trajectory. Add coupling."

Path β — Cross-Chain Coupling

{} → {Fw} → {Fw,Mn} → {Fw,Mn,Sc} → {Fw,Mn,Sc,Cp} → {Fw,Mn,Sc,Cp,Cx} → ... → Full

"Establish framework. Position the entity. Set scope (Sc3+ for physical coupling, Sc0-2 for abstract). Analyze coupling. Add context."

Path γ — Temporal / Ontogenetic

{} → {Fw} → {Fw,Sc} → {Fw,Sc,Mn} → {Fw,Sc,Mn,Tj} → {Fw,Sc,Mn,Tj,Cx} → ... → Full

"Establish framework. Lock scope. Position entity. Sweep trajectory while context and landscape change."

This is the ontogenetic pathway: scope-locked traversal along Tj.

Path δ — Context-First

{} → {Cx} → {Cx,Fw} → {Cx,Fw,Sc} → {Cx,Fw,Sc,Mn} → ... → Full

"Understand context first. Establish framework. Choose scope. Then position the entity."

Path ε — Scope Descent (zoom in)

Run at Sc0 → identify issue → re-run at Sc2 → identify component → re-run at Sc3

"Start strategic, discover need for tactical detail, zoom in." Each run is a full walk through the lattice; the sequence of runs descends through scope levels. This is Boyd's orientation phase as scope shift.

Step 9 — Load-Bearing Compositions

Core triads

{Mn, Cx, Sc} — The Analytical Frame ★

All three pairs heavy (Mn-Cx, Mn-Sc, Cx-Sc). Irreducible:

• Mn+Cx without Sc: entity in context but scope unknown — can't tell if talking about the category or a specific instance. THE confusion we experienced.
• Mn+Sc without Cx: entity at scope but unconstrained — positioned with no feasibility check.
• Cx+Sc without Mn: scoped context with nobody in it.

The analytical frame IS "an entity, in its operating context, at a chosen level of specificity." All three must be set before any other analysis makes sense.

{Mn, Cx, Ls} — Strategic Positioning ★

All three pairs heavy. Entity in context among peers. Niche identification, competitive feasibility. Unchanged from original analysis.

{Mn, Cx, Tj} — Trajectory Planning ★

All three pairs heavy. Entity in context over time. Roadmap generation, bottleneck identification. Unchanged from original analysis.

Three-triad structure

All three core triads share the Mn-Cx anchor pair and branch orthogonally:

              Sc (scope — at what level?)
              |
        Mn —— Cx (anchor: entity-in-context)
       / \
      Ls   Tj
  (space)  (time)

Three dimensions from one anchor: scope, space, time. Three fundamental questions:

1. {Mn,Cx,Sc}: "At what level of specificity am I analyzing?"
2. {Mn,Cx,Ls}: "Where does this entity sit among its peers?"
3. {Mn,Cx,Tj}: "Where is this entity going over time?"

Higher-arity compositions

{Mn, Cx, Sc, Ls} — Scoped Strategic Positioning (quad)

Strategic positioning at a specific scope. "The entity system category (Sc0) among peer categories in the current era" vs "this entity system deployment (Sc3) among competitor deployments in this market."

{Mn, Cx, Sc, Tj} — Scoped Trajectory Planning (quad)

Trajectory at a specific scope. "Computing's epochal evolution (Sc0)" vs "this project's quarterly development (Sc2)." Scope determines temporal grain.

{Mn, Cx, Sc, Ls, Tj} — Full Scoped Assessment (5-element)

The complete strategic picture at a chosen scope — where the entity is, among whom, under what constraints, heading where, at a specific level of abstraction.

Full set {Fw, Mn, Sc, Cx, Ls, Cp, Tj}

Adding Framework provides rigor. Adding Coupling provides cross-chain reach. The complete applied analysis.

Step 10 — Emergent Properties

From {Mn, Cx, Sc} (Analytical Frame):

• Scope-appropriate analysis — matching abstraction level to the question asked
• Physics/abstraction clarity — knowing when physical grounding matters (Sc3+ in physical domains) vs when it doesn't (Sc0-2, or abstract domains at any scope)
• Joint manifestation — locking in two entities + coupling at a specific scope: Joint(A,B) at Sc = Mn(A) × Cp × Mn(B), all at scope Sc
• Mn-Cx boundary determination — scope fixes what's "inside" the entity vs "outside" as context

From {Mn, Cx, Ls} (Strategic Positioning):

• Niche identification — structural position differentiating from peers
• Competitive advantage — what the position provides that peers don't
• Market viability — sustainability of position in current landscape

From {Mn, Cx, Tj} (Trajectory Planning):

• Bottleneck identification — binding constraint (context primitive or internal dependency)
• Phase transition timing — when to attempt discontinuous advances
• Path recommendation — optimal move sequence
• Lifecycle classification — Ship-and-Done, Feature Plateau, Continuous Elaboration, etc.

From {Mn, Cx, Sc, Ls, Tj} (Full Scoped Assessment):

• Strategy/tactics/operations — the SAME analysis at different Sc levels:
  • Strategy = Sc0-1, Ls-heavy, Tj in epochs
  • Tactics = Sc2-3, Mn-heavy, Tj in quarters
  • Operations = Sc3-4, Cp-heavy, Tj in days

Step 11 — Structural Patterns

Pattern 1: Three core triads from anchor pair

Three core triads ({Mn,Cx,Sc}, {Mn,Cx,Ls}, {Mn,Cx,Tj}) share the Mn-Cx anchor pair and branch in three orthogonal directions: scope, space, time. This extends the two-triad pattern seen in the UI domain ({E,S,V} and {E,C,Σ} sharing E). Applied analysis has THREE independent dimensions — abstraction level, competitive position, and temporal dynamics — all grounded by entity-in-context.

Pattern 2: Framework as depth multiplier

Fw connects to everything at medium+ level but creates only one heavy pair (Fw-Mn). It DEEPENS every analysis without being the primary content. Analogous to the evaluator's role in information substrates.

Pattern 3: Hub and independent root

Mn is hub (5 heavy). Cx is independent root. Same pattern as entity system (E hub, I independent) and biology (G hub, environment independent root).

Pattern 4: Scope determines primitive character

Unique to Layer 4: one primitive (Sc) determines the CHARACTER of all others. No other analyzed domain has a primitive that transforms the content of all other primitives simultaneously. This is why Scope was initially missed — it's not content, it's the FRAME that determines what content means.

Pattern 5: Strategy/tactics/operations as scope gradient

The universal strategy/tactics/operations hierarchy maps to Sc0/Sc2/Sc4. Not different kinds of analysis — the same analysis at different scope. This is a testable structural prediction.

Step 12 — Literature Alignment and Cross-Domain Mapping

12.1 Cross-domain mapping to methodology layers

Three genuinely new: Scope (Sc), Context (Cx), and Trajectory (Tj). They add specificity control, external constraint, and temporal dynamics — all absent from L1-L3.

12.2 Methodology meta-structure

Filter pattern: 29.7% → 25% → 18.75% → 29.7%. L1-L3 tighten progressively. L4 matches L1 exactly. Total: 24 primitives across 4 layers.

12.3 Genuine layer test

1. Own irreducible primitive set — YES: 7 primitives, all passing three-test. ✓
2. Primitives not derivable from L1-L3 — YES: Sc, Cx, Tj are genuinely new. ✓
3. Own internal structure — YES: dependency DAG, 3 core triads, anchor pair, 29.7% filter. ✓
4. Meaningful edges to other layers — YES: decomposition to L1/L2, feed from/to L3. ✓
5. Unique outputs — YES: bottleneck ID, trajectory prediction, scope-appropriate analysis. ✓

Layer 4 confirmed with 7 primitives.

Summary

The seven primitives

Structural signature

• Hub: Mn (5 heavy connections)
• Independent root: Cx
• Anchor pair: Mn-Cx (entity-in-context)
• Core triad 1: {Mn, Cx, Sc} — Analytical Frame (at what level?)
• Core triad 2: {Mn, Cx, Ls} — Strategic Positioning (among whom?)
• Core triad 3: {Mn, Cx, Tj} — Trajectory Planning (heading where?)
• Three orthogonal branches from anchor: scope, space, time
• Filter: 29.7% (38/128) — matches Layer 1
• Heavy pairs: 8/21 (38%)
• Phase transitions: Fw2→3 (description→structure), Sc0→1 (universal→constrained), Sc2→3 (abstract→physical for physical domains), Mn1→2 (single→multi-domain), Cx2→3 (described→actionable), Ls2→3 (positioned→compared), Cp2→3 (typed→mapped), Tj2→3 (descriptive→predictive)

Referenced by the model

Cited as a source by 2 model records (browse the model census):

• methodology-layer4 — domain methodology/sc1
• methodology — arrangement methodology/sc1