anchor-canon: release seven anchor documents at canonical v1.0#23
Merged
Conversation
…HEAD
Rebuilt all seven canonical-v1.0 anchor PDFs from papers/main HEAD (post #61
WP002 concordance regen, post #62 WP005 final polish, post #63 WP004 emergency
polish). Every prior PDF in this worktree was stale by at least one polish
cycle. Replaced PDFs in place and ran scripts/build_manifests.py to regenerate
manifest.json files plus the root catalog (catalog/publications.{json,yml,csv},
catalog/checksums.{sha256,sha512}, publications.yml).
Refreshed sha256 prefixes (papers/main HEAD = 07710fe):
c001 eaefe680 -> 0f547c4a 26 pages, 327,217 bytes
wp000 8caa1e83 -> cc65cae4 4 pages, 503,736 bytes
wp001 7a575fc1 -> 050e986c 26 pages, 2,445,801 bytes
wp002 dc22657b -> 91e53a7c 50 pages, 412,045 bytes
wp003 f0aa1bc0 -> f63cf77a 37 pages, 294,691 bytes
wp004 bc82d22f -> 835578e7 23 pages, 545,965 bytes
wp005 98f3d00c -> cb2067b7 35 pages, 324,239 bytes
Note: scripts/verify_publications.py reports source-byte mismatches against
site/assets/pdfs/anchor-documents/ — expected, the site repo deploy is the
next step in this release wave (Phase D of the anchor-canon v1.0 deployment
plan). Will reconcile once site/main carries the same bytes.
OpenTimestamps blocks remain status:missing across all seven; stamping is a
separate scripts/stamp_publications.py invocation, scoped as a follow-up.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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
This PR ships the canonical v1.0 release of all seven anchor documents to the public publications shelf. It is Phase B of the four-repo anchor-canon v1.0 deployment wave: build → publications → corpus → site → editorial pass.
The branch was already 9 commits ahead of `main` with the seven anchor docs assembled across earlier sprints (#14–#21). The latest commit on this branch refreshes every PDF and manifest against the current `papers/main` HEAD, so the published bytes match the post-polish artifacts that just landed in `papers` (#61 WP002 concordance regen, #62 WP005 final polish, #63 WP004 emergency polish).
Refreshed sha256 prefixes (papers/main HEAD = 07710fe)
Per-document provenance preserved
This branch's commit history retains the per-paper assembly trail (#14–#21 + WP000 release commit). The final refresh commit (`526b618`) atomically bumps all seven manifests against the post-polish PDFs. Use `gh pr merge --merge` (true merge, not squash) so the per-document provenance survives in `main`.
What this PR does
What this PR does NOT do
Test plan
🤖 Generated with Claude Code