v5w2-w8b(release-lines-verify): Release Lines on /verify/taulib/ + Formalization Release Lines table on /verify/release-manifest/#270
Merged
Conversation
…ib/ + Formalization Release Lines table on /verify/release-manifest/
Source: atlas/website/v5/panta-rhei-release-lines-formalization-
surfaces-v5-addendum.md §7 (TauLib Release Lines) + §9.2
(Verify lane TauLib representation) + §9.3 (Release Manifest
representation) + §8.4 (Proof Package States).
Data: _data/release_lines.yml · formalization_release_lines +
proof_package_states + citation_status enum (shipped W1).
Roadmap: atlas/website/briefings/v5/v5-next-wave-roadmap-2026-05-23/
README.md (W8 · Release lines + TauLib v2/v3 + cross-links — PR 8b).
Closes Wave 8 and the v5 next-wave cycle.
══ What lands ════════════════════════════════════════════════════════
verify/taulib/index.md (+35 / 0)
────────────────────────────────
New "## Release Lines" section inserted between "TauLib inside the
verification matrix" and "What Verify still owns". Three-tile grid
framed as the inspection-bridge view (parallels W8a's Corpus-side
framing but from the trust-boundary angle):
TauLib v2 Snapshot — Citable as a proof basis. Reproduction
instructions clear (clone pinned commit,
re-run lake build).
TauLib v3 Library — Active restructure · not yet citable.
Current Results cite v2.
Proof Packages — Per-result · 5-state lifecycle. Released
packages are citable per result.
Closing block re-states the IA §9.2 core warning verbatim: Lean
compilation checks formal obligations; it does not establish
empirical truth, bridge adequacy, or external scientific
acceptance. Cross-links to /verify/verification-framework/ +
/verify/how-to-verify/ for the broader inspection questions.
Doctrine comment block above the section pins both §7 + §9.2.
verify/release-manifest.md (+36 / 0)
────────────────────────────────────
New "## Formalization Release Lines" section inserted between
"Release identity" and "Build status — summary". Canonical four-
row table per Addendum §9.3:
| Surface | Corpus Relation | Status | Public | Citable |
|----------------------|-----------------------------------|-------------------|---------|------------|
| TauLib v2 snapshot | Corpus v2 / Second-Edition comp. | frozen | ✓ | ✓ |
| TauLib v3 library | Corpus v3 working line | active restructure | not yet | no |
| Proof packages | per-result | per package | varies | per package|
| Citation status enum | cross-cutting | enum: 4 values | ✓ | per artifact |
Two explanatory paragraphs below the table:
· Proof package states — five-state lifecycle (in_construction →
draft → candidate → released → superseded), only released is
citable.
· Citation status enum — four values per Addendum §3 vocabulary
(citable · active_working · private · deprecated), surfaced on
every Research Graph entry.
Anchor: <a id="formalization-release-lines"></a> — used by deep-
links from the Corpus + Verify TauLib pages and by W8a's Research
Modules / Proof Packages tile.
Cross-links to Research Graph §rg-software (W6a) where the same
data appears as graph entities, and to the right-rail identifier
boxes (W6b) which render the relevant table row inline on every
TauLib + proof-package page.
══ Three-surface model now fully realised for formalization ═════════
Per IA §10.3, the program's authority/provenance layer is exposed
through three surfaces. Wave 8 closes the formalization slice of
this model:
Surface 1 (machine-readable JSON-LD):
Already shipping per-page (W6a Schema.org per page-type) +
the JSON projection at /assets/research-graph.json (W6a).
Surface 2 (human-visible identifiers):
Identifier boxes on every TauLib entity page (W6b — auto-
match against the research-graph manifest).
Surface 3 (authoritative page):
This PR — /verify/release-manifest/#formalization-release-
lines is now the authoritative table for the formalization
release-line picture; the Corpus + Verify TauLib pages
(W8a + W8b) link here.
══ URL preservation posture ═════════════════════════════════════════
Purely additive — no existing URL changes, no existing content
removed or hidden on either page. Build status / Per-book
reconciliation / Reproduction instructions / Next release targets
on the Release Manifest all preserved; What Verify still owns /
Inspection routes on /verify/taulib/ all preserved.
══ Gates run locally ════════════════════════════════════════════════
✓ scripts/check_hardcoded_release_numbers.py
✓ scripts/check_release_manifest_parity.py
✓ Forbidden-strings pre-commit hook
· Jekyll build deferred to CI (local Ruby mismatch)
══ Cycle close ══════════════════════════════════════════════════════
Wave 8b closes the v5 next-wave cycle. Eight waves · 12 PRs ·
shipped over a single working session. All three v5 doctrine
documents (IA Doctrine v5, Publication Taxonomy v5 Supplement,
Release Lines + Formalization Surfaces v5 Addendum) are now
realised on the public site.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
…aseline for new Formalization Release Lines PR #270 verify gate failed: registry_verify --full ❌ 1 error(s): • RELEASE MANIFEST NEW UNBASELINED SECTION: 'Formalization Release Lines' scripts/registry_verify.py:117 enforces that every section heading in verify/release-manifest.md appears in the saved baseline at _data/registry/release_manifest_sections.yml. The baseline is auto- extracted by registry_preserve_prose.py and stores section text + SHA-256 checksums to catch stale or accidentally edited prose. The new "Formalization Release Lines" section shipped in the parent W8b commit (32bf81f) is doctrine-prescribed (Release Lines + Forma- lization Surfaces v5 Addendum §9.3) — the baseline needs to learn about it, not the section to be reverted. Ran: python3 scripts/registry_preserve_prose.py The script re-extracted all 11 sections (was 10) of the release manifest including the new "Formalization Release Lines" section, recomputed all SHA-256 checksums, and rewrote the baseline file. 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
W8b of the v5 next-wave cycle — closes Wave 8 and the entire v5w2 cycle. Adds the Verify-side formalization release-line surfaces per Release Lines + Formalization Surfaces v5 Addendum §7 + §9.2 + §9.3 + §8.4.
Pairs with PR #269 (W8a — Corpus-side at
/corpus/taulib/+ Research Code adjacency on/publications/).What lands
verify/taulib/index.md(+35 / 0)New "Release Lines" section inserted as the inspection-bridge view of the same three release lines that
/corpus/taulib/surfaces (W8a). Framed from the trust-boundary angle:lake build. Citable as a proof basis.Closing block re-states the IA §9.2 core warning verbatim and cross-links to the broader Verification Framework + How to Verify pages.
verify/release-manifest.md(+36 / 0)The authoritative surface for the formalization release-line picture. New canonical four-row table per Addendum §9.3:
Anchor
#formalization-release-linesis used by deep-links from the Corpus + Verify TauLib pages (W8a + W8b).Proof package states — five-state lifecycle (
in_construction → draft → candidate → released → superseded); only released packages are citable.Citation status enum — four values per Addendum §3 vocabulary (
citable · active_working · private · deprecated), surfaced on every Research Graph entry.Three-surface authority/provenance model now fully realised for formalization
Per IA Doctrine §10.3, the program's authority/provenance layer exposes three public surfaces. Wave 8 closes the formalization slice:
/assets/research-graph.json/verify/release-manifest/#formalization-release-lines(this PR) is now the canonical table; Corpus + Verify TauLib link hereURL preservation posture
Purely additive. No existing URL changes, no existing content removed or hidden on either page.
Test plan
/verify/taulib/renders the new "Release Lines" 3-tile grid between "TauLib inside the verification matrix" and "What Verify still owns"/verify/release-manifest/renders the new "Formalization Release Lines" section between "Release identity" and "Build status — summary"#formalization-release-linesanchor works for deep-links/research-graph/#rg-softwareworkGates run locally
scripts/check_hardcoded_release_numbers.pyscripts/check_release_manifest_parity.py🤖 Generated with Claude Code
This PR closes the v5 next-wave cycle. 8 waves · 12 PRs · all three v5 doctrine documents fully realised on the public site.