M16 — Intra-Shot Persistent Consequences

M16 — Intra-Shot Persistent Consequences

Milestone release covering the M16 product implementation in PR #21: six review-gated slices (P0/A/B/C/D/E), the frozen R7 plan revision, the authorized exec_08 MaterializerContract recertification, and the post-closure publication layer (README refresh + boundary carves).

The certified implementation identity is the branch head inside the merge, not the merge commit itself; the squash tree is byte-identical to the publication head's tree.

Identity

Tag	M16 — annotated (object 4a890260448021419168ea51da6321d5b1e3867c)
Published main commit	488031a2b7d0070d23425bbe04b86d9f9f16e0bd — PR #21 squash
Published main tree	a2a3c3e480d20b10e472812505e4370a865a8d6d
Certified implementation head	9e703806304063110a07458c3d3e0b0124c6ab14
Certified implementation tree	ca52da2629502ac813538854bd812f2886a99c7b
Frozen plan	R7 — SHA-256 fde28502b8aff0a5a418d1d31d8da82efa034db50b92f48a9fba1a8fe6e6b240
R6→R7 delta	SHA-256 c15459a5af267a3f27ad367ba9110a77a846ff6f2aa26c6b62e669424764bbf7
Migration head	0017_m16_intra_shot_consequences
MaterializerContract live pin	963e3a035c202d4a906e6a9b86cc416895987f6a652aa0b19d94ee7538e6925c

CI gates

Run	Scope	Result
#149	closure gate on certified 9e703806	PASS
#150	publication gate on 44936bf	PASS
#151 (attempt 2)	post-merge on main @ 488031a2	PASS — backend 2477/20, frontend green

Certification battery (beyond CI): identity-guarded §28.2 ×2 on the certified machine — backend 2490 passed / 7 skipped in both runs, all 18 predecessor+M16 validators, both residue checks, bracketed by exact head/tree/clean-worktree guards — plus exec_08 through the real certified ComfyUI executor. Evidence bundle manifest d5b76ddd… (96/96 files verified).

What M16 delivers

Intra-Shot persistent consequences: events with exact before/after state chains and deterministic folds per target domain (entity feature / entity relation / Production Instance feature); terminal-state and Shot/end handoff equality; the fail-closed readiness gate on the working snapshot; immutable proposal ingestion (Grammar v1, exact source ShotRevision/Generation/Take provenance) and explicit consequence review/adoption — direct and batch, under the R7 five-field event-review basis grammar; connection-scoped transition authoring with create-or-exact-match convergence; schema-7 Shot capture with immutable intra-shot companions and historical re-fold; the fail-closed generation fence refusing to execute schema-7 authority; 0017 recovery verification at full M16 depth; and the Shot event-timeline / consequence-review UI as a pure server projection.

The R7 plan revision resolved a frozen-plan contradiction (the direct-review working-snapshot fence vs. §9.2 unavailability) by removing the field from the direct-review basis — documented in the committed R6→R7 delta record.

Slice ledger

Slice	Certified head	Closure
M16-P0 / M16-A	f7107d6	2026-09-16
M16-B	4dcb69e	2026-09-16
M16-C	081ef14	2026-09-17
M16-D	db8815d	2026-09-18
M16-E	c53d202	2026-09-18
exec_08 recertification	f08e27d	2026-09-18

M15 — EVOLVE THE WORLD: Safe Reusable-Revision Evolution

M15 — EVOLVE THE WORLD: Safe Reusable-Revision Evolution

Milestone release covering the M15 product implementation in PR #19 and the post-M15 review-remediation publication in PR #20.

The final published baseline is the post-remediation main commit, not the earlier product-only merge.

Identity

Tag	M15 — annotated
Commit	30ea135f3b2339491e9b36eaee2d0d8bc4ab8585
Tree	db21568a3522a5ed2fa6fab44d1f9741d6d71ad2
M15 product merge	3d166bb320f3686e913faf1fa613bd05429320f7 — PR #19
Final remediation merge	30ea135f3b2339491e9b36eaee2d0d8bc4ab8585 — PR #20
Migration head	0016_m15_revision_compatibility

What M15 delivers

M15 introduces compatibility-gated evolution of reusable immutable Production Revisions without rewriting historical Shots or introducing a mutable global “current asset” pointer.

It provides explicit source/target compatibility assessment, deterministic-translation handling, set-oriented impact discovery, occurrence revision tracking, compatibility-gated application to current working occurrences, immutable historical preservation, and explicit revision-update operations.

The final publication additionally includes the review-remediation hardening required before release: schema-3 control-graph integrity and collision protection, exact transport-byte verification, recovery/history verification, shared ControlNet-loader handling, hardened SQLite recovery URIs, production-world error rendering, and historical-boundary proof corrections.

Evidence

• M15 frozen proof map: 127/127
• Exact final PR-head CI #79 (34851439162): Backend + Frontend success
  • backend: 2270 passed, 20 skipped
  • frontend: 137/137
  • typecheck, production build, security audit green
• Post-merge main CI #80 (34855331701): success on exact commit 30ea135f...
  • all predecessor, M11, M12, M13, hygiene, next-security, M14, and M15 validators green
  • backend: 2270 passed, 20 skipped
  • post-suite residue gate green
• PR #20 final tree is byte-identical to the published merge tree
• All PR #20 inline review findings were dispositioned before merge

Product claim boundary

SoloRing can evolve reusable production assets during a film through explicit compatibility assessment and controlled adoption while preserving occurrence identity, persistent state, consuming contracts, and immutable historical Shots.

Newer Production Revisions do not silently replace historical or current uses merely because they exist.

M14 — SHOOT THE WORLD: World Observation Compilation and Execution

M14 — SHOOT THE WORLD: World Observation Compilation and Execution

Milestone release for PR #18 (squash merge 89298e793c651e9e8b9164912c76e3595867a60a, parent exactly 20429b3, published tree 3c4fec0bdb11732f0c77c22acc65d3ba882df393 — byte-identical to the final PR head 6652d5d tree). Implementation against frozen plan R2 68f910f5… + Erratum E-1 4acadcc6….

Identity

Tag	M14 (annotated, object ff4c6107876ddd991ec626b3605deb143ec7daf9)
Commit	89298e793c651e9e8b9164912c76e3595867a60a
Tree	3c4fec0bdb11732f0c77c22acc65d3ba882df393
Final PR CI	run 34639348757 — Backend + Frontend success on the exact merge head

What M14 delivers

Compiles an exact captured reusable production world into a supported production execution path: WorldObservationSpec schema 1, profile schema 3 + capability negotiation (Erratum E-1 verdict law), WorkflowSpec schema 4 wrapping the exact schema-3 execution meaning, the retained structural-mesh consumer with set-oriented closure loading and B1 resource caps, convergence-unique derived observation storage (migration 0015), the mesh-depth materializer reusing the certified M10 rasterization seam (contract 9e5526b1…), the wan21_spatial_v1 v2 production release (descriptor 4 / profile 3), worker historical execution with integrity replay, the §31 observation readiness + historical inspector API surface, and feature-film-scale proofs.

Evidence

• Proof map: 90 TEST / 0 PENDING under M14_REQUIRE_COMPLETE=1
• Real GPU source gate (EXEC:08–10) executed on the certified executor (ComfyUI b963f4ad + ComfyUI-WanVideoWrapper 088128b2): retained production geometry drove Wan/ControlNet, produced Takes under two new cameras, with zero production-authority mutation and byte-exact submitted control frames
• §52 production evidence record SHA-256 4f67d7752d746629bbaa6f7ee35544e4946af94a494002bbf3851c12e6dd212b (external file; reported evidence — not independently hashable from GitHub)
• Historical integrity: the schema-4 worker delegates the inherited M10 closure to the shared predecessor verifier — the shared predecessor verifier proves inherited artifact-id equality, while EXEC:07 proves the carried entity transports preserve captured key/position/Blob identity
• Five independent source-review rounds (each correction a single normal child commit), PR review PASS, post-merge identity verified (main tree == PR head tree)

Product claim boundary

SoloRing can compile an exact captured reusable production world into a supported production execution path, preserve declared hard structural properties through mechanically bound controls, and refuse executor paths that cannot honor the captured requirements. SoloRing has feature-film-level reusable-world continuity architecture with one real structural production execution path.