docs: reconcile RELEASING.md + .gpd/STATE.md with live v0.1.0 release#5
Open
Zer0pa-Architect-Prime wants to merge 1 commit into
Open
docs: reconcile RELEASING.md + .gpd/STATE.md with live v0.1.0 release#5Zer0pa-Architect-Prime wants to merge 1 commit into
Zer0pa-Architect-Prime wants to merge 1 commit into
Conversation
Closes the governance drift flagged by the FPO Wave-2 R5 review: both
docs still claimed v0.1.0 was a local-only internal tag with
OWNER_DEFERRED licence, while the public custody-only release v0.1.0
(cuneiform-control 0.1.0 Apache-2.0 on PyPI, GitHub release 2026-05-04)
has been live since 2026-05-04T01:44:58Z.
The reconciliation distinguishes the two release types that have
collapsed in the prior wording:
- **Custody-only public release** (what v0.1.0 actually is):
manifest-validation control pack; preserves NO_GO_GOVERNING_GATE_UNMET
verbatim; no decipherment claimed; no image-bearing corpora
redistributed; Apache-2.0 (code) + CC-BY-4.0 (docs).
- **Scientifically-repaired public release** (still not allowed):
requires repaired governing gate on new scientific evidence and an
extracted rerun surface beyond manifest validation.
The failed-gate boundary discipline is unchanged. Smoke PASS, HF custody
pinned, NO_GO_GOVERNING_GATE_UNMET still authoritative. No code or proof
artefact changes — pure documentation reconciliation.
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.
Summary
Closes the governance drift flagged by the Wave-2 FPO/Repo review (R5): both
RELEASING.mdand.gpd/STATE.mdstill claimedv0.1.0was a local-only internal tag withOWNER_DEFERREDlicence, while the public custody-only releasev0.1.0has been live on GitHub + PyPI since 2026-05-04T01:44:58Z (cuneiform-control0.1.0 Apache-2.0 via Trusted Publishing).The reconciliation distinguishes the two release types that had collapsed in the prior wording:
v0.1.0actually is): manifest-validation control pack; preservesNO_GO_GOVERNING_GATE_UNMETverbatim; no decipherment claimed; no image-bearing corpora redistributed; Apache-2.0 (code) + CC-BY-4.0 (docs).Scope discipline
RELEASING.md+.gpd/STATE.md. No code, no proof artefact, no smoke-runner changes.NO_GO_GOVERNING_GATE_UNMETremains authoritative; smokePASSrecorded; HF custody pinned.v0.1.0-internalstaging tag record is preserved for traceability; the public custody-onlyv0.1.0release record is added alongside it.Test plan
RELEASING.mdand.gpd/STATE.mdno longer assertOWNER_DEFERREDlicence or "tag not pushed" while v0.1.0 is publicly liveNO_GO_GOVERNING_GATE_UNMETanywhere in the diffTruth basis
main:3d29caa(2026-05-04T01:34:04Z)## Live Status,pyproject.toml,LICENSE,CITATION.cff,.zenodo.json— all consistent on Apache-2.0 + custody-only scopeLANDING_CARD_WAVE2_CENTRAL_DISPATCH_BRIEF_2026-05-08.md§B row 459 (R5);FPO_DISPATCH_BRIEF_PRODUCT_PAGE_2026-05-09.md§A line 335 ("Repo fixes required: reconcile RELEASING.md /.gpd/STATE.mdgovernance drift")