Verify-Lane v3.0 — site side: _data/verify/coverage_by_domain.json by ThorFuchs · Pull Request #23 · Panta-Rhei-Research/site

ThorFuchs · 2026-04-30T22:16:17Z

Summary

Phase v3.0 of the Verify-Lane release plan (site side). Auto-generated data file consumed by v3.1+ verify-page badges + per-domain hub redesigns in subsequent PRs.

Pure data plumbing — no UX changes in this PR.

Generated by corpus/scripts/sync_corpus_to_site.py Step 6/6.

What lands

_data/verify/coverage_by_domain.json — per-domain Lean module + declaration stats now available at site.data.verify.coverage_by_domain for v3.1 Liquid layouts.

Domain	Modules	Declarations	Formalized	Lines
mathematics	284	7,617	5,002	70,685
physics	171	6,069	4,489	58,581
life	31	476	476	5,329
metaphysics	9	337	337	4,517
Total	495	14,499	10,304	139,112

(Tour + unspecified books excluded from rollup; matches corpus global summary 512 modules total · 0 active sorries.)

source_commit field matches the corpus taulib-projections summary (cb5e83015b54), so the freshness gate detects drift if either side updates without re-syncing.

_data/_sync_manifest.json schema_version bumped to verify-v3.0.

Verification (all green)

✓ python3 corpus/scripts/check_site_data_freshness.py
    → 15 pairs in sync · objects.json: 4139 public items
    · verify/coverage_by_domain.json: 4 domains · 495 modules
    · source_commit cb5e83015b54 (matches corpus)

✓ bundle exec jekyll build    → clean exit 0

Test plan

CI green on jekyll build
Confirm site.data.verify.coverage_by_domain.mathematics.module_count == 284 is queryable from a Liquid scratch page
Confirm _data/_sync_manifest.json reports schema_version: verify-v3.0

Sequencing

Depends on Panta-Rhei-Research/corpus#16. Merge order: corpus #16 → site (this PR).

Next phase

v3.1 — _includes/verify-page-badges.html consuming this data file. Renders Lean-coverage / scope / verification-mode / bridge-status chips on /verify/domain-verification/<domain>/ × 4, /verify/release-manifest.md, /verify/predictions-and-falsification/. Mirror of the v3.2 result-page enrichment from the just-shipped Results-Lane v3 sprint.

🤖 Generated with Claude Code

Phase v3.0 of the Verify-Lane release plan (site side). Auto-generated data file consumed by the v3.1 verify-page badges + per-domain hub redesigns landing in subsequent PRs. Pure data plumbing — no UX changes in this PR. Generated by `corpus/scripts/sync_corpus_to_site.py` (Step 6/6) from `exports/public/taulib-projections/data/{modules,summary}.json`. Aggregates by mapping books → domains: Books I-III → mathematics Books IV-V → physics Book VI → life Book VII → metaphysics Per-domain stats now available at site.data.verify.coverage_by_domain for v3.1 Liquid layouts: mathematics : 284 modules · 7,617 declarations · 5,002 formalized · 70,685 lines physics : 171 modules · 6,069 declarations · 4,489 formalized · 58,581 lines life : 31 modules · 476 declarations · 476 formalized · 5,329 lines metaphysics : 9 modules · 337 declarations · 337 formalized · 4,517 lines Total : 495 modules · 14,499 declarations · 0 sorries (Tour and unspecified books excluded from per-domain rollup; matches global summary 512 modules total.) `source_commit` field in the data file matches the corpus taulib-projections/data/summary.json source_commit (cb5e83015b54), so the freshness gate `corpus/scripts/check_site_data_freshness.py` detects drift if either side updates without re-syncing. `_data/_sync_manifest.json` schema_version bumped to verify-v3.0. Verification (all green): ✓ python3 corpus/scripts/check_site_data_freshness.py → 15 pairs in sync · objects.json: 4139 public items · verify/coverage_by_domain.json: 4 domains · 495 modules · source_commit cb5e83015b54 (matches corpus) ✓ bundle exec jekyll build → clean exit 0 (incremental on top of v3-results-lane infrastructure) Sequencing Depends on Panta-Rhei-Research/corpus#16. Companion site PR for v3.1 (verify-page badges) lands in next phase. Next phase v3.1 — `_includes/verify-page-badges.html` consuming this data file. Renders Lean-coverage / scope / verification-mode / bridge-status chips on /verify/domain-verification/<domain>/ × 4, /verify/release-manifest.md, /verify/predictions-and-falsification/. Mirror of the v3.2 result-page enrichment. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

…#24) * feat(site): verify-lane v3.1 — verify-page badges (Lean coverage / mode / bridge) Phase v3.1 of the Verify-Lane release plan. Renders Lean-coverage / mode / bridge-status / scope chips on verify pages. Mirror of the v3.2 result-page enrichment, adapted for verification-domain semantics. Builds on v3.0 (corpus PR #16 + site PR #23) which landed `_data/verify/coverage_by_domain.json`. NEW include: _includes/verify-page-badges.html Reads site.data.verify.coverage_by_domain[page.domain]. Three render branches gated on page.verify_type: - verify_type: domain_verification → Lean coverage chip · verification mode chip · bridge-status chip (Strong ≥ 90% formalized · Moderate ≥ 65% · Emerging otherwise) + optional scope chip → Renders on /verify/domain-verification/{mathematics,physics,life, metaphysics}/ - verify_type: release_manifest → Global TauLib stats · Pinned snapshot · 0 sorries + custom-axiom count → Renders on /verify/release-manifest/ - verify_type: falsification_path | predictions_falsification → Physics-domain Lean linkage · Empirical (2025–2035) mode chip → Renders on /verify/predictions-and-falsification/ Always renders a Public visibility chip first. Layout wiring: _layouts/program-doc.html Calls verify-page-badges.html in the hero block, gated on page.verify_type. Other program-doc consumers (program/, corpus/, etc.) unaffected. Frontmatter updates: /verify/release-manifest.md — added verify_type: release_manifest plus v2_lane / type / status fields for parity with other verify pages. Other 4 domain hubs and predictions-and-falsification already had verify_type set; no frontmatter changes needed. SCSS: _sass/_content.scss .chip-row-verify, .chip-verify-coverage, .chip-verify-mode (formal + empirical variants), .chip-verify-bridge (strong/moderate/emerging variants), .chip-verify-scope. All match the v3.2 chip-row-badges pattern with verify-specific palette. Rendered output verified live (after `bundle exec jekyll build` exit 0): /verify/domain-verification/mathematics/ → Public · Lean · 284 modules · 5002/7617 formalized · Mode · Formal+Empirical · Bridge · Moderate (66%) /verify/domain-verification/physics/ → Public · Lean · 171 modules · 4489/6069 formalized · Mode · Formal+Empirical · Bridge · Moderate (73%) /verify/domain-verification/life/ → Public · Lean · 31 modules · 476/476 formalized · Mode · Formal+Empirical · Bridge · Strong (100%) /verify/domain-verification/metaphysics/ → Public · Lean · 9 modules · 337/337 formalized · Mode · Formal+Empirical · Bridge · Strong (100%) /verify/release-manifest/ → Public · TauLib · 512 modules · 14601 declarations · Mode · Pinned snapshot · 0 sorries · 3 custom axioms /verify/predictions-and-falsification/ → Public · Physics Lean · 171 modules · 4489/6069 formalized · Mode · Empirical (2025–2035) Verification gates (all green): ✓ bundle exec jekyll build → exit 0 in 482s ✓ All 6 chip rows render with v3-aligned classes (data-badge attributes set; v3.2 result-page parity preserved for filterable browse) Sequencing Depends on #23 (v3.0 data file). Already merged. Next phase v3.2 — Domain-verification hub redesign. Expand the 43-60-line thin routing pages into v3-shape hubs with hero stats grid · 5-6 sub-route cards · plain-language intro · See-also footer. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * fix(site): refresh release-manifest sections baseline after v3.1 frontmatter add The v3.1 frontmatter additions to verify/release-manifest.md (verify_type / v2_lane / type / status) shifted the __frontmatter__ section checksum, causing the Registry Verify CI check to fail. This commit regenerates the baseline via `scripts/registry_preserve_prose.py` so the gate passes again. Live + baseline now both: 1fe00850442b307f Verification: ✓ python3 scripts/registry_verify.py --full → All checks passed (dashboard prose / release manifest sections / filter_rules consistency / site data registry totals) Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com> Co-authored-by: Anna-Sophie Fuchs <anna-sophie.fuchs@panta-rhei.site>

) Replaces the live PDFs and metadata for the seven anchor documents (C001 + WP000-WP005) with the canonical v1.0 versions just shipped to publications/main (#23). Picks up the late polishes that landed in papers/main today: WP002 concordance regen (#61 papers), WP005 final polish (#62 papers), WP004 emergency polish (#63 papers). This is Phase D of the four-repo anchor-canon v1.0 deployment wave. ## What changes - Replaces 7 PDFs in assets/pdfs/anchor-documents/ with the freshly built bytes (sha256 matches publications-repo manifests at HEAD) - Updates _data/publications/anchor_documents.yml integrity per entry: checksum_sha256, file_size, page_count, release_date - Bumps last_updated: 2026-05-10 in each anchor-document detail page frontmatter ## Refreshed sha256 prefixes (publications/main HEAD = 4f89a53) | ID | Old prefix | New prefix | Pages | Bytes | |-------|--------------|--------------|-------|-----------| | C001 | `eaefe680` | `0f547c4a` | 26 | 327,217 | | WP000 | `8caa1e83` | `cc65cae4` | 4 | 503,736 | | WP001 | `7a575fc1` | `050e986c` | 26 | 2,445,801 | | WP002 | `dc22657b` | `91e53a7c` | 50 | 412,045 | | WP003 | `f0aa1bc0` | `f63cf77a` | 37 | 294,691 | | WP004 | `bc82d22f` | `835578e7` | 23 | 545,965 | | WP005 | `98f3d00c` | `cb2067b7` | 35 | 324,239 | ## Page-count reductions Several papers compressed during the polish cycle (e.g. WP002 71 → 50, WP004 29 → 23, C001 45 → 26 — driven by the design-uplift and concordance-compaction waves). Page counts now reflect ground-truth via pdfinfo on the new PDFs. ## What's next Phase E (separate follow-up PR) will land the editorial WP-code de-emphasis across site prose: lead with the full italic title, keep the WP-code as a trailing parenthetical for findability. Codes preserved in URLs, route tables, citations, and structured data. ## Out of scope - OpenTimestamps stamping of publications manifests (separate follow-up) - Zenodo DOI minting (only WP001 currently has a DOI) - prrp.site short-route DNS configuration (smoke-test only post-launch) Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

ThorFuchs requested a review from AnSoFuchs as a code owner April 30, 2026 22:16

AnSoFuchs approved these changes Apr 30, 2026

View reviewed changes

ThorFuchs merged commit 56e3e4b into main Apr 30, 2026
2 checks passed

ThorFuchs deleted the verify-lane-v3.0/per-domain-coverage-data branch April 30, 2026 23:11

ThorFuchs mentioned this pull request May 1, 2026

Verify-Lane v3.1 — verify-page badges (Lean coverage / mode / bridge) #24

Merged

5 tasks

This was referenced May 1, 2026

Verify-Lane v3.3 — plain-language accordions across 14 verify pages #25

Merged

verify: math-specific glossary layout (Sprint 3 of v0.5+ expansion) #43

Merged

ThorFuchs mentioned this pull request May 10, 2026

site/anchor-canon: deploy seven anchor documents at canonical v1.0 #195

Merged

5 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Verify-Lane v3.0 — site side: _data/verify/coverage_by_domain.json#23

Verify-Lane v3.0 — site side: _data/verify/coverage_by_domain.json#23
ThorFuchs merged 1 commit into
mainfrom
verify-lane-v3.0/per-domain-coverage-data

ThorFuchs commented Apr 30, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Conversation

ThorFuchs commented Apr 30, 2026

Summary

What lands

Verification (all green)

Test plan

Sequencing

Next phase

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants