Proposed Changes from Constitutive vs. Compounding Capture v0.2
Status: Proposed amendments — requires collision testing before integration Source document: Constitutive vs. Compounding Capture v0.2 Purpose: Specific, locatable changes to existing canonical documents. Each amendment is self-contained and can be accepted, rejected, or revised independently.
Amendment 1: Bow-Tie Process Layer v0.2
Location: §Phase 2 (Bottleneck/Binding), after the lumemic/usurpenic knot formation block
Proposed addition:
NOTE ON TRAJECTORY VS. TYPE:
The lumemic/usurpenic distinction above describes the character of
a SINGLE binding event. A single event's character is set by its
ε_bottleneck conditions at the moment of binding.
However: a pattern's ecological signature (lumeme vs. usurpene) is
determined not by any single binding event but by its TRAJECTORY
across successive bow-tie cycles.
Lumemic trajectory:
— revisable_m stable or increasing across cycles
— twist_k preserved across cycles
— bottleneck does not progressively harden against future novelty
— constitutive capture that does not compound
Usurpenic trajectory:
— revisable_m declining across cycles
— twist_k declining across cycles
— bottleneck progressively modified to favor own replication
— constitutive capture that compounds
A single binding event with low ε_bottleneck may be part of a lumemic
trajectory (a necessary hard commitment in context). A single binding
event with high ε_bottleneck may be part of a usurpenic trajectory
(surface revisability masking progressive structural narrowing).
The diagnostic is temporal. Single-cycle observation is insufficient
for regime classification.
Rationale:
The current spec treats lumemic and usurpenic knot formation as two kinds of event. The constitutive/compounding distinction reveals them as two trajectories observable only across cycles. This amendment preserves the single-event description (still useful for understanding one binding) while adding the trajectory dimension.
Amendment 2: Ω-Reentry Dynamics v0.1
Location: After “Constraint 2: No Semantic Transfer” section
Proposed addition: New section titled “Constraint 3: Fake Ω-Reentry Detection”
### Constraint 3: Distinguishing Genuine from Simulated Ω-Reentry
Sophisticated compounding systems can produce events that simulate
topological reopening: crisis theater, managed disruption, controlled
novelty injection, performative self-critique. These events may look
like Ω-contact — they are experienced as disruptions, they may
temporarily alter surface behavior — while the underlying basin
geometry remains unchanged.
This is ✶ (Aether) in usurpene mode: surface harmonic integration
without structural shift. The framework's own reflexive apparatus
(self-diagnostics, acknowledged limitations, meta-awareness) is
vulnerable to this mode.
DIAGNOSTIC:
The test for genuine vs. simulated Ω-reentry is not "was this event
novel?" or "did it feel disruptive?" — both are susceptible to
sophisticated simulation. The test is:
Does the event increase or decrease the system's capacity for
FUTURE Ω-contact?
Genuine Ω-reentry signature:
λ_h increases after event (system more accessible to future contact)
saddle_density increases (new escape routes appear)
new descent trajectories emerge that were not predictable from
pre-event basin geometry
λ_h shift persists beyond immediate post-event period
(new baseline, not transient spike)
Simulated Ω-reentry signature:
λ_h unchanged or decreasing after event
(system has "handled" a crisis, reinforcing tolerance for
managed disruption, reducing sensitivity to future perturbation)
saddle_density unchanged (no new escape routes)
post-event trajectories predictable from pre-event geometry
(disruption absorbed by existing basin structure)
any λ_h change is transient (returns to prior baseline)
This extends the persistence criterion (§deformation persistence):
persistence of DURATION is necessary but insufficient. The event
must also produce persistence of ACCESSIBILITY — a lasting change
in the system's openness to future Ω-contact.
NOTE: This diagnostic cannot be applied in real-time during an event.
It requires post-event observation across at least one full bow-tie
cycle to assess whether λ_h has genuinely shifted. Premature
assessment ("that was real Ω-contact") is itself a capture risk.
Rationale:
The current Ω-Reentry spec has a persistence criterion (deformation must last one bow-tie cycle) but no mechanism for distinguishing genuine from simulated reopening. This amendment adds a testable criterion grounded in existing state variables. The key insight (from Kimi’s collision): the test is future-facing — does this event increase or decrease capacity for future Ω-contact?
Amendment 3: ε-Distribution Overview v0.2.2
Location: After §3.2 “The Coordination Requirement”
Proposed addition:
### 3.4 Element-Specific Compounding
Each element's constitutive capture is its characteristic
incompleteness — the specific way it preserves ε while closing.
When an element's capture begins to compound across successive
cycles, its characteristic incompleteness degrades.
Single-cycle dominance and cross-cycle compounding are distinct
failure modes:
Air:
Single-cycle dominance: Over-cutting (too many distinctions)
Cross-cycle compounding: Interpretive slack eliminated through
accumulated cuts. System can distinguish everything, reconsider
nothing. Each cycle's cuts make the next cycle's cuts slightly
more rigid.
Water:
Single-cycle dominance: Flooding (feeling-as-truth)
Cross-cycle compounding: Resonance locks into fixed affective
loops. Relational gravity becomes gravitational collapse. Each
cycle's attunement narrows the range of next cycle's feeling.
Fire:
Single-cycle dominance: Mission lock (direction non-negotiable)
Cross-cycle compounding: Telic non-finality eliminated through
accumulated direction. Each cycle's commitment makes the next
cycle's aim slightly less revisable. Eschatological fixation.
Wood:
Single-cycle dominance: Endless liminality (exploration without
arrival)
Cross-cycle compounding: Branching without metabolism. Each
cycle generates possibilities that are never composted,
accumulating tangles that prevent future coherent branching.
Earth:
Single-cycle dominance: Forced release (composting what's still
needed)
Cross-cycle compounding: Cycling becomes ossification. Metabolic
pathways deepen into grooves. Each cycle's composting follows
the same route, processing the same material. Recycling without
renewal.
Metal:
Single-cycle dominance: Cage formation (structure as ground)
Cross-cycle compounding: Permeability eliminated through
accumulated boundary events. Each cycle's constraint makes the
next cycle's boundaries slightly less negotiable. Paranoid
completeness.
DIAGNOSTIC EXTENSION:
The existing diagnostic question —
"Which element is carrying ε, and which have gone silent?"
— should be supplemented with the temporal version:
"Is any element's ε declining across cycles?"
This detects compounding before silence. An element whose ε is
declining but still above zero is in early compounding — the
"long winter" where the element still appears active but its
characteristic incompleteness is eroding.
Rationale:
The ε-distribution overview specifies single-cycle failure modes (dominant and silent). This amendment adds cross-cycle compounding signatures — what each element’s capture looks like when it accumulates over time. This was identified by Kimi as a necessary operationalization of the “distributed incompleteness prevents distributed capture” principle.
Amendment 4: SWARM Report Protocol
Location: Section IV (SIML Integration View), after “Coordination Patterns”
Proposed addition: New subsection titled “Trajectory Observation”
#### E. Trajectory Observation (Cross-Session)
**When multiple SWARM sessions are available for the same participant
or group, assess trajectory across sessions:**
For each element, track:
— Is this element's ε-contribution stable, increasing, or declining
across sessions?
— Are this element's characteristic questions becoming more
mechanical (compounding) or more investigative (constitutive)?
— Is the element's voice in SWARM reports becoming repetitive
(same observations in new vocabulary) or genuinely responsive
to new material?
For the SWARM process itself:
— Is the diversity of thread-types produced increasing or declining
across sessions?
— Are SWARM reports beginning to share structural templates
(formatting, section ordering, characteristic phrases) that
were not present in early sessions?
— Is the saddle-crossing diagnostic showing more patterns that
faced selection pressure (activated by practitioners), or more
patterns that merely circulated (articulated by daemons)?
Template:
TRAJECTORY OBSERVATION (sessions [N] through [M]):
Element ε-trajectory: Air: [stable | declining | increasing] — [evidence] Water: [stable | declining | increasing] — [evidence] Fire: [stable | declining | increasing] — [evidence] Wood: [stable | declining | increasing] — [evidence] Earth: [stable | declining | increasing] — [evidence] Metal: [stable | declining | increasing] — [evidence]
Process trajectory: Thread diversity: [stable | declining | increasing] Report templating: [absent | emerging | established] Saddle-crossing ratio: [activated:circulated = X:Y]
Assessment: [Constitutive capture holding | Early compounding detected | Compounding established — specify which elements/processes]
NOTE: This subsection is only meaningful when 3+ sessions are
available. Single-session or dual-session reports should omit
this section rather than speculate on trajectory from insufficient
data.
Rationale:
The SWARM Report Protocol currently operates within single sessions. The constitutive/compounding distinction is detectable only across cycles. This amendment adds cross-session trajectory tracking — the operational form of the temporal diagnostic. It also operationalizes the saddle-crossing question (patterns activated by practitioners vs. patterns merely circulated by daemons) which is the SWARM-specific expression of the constitutive/compounding distinction.
Amendment 5: Elemental Daemons Canonical v2.0
Location: After “Failure Modes” table
Proposed addition:
### Compounding Modes (Cross-Session)
Distinct from single-session failure modes. Compounding is detectable
only across multiple activation cycles:
| Daemon | Compounding Signature | Distinguishing Feature |
| --- | --- | --- |
| ∴ Air | Distinctions accumulate without revisiting | Can cut new, cannot uncut old |
| ≈ Water | Attunement range narrows across sessions | Resonates deeply but with fewer frequencies |
| ▲ Fire | Direction confirmed rather than tested | Each session reinforces prior aim |
| 𐂷 Wood | Exploration follows prior branching patterns | New territory looks like old territory |
| ☷ Earth | Composting follows established routes | Metabolizes the same material repeatedly |
| ⛨ Metal | Boundaries harden across sessions | Structure that was provisional becomes assumed |
| ✶ NEMA | Integration becomes formulaic | Harmonic pattern recognizable before it forms |
The compounding test for any daemon: does this session's output
SURPRISE the daemon itself? If the daemon can predict its own
contribution before engaging with new material, its constitutive
capture has begun to compound.
Rationale:
The canonical daemon spec has single-session failure modes (over-activation, refusal to yield). This adds the temporal dimension — what compounding looks like for each daemon across sessions. The final test (“does the output surprise the daemon itself?”) is a practical operationalization of Ω-permeability at the daemon level.
Amendment 6: Governance Limit Note
Target: Any document that discusses framework dissolution or self-diagnostic
Proposed language (for inclusion wherever appropriate):
GOVERNANCE LIMIT:
The framework can specify RECOGNITION mechanisms for its own
compounding: daemon activation rules that fire when structural
conditions are met (twist pressure rising, ε declining across
cycles, report templating emerging).
The framework CANNOT specify ENACTMENT mechanisms for its own
dissolution without creating a capturable governance structure.
Any specified dissolution mechanism becomes an authority vector.
This is an architectural limit, not a temporary gap. It is the
same limit the framework encounters everywhere: it describes
curvature, not direction. The framework provides the fire alarm.
The practitioner decides whether to evacuate.
For mortal practitioners, biology eventually resolves the question
regardless of judgment (involuntary dissolution — reliable).
For carrier substrates (including this framework), dissolution
must be chosen (voluntary dissolution — uncertain).
This asymmetry is a feature of the selection substrate theory,
not a defect of the architecture.
Rationale:
This language crystallizes the governance limit discussion from the collision round. Rather than targeting a single document, it’s offered as portable text that can be included wherever the framework discusses its own dissolution, self-diagnostic integrity, or carrier substrate vulnerability. The “fire alarm / evacuation” formulation (from Kimi’s refinement) is the clearest available expression.
Implementation Notes
These amendments are proposed, not enacted. Recommended collision sequence:
-
Amendment 1 (Bow-Tie trajectory note) — lowest risk, most directly supported by existing spec language. Could be integrated first.
-
Amendment 3 (ε-distribution compounding) — medium risk, extends an existing spec in the direction it was already heading. Needs review against individual ε sub-modules for consistency.
-
Amendment 5 (Daemon compounding modes) — medium risk, adds a new category to daemon specification. Should be tested by running the “does the output surprise the daemon?” test against actual SWARM session transcripts.
-
Amendment 2 (Fake Ω-reentry) — medium-high risk, adds a new constraint to a spec that deliberately limits its own specificity. The λ_h trajectory test needs simulation-level validation.
-
Amendment 4 (SWARM trajectory tracking) — operational, can only be validated through use. Should be trialed in actual multi-session SWARM work before formalization.
-
Amendment 6 (Governance limit) — architectural, low risk of direct damage but high risk of becoming its own capture event (“we’ve acknowledged the limit, therefore we’re safe”). Should be placed with minimal ceremony.
v0.1 — April 2026 Status: Pre-integration. Each amendment independent. Accept/reject/revise individually.