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
mainCI #80 (34855331701): success on exact commit30ea135f...- 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.