Verify-Lane v3.1 — verify-page badges (Lean coverage / mode / bridge)#24
Merged
Conversation
…de / 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>
…tmatter 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>
AnSoFuchs
approved these changes
May 1, 2026
7 tasks
ThorFuchs
added a commit
that referenced
this pull request
May 12, 2026
…ections (#211) Replaces the WP003 PDF and bumps metadata after publications/main #24 and papers/main #65. WP003 ships its finalization v2 polish: - New "TauLib in One Page" opener (Technical Snapshot + Trust Budget at a Glance with all 3 axiom names visible upfront + Boundary Rule + 15-minute reviewer route) - Cover label corrected: "Anchor canon technical overview" - Reading time: dual fast-route (10-15 min) / full-route (70-100 min) framing - Broken generated-docs URL taulib.panta-rhei.site -> taulib.site All TauLib release metrics in the document already matched the canonical site/_data/release/current.yml ledger (cross-checked all 17 taulib.* metrics). ## Refreshed identity (WP003) sha256 prefix: f63cf77af043 -> db01b46b129c bytes: 294,691 -> 303,923 pages: 37 -> 39 (+2 for opener) 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
2 participants
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
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 (site#23 + corpus#16) which landed
_data/verify/coverage_by_domain.json.What lands
NEW include:
_includes/verify-page-badges.htmlReads
site.data.verify.coverage_by_domain[page.domain]. Three render branches gated onpage.verify_type:verify_typedomain_verification/verify/domain-verification/{4 domains}/release_manifest/verify/release-manifest/falsification_path/predictions_falsification/verify/predictions-and-falsification/Layout wiring:
_layouts/program-doc.htmlCalls
verify-page-badges.htmlin hero block, gated onpage.verify_type. Other program-doc consumers (program/, corpus/, etc.) unaffected.Frontmatter
/verify/release-manifest.md— addedverify_type: release_manifest+v2_lane+type+statusfor parityverify_typesetSCSS chip rules (
_sass/_content.scss).chip-row-verify,.chip-verify-coverage,.chip-verify-mode-{formal,empirical},.chip-verify-bridge-{strong,moderate,emerging},.chip-verify-scope. All match v3.2 chip-row-badges pattern with verify-specific palette.Rendered output (verified live)
/verify/domain-verification/mathematics//verify/domain-verification/physics//verify/domain-verification/life//verify/domain-verification/metaphysics//verify/release-manifest//verify/predictions-and-falsification/Verification (all green)
bundle exec jekyll build— exit 0 in 482sdata-badgeattributes preserving v3.2 result-page parity for future filterable browseTest plan
/verify/domain-verification/mathematics/— confirm Bridge · Moderate (66%) chip renders/verify/release-manifest/— confirm 0 sorries · 3 custom axioms chip/verify/predictions-and-falsification/— confirm Empirical (2025–2035) chipSequencing
Depends on site#23 (v3.0). v3.0 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.
🤖 Generated with Claude Code