Skip to content

docs: record repository policy revisions in the ledger and render them on their own page - #230

Merged
wheakerd merged 1 commit into
mainfrom
feature/policy-revisions-ledger-page
Oct 30, 2026
Merged

wheakerd merged 1 commit into
mainfrom
feature/policy-revisions-ledger-page

Conversation

@wheakerd

Copy link
Copy Markdown
Owner

Scope

Refs #219. CHANGELOG.md interleaved 49 ## Repository policy revision N entries with the 77 version entries, so a user looking for what changed for them had to skip repository-process entries. The policy ledger evidence/repository-policy-revisions-v1.json already records every revision. The changelog now keeps version entries only and states where revisions are recorded. A new docs/repository-policy-revisions.md renders 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 checks docs/runtime-identity.md, scripts/render-release-facts.py --render rewrites 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

  • Shared files: None
  • Codex-specific files: None
  • Claude Code-specific files: None
  • Documentation or validation files: 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

  • Route-selection impact: None. No skill text changes.
  • Action-authorization impact: None. The catalog handoff writes one more documentation file in the same signed pull request; it gains no permission.
  • New or changed stop conditions: None.

Documentation

docs/repository-policy-revisions.md is indexed from docs/README.md and linked from docs/repository-governance.md; the Changelog Contract in docs/maintainers/release-documentation.md and the ownership table in docs/maintainers/documentation-policy.md state the rule. Installation and hook commands are unchanged.

Validation

Command Result
python3 -B scripts/check-publication.py Passed on this exact tree: 153 required files, 169 Markdown files, 45 canonical release-fact surfaces, 30 immutable external action and image pins
python3 -B -m unittest discover -s tests -p 'test_*.py' OK in a disposable clone of this tree: 312 tests
git diff --check Passed
Additional targeted checks python3 -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

  • Shared skill changes were reviewed against Codex and Claude Code, or this change does not affect shared skills.
  • Manifest, marketplace, and hook differences remain intentional and documented.
  • Optional host-native validation results include the host/tool version, or are marked unavailable.

Unrelated work

  • I reviewed the final diff and did not reset, hide, stage, or rewrite unrelated work.
  • I did not add generated caches, disposable validation copies, local maintenance notes, or tool output.
  • I called out every affected file and any routing, authorization, documentation, or parity impact above.

…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
@wheakerd
wheakerd merged commit e88e306 into main Oct 30, 2026
10 checks passed
@wheakerd
wheakerd deleted the feature/policy-revisions-ledger-page branch October 30, 2026 09:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant