Program contract route
Inspect the records that give all five repositories the same exchange vocabulary while preserving each repository's authority.
Source revision 4e0e48f52a4ce0de1963d1c6bfe404b76a75879a · standing clean
Release identity
The signed spec-v0.3.1 tag exists, and accepted Governance 2.1.0, Implementation 0.3.2, Simulation, and Comparison release subjects are bound with their selected-future semantics. The living Program carriers remain candidate_pending_promotion until the hosted sibling proof and post-tag release observation settle.
Records maintained here
The release-role record states what this repository owns, the living candidate status, its contract links, the standing branch controls, and the release-specific review route. Its pending Program coordinate represents the open post-tag observation.
Open exact sourceThe constellation record names all five repositories and the behavior each one owns.
Open exact sourceThe lock records each accepted sibling release subject and its decision-changing semantic bindings. The Program placeholder remains until the post-tag observation records the permanent commit and tree in the living carriers.
Open exact sourceThe version-specific record starts with planned post-tag evidence fields and later carries the signed Program subject, hosted proof, merge admission, independent review, and GitHub review record from a separate observation commit.
Open exact sourceThe packaged catalog gives implementation, simulation, and comparison work one versioned operation vocabulary.
Open exact sourceThe synthetic journey gives producers one executable scenario with a stable identity and one content digest used by every consumer.
Open exact sourceThe closed schema defines the decision-relevant result shape that both producers can project while retaining their own evidence detail.
Open exact sourceThe records above establish the program vocabulary and the candidate coordinates declared at this revision. Running behavior, selected-future behavior, comparison results, and governed schema interpretation remain with the repositories that own those observations.
These links open the full Git revision that produced this page.