Close superseded Morphogenesis transitions and publish v0.5 evidence - #184
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
An approved Morphogenesis proposal can activate owner effects and then lose the morphology-head CAS. The old execution could remain nonterminal after application cleanup. This change adds an opt-in, authoritative direct-successor check and a durable checkpoint → fence → drain → budget-release path ending in
superseded, with its own receipt and no change to the winning head.Adds workflow compensation and authority-neutral Room projection, preserves original fence timestamps on reconciliation, and includes a runnable PostgreSQL Room/Team/Work example. Legacy records retain their digest/field set. Prepares the coordinated 65-package beta.9 release; npm publication still uses protected staging and human approval.
The paper v0.5 and its new evidence are separate from frozen v0.4 results: 36 shared-owner authority/recovery cells, independently implemented evidence verification with mutation controls, a persistent losing-transition trace, and a bounded TLA+ model (260 distinct states) with three failing variants. The manuscript reports the durable-baseline tie and explicitly leaves full comparative P5 contention coverage open.
Validation before PR: 59 Morphogenesis tests, 9 verifier tests, 28 release/version tests, public API type-check, focused package type-check, public-surface audit, persistent PostgreSQL example, and TLC. Full repository checks run locally and in CI. No production reliability, LLM intelligence, or formal implementation-refinement claim is made.