ci: bind registry parity before release admission - #29
Draft
abrichr wants to merge 5 commits into
Draft
Conversation
abrichr
force-pushed
the
codex/release-admission-order-20260820
branch
from
August 20, 2026 16:32
a25dba5 to
ff6e876
Compare
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
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.
Summary
vX.Y.Ztag the one authoritative publish event; publishing the GitHub Release cannot start a second publisher runserver.jsonvalidates against the exact MCP2025-12-11schema bytes and pinned SHA-256Authority and evidence boundary
The candidate says
not_admitted. It contains no admission ID, release identity, or Production channel selector. PyPI latest and MCP latest are parity evidence only. The signed active ledger inOpenAdaptAI/.githubremains the sole Production authority.The Actions artifact is a temporary transport copy, not the durable evidence record. Before activation, the central process must verify its exact digest and copy it with the supporting release evidence into the immutable evidence store. If the handoff expires first, registry parity must run again.
This PR stays draft because the central admission ledger has no active Agent admission. A future release still needs independent acceptance evidence and an active signed central admission. The activation path must also confirm that the current public defaults still equal the candidate before it admits the release.
Validation
3fba09590c99f61735d234822279f4223fab9e300c0a81e81c91ab62a4114de0No package, MCP record, release, or Production admission was published by this PR.