Repository navigation
docs: record repository policy revisions in the ledger and render them on their own page - #230
Merged
Merged
Conversation
…m on their own page Remote baseline: origin/main @ 4fb5271 Scope: CHANGELOG.md interleaved 49 repository policy revision entries with the version entries that users read for changes and required actions. The policy ledger evidence/repository-policy-revisions-v1.json already records every revision, so the changelog now keeps version entries only and says where revisions live. A new docs/repository-policy-revisions.md renders the ledger as a table inside a managed marker region, newest revision first, and preserves the 49 moved entries unchanged below it, with their repository-relative links adjusted for the new location. The runtime-identity validator renders and checks that region the way it checks docs/runtime-identity.md, scripts/render-release-facts.py renders it, and the Release pipeline's catalog handoff writes the page and no longer inserts a changelog entry; it still dates the released version's heading and appends the ledger revision. The documentation index, repository governance, the release documentation contract, and the documentation policy name the page and the rule. Tests cover the handoff, the stale-page rejection, the render CLI, and the new document counts. Repository policy revision 117 records the change for Issue #219 in the ledger only, with an unchanged plugin version and runtime digest. Validation: python3 -B scripts/check-publication.py: passed on the exact tree (153 required files, 169 Markdown files, 30 immutable action pins) python3 -B scripts/render-release-facts.py --check: passed (45 release-fact surfaces, the policy ledger page included) python3 -B -m unittest discover -s tests -p 'test_*.py': 312 tests OK in a disposable clone of the tree git diff --check: clean; ASCII scan of the changed Markdown and JSON files: passed
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.
Scope
Refs #219.
CHANGELOG.mdinterleaved 49## Repository policy revision Nentries with the 77 version entries, so a user looking for what changed for them had to skip repository-process entries. The policy ledgerevidence/repository-policy-revisions-v1.jsonalready records every revision. The changelog now keeps version entries only and states where revisions are recorded. A newdocs/repository-policy-revisions.mdrenders the ledger as a table inside a managed marker region (newest first, with the source Issue, baseline commit, and summary) and preserves the 49 moved entries unchanged below it; their repository-relative links are adjusted for the new location. The runtime-identity validator renders and checks the region the way it checksdocs/runtime-identity.md,scripts/render-release-facts.py --renderrewrites it, and the Release pipeline's catalog handoff writes the page instead of inserting a changelog entry while still dating the version heading and appending the ledger revision.This change is the first revision recorded under the new rule: revision 117 has its ledger row and this pull request, and no changelog entry. The plugin version and runtime contract digest are unchanged.
Affected files and surfaces
docs/repository-policy-revisions.md(new);CHANGELOG.md(49 entries moved out, header sentence);axiom_validation/runtime_identity.py(ledger rendering and surface check);axiom_validation/release_pipeline.py(handoff writes the page, no changelog entry);scripts/render-release-facts.py;docs/README.md,docs/repository-governance.md,docs/maintainers/release-documentation.md,docs/maintainers/documentation-policy.md;tests/test_release_pipeline.py,tests/test_runtime_identity.py,tests/test_release_facts.py,tests/test_documentation.py;evidence/repository-policy-revisions-v1.json,evidence/runtime-identity.json,evidence/release-status.json,docs/runtime-identity.md(revision 117)Routing and authorization impact
Documentation
docs/repository-policy-revisions.mdis indexed fromdocs/README.mdand linked fromdocs/repository-governance.md; the Changelog Contract indocs/maintainers/release-documentation.mdand the ownership table indocs/maintainers/documentation-policy.mdstate the rule. Installation and hook commands are unchanged.Validation
python3 -B scripts/check-publication.pypython3 -B -m unittest discover -s tests -p 'test_*.py'git diff --checkpython3 -B scripts/render-release-facts.py --check: passed with the policy ledger page included; the handoff test proves the rendered page gains the new revision row and the changelog gains no policy entry; a stale ledger rendering is rejected by the runtime-identity check. ASCII scan of the changed Markdown and JSON files: passed.Cross-platform parity
Unrelated work