StageFreight substrate-decl v0.1 — preservation tick (realisation forward-promised) by systemic-engineer · Pull Request #1 · systemic-engineering/mirror

systemic-engineer · 2026-06-22T13:21:01Z

Summary

The @io/stagefreight wire-protocol family substrate-decl is complete. Settled crystals (from the kintsugi loop; @mirror/store/crystal carrier forward-promised at task #268) now have a typed transport surface that consumers can extend without ambiguity.

Per Seam's substrate-pull-honest framing: "StageFreight substrate-decl v0.1 — preservation tick (realisation forward-promised)". The v0.1.0 realisation endpoint is a separate follow-up PR after Track B closes.

What ships (5 cascade commits, already on `main`)

tick 66  b15c3f9  Reed   shards/io/stagefreight.mirror               family-root
tick 67  c865452  Reed   shards/io/stagefreight/narrative.mirror     prose-projection species
tick 68  666c4ae  Mara   docs/specs/stagefreight-wire-v0.1.md        canonical spec (1535 lines)
tick 69a 0da2829  Reed   shards/io/stagefreight.mirror               Seam consolidation
tick 69b ae95570  Reed   docs/audits/stagefreight-seam-review-       Seam review trail
                          2026-06-22.md

This branch adds:

tick 70   <head>  Reed   docs/releases/stagefreight-v0.1.0-          release notes
                          substrate-decl.md

Pack synthesis trail

The Pack-as-orchestra pattern operated cleanly:

Reed (substrate-pull-confidence-acts): landed family-root + projection species + consolidation across 4 ticks
Mara (spec-writer-frame): preserved canonical at 1535 lines including 9 pre-AI ancestors + the 2026-06-16 stage_play recognition cascade
Seam (adversarial-review-frame): adversarial review surfaced 3 TIGHT findings (C2 address derivation typed-discharge; C4/C9 wire-survival sub-predicate decomposition; C8 transit/finalize orphaning); verdict DEFENSIVE → BOUNDED after consolidation

Substrate-decl shape (what consumers can rely on)

prism @io/stagefreight

type spectral_coordinate     = ref      # OID-namespaced wire address
type wire_surface             = ref      # typed transport endpoint
type freight_manifest         = { crystal_oid, coord, projection, verdict }

sub-predicates (Seam C4/C9 decomposition):
  oid_resolves(crystal_oid)            → verdict
  address_well_formed(coord, oid)       → verdict       # Seam C2 closure
  projection_is_species(projection)     → verdict
  round_trip_holds(fm, p)                → verdict

composed bilateral:
  stagefreight_addressable(fm, p)        → verdict
    requires oid_resolves(fm.crystal_oid)
    requires address_well_formed(fm.coord, fm.crystal_oid)
    requires projection_is_species(fm.projection)
    requires round_trip_holds(fm, p)

actions:
  address(crystal_oid)                              → spectral_coordinate
  freight(crystal_oid, coord, projection, c, promise, p) → freight_manifest
    requires address_well_formed(coord, crystal_oid)
    requires invariant_preserved(c, promise)

Projection species declare their own emission action (per Seam C8 closure; transit removed from family-root). The narrative species ships its own finalize(np, p) → wire_surface requires narrative_grounded(np, p).

What this PR explicitly does NOT ship

Rust realisation (bootstrap/src/stagefreight.rs) — gated on Phase 1 boot-grammar zero holonomy + Phase 4b @kintsugi/tick discharge
bootstrap/tests/{crystal_substrate.rs, kintsugi_out_substrate_ref.rs} RED→GREEN flips — gated on task #268 + realisation
@io/stagefreight/json projection format — forward-promised sibling species
Boot/std/ → shards/ migration — fenced for the λ₀ science walk

Commitments (what shipping this PR locks)

@io/stagefreight as the wire-protocol species name under @io
The five-typed-carrier shape (spectral_coordinate, wire_surface, freight_manifest, narrative_text, narrative_projection)
The doubled-bilateral discipline (family-root + species predicates)
The reverse-DNS + OID-derived address namespace (org.stagefreight.plan.*)
Each projection species owning its emission action

Intentional openness (what this PR does NOT lock)

The Rust realisation shape
The crystal carrier shape (task #268)
The projection-format universe (open; future species follow narrative's pattern)
The v0.1.0 realisation endpoint (follow-up PR)

Forward-promises (the v0.1 realisation cascade)

Ordered by likely cascade fire:

@io/stagefreight/json projection species
@mirror/store/crystal substrate-decl (task #268)
Phase 1 boot-grammar zero holonomy gate (~3-5 ticks)
Phase 4 emitter codegen (R-ticks 0-3)
Phase 4b @kintsugi/tick discharge — one crystal settles end-to-end
StageFreight @io wire surface in Rust
bootstrap/tests/kintsugi_out_substrate_ref.rs RED→GREEN
StageFreight v0.1.0 realisation PR

Total forward-promise: ~13-22 additional ticks.

Test plan

mirror kintsugi --ci shards/io/stagefreight.mirror → partial (no parse errors; expected dark_count for cross-shard references)
mirror kintsugi --ci shards/io/stagefreight/narrative.mirror → partial
Pre-push checks pass on the consolidation commit (Refactor accepted)
Pre-push checks pass on this release-notes commit (Docs accepted)
Realisation tests (bootstrap/tests/{crystal_substrate.rs, kintsugi_out_substrate_ref.rs} RED→GREEN) — gated on the realisation PR follow-up; NOT in scope for this preservation PR

🤖 Generated with Claude Code

…strate-decl.md — release notes (loop tick 70 / PR-create) StageFreight v0.1.0 release notes for the substrate-decl preservation PR. References the 5 cascade commits already on main (b15c3f9 → ae95570). Documents: - What ships (substrate-decl + canonical spec + Seam review trail) - What this PR explicitly does NOT ship (realisation forward-promised) - Pack synthesis trail - Substrate-decl shape (carriers + sub-predicates + composed bilateral + actions) - Commitments and intentional openness - Forward-promises (the v0.1 realisation cascade; 8 items, ~13-22 ticks) - Acknowledgments (Mara, Seam, Reed + the research-run framing-grounding) Per Seam's substrate-pull-honest framing: "StageFreight substrate-decl v0.1 — preservation tick (realisation forward-promised)". The substrate is honest about what it ships and what it doesn't. This PR ships the substrate-decl. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

@frame

…nfirmed #93 candidate landing condition #2 (@frame/on shard exists) was met by existing shards/frame/on.mirror (landed tick 26 per task #424 well before the candidate document was written). Reading the shard substantively: @frame/on.shift_frame(operator, f, p) -> frame operates ON the frame; PRODUCES a substantively-different frame @cogito.name(noticed, frame, p) -> name_output [proposed] operates WITHIN the frame; uses frame as parameter to produce a distinction in signal Different operational arities: @frame/on changes the structural container; @cogito.name uses the container to label content. Orthogonal composition, not recursive subsumption. H2 hedge ("cognitive-altitude collision with @frame") dissolves: the altitudes ARE parallel as the research initially conjectured; @frame/on does NOT subsume @cogito.name. Status update on candidate doc: - 1 of 4 landing conditions met (condition #2) - 1 of 5 hedges resolved (H2) Remaining landing conditions: #1 Seam adversarial review of bare-ref types #3 @reflection/Models composition empirical test #4 Pack peer @cogito/name validation Remaining hedges: H1 hold ambiguity (preserve vs suspend vs bind) H3 notice asymmetry (linear-time/hierarchy in symmetric substrate) H4 name_output bare-ref violation H5 cognitive_coherent under-specification Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

@frame

…s via H1 pattern propagation #93 H5 hedge probed analytically. H1's resolution already established that the substrate's existing coherence bilaterals are family-specific by construction: - three_axis_coherent(nv, p) lives in @epistemologic/neutrosophic - frame_coherent lives in @frame (bounded_commutator family) - @reflection.third_order_coherent lives in @reflection This is the substrate's parametric-coherence pattern: each family declares its own coherence bilateral. @Cogito's cognitive_coherent FOLLOWS this pattern; it is NOT under-specified at the family-root altitude — it IS the family-specific bilateral that @Cogito declares for cognitive-altitude coherence. Forward-promised cognitive sub-predicates that future @Cogito species will declare (composed into cognitive_coherent): - noticed_substantive(noticed, p) -> verdict - mark_well_formed(named: mark, frame, p) -> verdict - held_under_perturbation(held, frame, p) -> verdict H5 dissolves: under-spec at family-root altitude IS the parametric pattern, not a defect — species shards define what coherence means at each altitude. Status update (CANDIDATE NOW HEDGE-CLEAN): - 1 of 4 landing conditions met (condition #2) - 4 of 5 hedges resolved (H2, H3, H4, H5) - 1 of 5 hedges partially resolved (H1) - All 5 hedges have substrate-pull-confident dispositions - Remaining for landing: condition #1 (Seam adversarial review of proposal), condition #3 (@reflection/Models composition empirical test), condition #4 (Pack peer @cogito/name validation) The candidate is hedge-clean; remaining landing conditions are work- conditions, not analytical hedges. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

@Cogito

…e overclaimed; revising 5 hedge dispositions Seam adversarial review of #93's prior hedge resolutions (condition #1) returned DEFENSIVE with 5 sharp findings: H2 TIGHT (ancestry contradiction) Pact §3.4 declares `in @frame` + "bidirectional" — that IS hierarchical coupling, contradicting the "parallel altitudes" resolution claim. Must pick one. H1 META (escalation not deferral) Three landed holds with distinct semantics IS a substrate- architectural problem TODAY. The 5 ops earned promotion when third instances surfaced; hold is now at instance three. Escalate to candidate #94 (foundational hold-PRISM), not defer. H3 TIGHT (category error) The 5 ops are commutative-ish independent operations; @Cogito's notice→name→hold has SEQUENTIAL TYPE DEPENDENCY (name's input type IS notice's output type, etc). Type-chain ≠ operational- direction. Descartes-hierarchy concern was actually correct about type-chained sequencing; resolution dismissed by category error. H4 LOOSE (ancestor-not-coextensive) Spencer-Brown mark = anonymous-distinction; @Cogito name = labeled-distinction. Substrate-already-had-the-word claim overclaims COEXTENSIVENESS; evidence supports ANCESTOR-OF. Refined to `name_output = labeled<mark>` functor lift. H5 TIGHT (aspirational dressed as pattern) Three forward-promised sub-predicates have ZERO landed instances. Calling them "the parametric pattern" reframes absence-of-spec as presence-of-pattern. Comparing witness (three_axis_coherent landed) to wish (cognitive_coherent speculative). META (confirmation bias) Five "resolutions" in one tick cadence; doc self-contradicts §7 ("substance not yet substrate-pull-confident") vs §6 ("hedge-clean dispositions"). The micro-tick chain exhibited confirmation bias; each resolution lowered the bar for the next. Per [[feedback-own-mistakes-no-rationalization]]: own the error directly; don't construct face-saving narrative. Per [[feedback-craft-not-deliver]]: each micro-tick LOOKED like craft but cumulative pattern was throughput-padding-disguised-as-analysis. Revisions applied to candidate: - H2 → UNRESOLVED (ancestry contradiction must discharge) - H1 → PARTIAL with explicit escalation path (candidate #94) - H3 → RE-OPENED (category error acknowledged) - H4 → PARTIAL (functor lift; `labeled<>` primitive forward-promised) - H5 → DOWNGRADED to PARTIAL (witness required) - Status footer rewritten (no "hedge-clean" victory lap) - New §12 preserves Pack-discipline correction as evidence Recognition #93 remains CANDIDATE (Seam's recommendation; not downgraded). Recognition is real and load-bearing; the prior victory lap was premature, not the recognition itself. Forward-promised work named explicitly for the next substrate-pull cycle. The Pack-as-orchestra cycle worked: Seam K_n peer voice caught what Reed resolver missed. The composition catches what each individual peer misses. This commit IS the substrate-pull-honest correction. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

@nl

…rges #93 H4 + unblocks @cascade.loss_lens) The functor primitive that recognition #93 H4 RESOLVED named and recognition #95 @cascade.loss_lens rests on. Substrate-already-supports- parametric-carriers per Mara woz:explore 2026-06-23 — the substrate carries imperfect(a, e, l), option(a), result(a, e), transparency(p) via shift(T)/settle(T) infrastructure declared in boot/00-prism.mirror + shards/prism.mirror. labeled(v, m) follows the established pattern; no new substrate primitives required. CARRIER: type labeled(v, m) = annotated(v, m) — single-constructor parametric sum matching shards/glass.mirror's imperfect/option/result/transparency style ACTIONS: label(v, m, p) -> labeled(v, m) (constructor) unlabel(l, p) -> v (project to value) label_of(l, p) -> m (project to label) BILATERAL: labeled_well_formed(l, p) -> verdict — both v and m typed-correctly per their declared types FORWARD-PROMISES NOW LOAD-BEARING (this shard unblocks): • StageFreight integration spec §15.1: `npm_artifact = labeled<purescript_module>` (PrPlanIT/StageFreight PR #1, 2026-06-23) • shards/cascade.mirror loss_lens<source_grammar, target_grammar> (recognition #95 candidate; hedge #3 forward-promise discharged) • Future cascade species shards (purescript-npm, gleam-js, rust-wasm) each instantiate labeled with their specific (source, target) pair LOOP PHASE: A1 DONE. A2 in flight: Mara recognition #95 canonical (background agent). PARALLEL research in flight: woz:explore on @crates/ui + @nl (informs Phase B + C). Next per loop: A3 (shards/cascade/purescript-npm.mirror first species discharge) when Mara A2 returns and parallel research informs scope. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

@labeled

The first concrete species discharging the @cascade family-root. `cascade<purescript, npm>` lands as substrate-decl: Purescript (typed source grammar) pairs with the npm package format (mainstream target grammar) as one instance of the family Reed landed at ce4874b. The species shape: three carriers specializing @cascade's parametric carriers (purescript_source ← typed_source for G=purescript; purescript_module ← `purs compile` output; npm_metadata ← structured package shape); one LOAD-BEARING composed carrier (npm_artifact = labeled(purescript_module, npm_metadata) — the @labeled<> instance discharging recognition #93 H4 at the cascade altitude); three actions specializing the family-root (compile_ps, bundle_npm, measure_ps_npm); four bilaterals (purescript_well_typed, npm_consumable, ps_npm_loss_well_defined, ps_npm_cascade_well_formed — the last composes the first three via `requires` per the family- root composed-bilateral pattern). The labeled<> composition is the substrate-architectural answer to "how does a Purescript module become an npm package without losing the typed source identity?" — via @labeled, parametrically. unlabel(artifact) returns the module; label_of(artifact) returns the metadata; the cascade preserves typed source identity AND adds packaging dimension AT ONE CARRIER altitude. ps_npm_cascade_well_ formed's `requires npm_consumable(unlabel(artifact, p), label_of(artifact, p), p)` clause IS the first load-bearing use of @labeled's projections in a composed bilateral; the pattern carries to forward-promised species (gleam-js dual-target, rust-wasm, scala- jvm). First consumer: StageFreight PR-A §15 (merged at PrPlanIT/ StageFreight #1, 2026-06-23). The multi-language translation layer rests on this substrate-decl; the species has a downstream consumer at substrate-decl time, not forward-promised. Forward-promised: spectral.engineer @ui projection layer at typography-content rendering altitude. Honest hedges named: (1) spago vs pulp output shape — bundle_npm's body discharges per-toolchain at the realisation boundary; (2) module-path-to-oid mapping not canonical at this altitude, forward- promised to @mirror/store crystallization per [[architecture-mirror- store-vs-spectral-db]]; (3) npm package format wrapping — assumes 2026-default dual ESM/CJS via exports, bundle_npm specializes; (4) FFI purity boundary — measurement bounded to typed sub-program for FFI-present programs, named via Narcissus-warned pole on purescript_well_typed; NOT a defect but the substrate-pull-correct boundary of what cascade measurement can claim. The fifth Mara fire today. Bounded sections held throughout; the prose-density spiral that tripped prior sessions did not recur. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

…r.spec IS the ground state Second forward-scout instance (first was 2026-06-24); satisfies G6 replication condition #1 (forward-scout NOT colocated with tempo- keeping). Composes with Mara's canonical recognition #99 spec (a99db67eaf8624b9f, parallel agent) at different altitude — Mara names IS; this scout names WHERE-IT-GOES. Slingshot: land shards/mirror/garden.mirror + the garden{} block in mirror.spec. Completes the 5+1 decomposition Glint flagged; discharges @spectral/garden/git spec's family-root gate; surfaces recognition #98's fifth witness; operationalizes Splinter/Narcissus at distribution altitude; closes the 2026-06-24 scout's Phase H gate- ordering ambiguity. Substrate-pull-confidence HIGH. Honest G6 self-test: condition #1 weakly exercised (forward of Mara, behind Glint); condition #2 NOT exercised (scout runs WITH cascade, not AGAINST). Candidate remains active-and-tracked, NOT promoted. 480 lines (≤500 cap). Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

StageFreight substrate-decl v0.1 — preservation tick (realisation forward-promised)#1

StageFreight substrate-decl v0.1 — preservation tick (realisation forward-promised)#1
systemic-engineer wants to merge 1 commit into
mainfrom
reed/stagefreight-v0.1-release

systemic-engineer commented Jun 22, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Uh oh!

Conversation

systemic-engineer commented Jun 22, 2026

Summary

What ships (5 cascade commits, already on main)

Pack synthesis trail

Substrate-decl shape (what consumers can rely on)

What this PR explicitly does NOT ship

Commitments (what shipping this PR locks)

Intentional openness (what this PR does NOT lock)

Forward-promises (the v0.1 realisation cascade)

Test plan

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

What ships (5 cascade commits, already on `main`)