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

[ThorFuchs]

Summary

Phase v3.3 of the Verify-Lane release plan. Adds a green-accent plain-language accordion (expanded by default) at the top of every technical verify page — so the intelligent layperson reads one paragraph of accessible-register prose before the technical body.

Mirrors the v3.4 results-lane plain-language pattern: same .result-plain-language SCSS palette, same <details open> UX, same "In plain language" eyebrow + ▾ toggle. The verify lane carries an additional .verify-plain-language hook class for future divergence without breaking the shared visual.

Builds on #23 (v3.0 data) + #24 (v3.1 badges) — both already merged.

What lands

NEW include: _includes/verify-plain-language.html

Renders only when page.plain_language_summary frontmatter is set (manual opt-in, currently 14 verify pages). Reuses the v3.4 result-plain-language SCSS panel for visual consistency.

Layout wiring: _layouts/program-doc.html

Conditionally calls verify-plain-language.html between summary-cards and the technical content card. Other program-doc consumers (program/, corpus/) unaffected.

Authored plain_language_summary on 14 pages

Technical layer (8):

Page	Plain-language framing
/verify/formal-verification-stack/	4-layer formal checking explained
/verify/scientific-rigor/	typed claims, domain-appropriate standards
/verify/verification-framework/	four verification modes, why not collapsed
/verify/tcb/	what's trusted beyond Lean's kernel
/verify/custom-axioms/	3 custom axioms accounted for honestly
/verify/meta-verification-frontier/	who verifies the verifier
/verify/bridge-verification/	internal-↔-external claim audit
/verify/construction-spine-verification/	map of 10 build steps to verify modes

Reviewer-route layer (hub + 6):

Page	Plain-language framing
/verify/how-to-audit/	pick your role, jump to your route
/verify/how-to-audit/formal-methods/	afternoon audit for proof-assistant specialists
/verify/how-to-audit/mathematician/	3 load-bearing theorems in Books I-III
/verify/how-to-audit/physicist/	ι_τ fitted-or-forced + a-priori-or-postdiction
/verify/how-to-audit/philosopher/	derivation-or-redefinition test
/verify/how-to-audit/prior-art-specialist/	new-or-isomorphic-relabel test
/verify/how-to-audit/journalist-skeptic/	15-minute scan + specialist questions

Plan deviation note

The v3.3 plan said "author 3 new how-to-audit reviewer pages (mathematician, philosopher, journalist)". A parallel v2.x sprint had already authored 5 reviewer pages + a richer hub (formal-methods, mathematician, physicist, philosopher, prior-art-specialist, journalist-skeptic). v3.3 adapts: instead of duplicating that work, it adds the plain-language accordion layer across all 14 verify-lane pages so the layperson gets a consistent affordance everywhere — strictly additive on top of the existing reviewer pages.

Verification (all green)

• ✅ python3 scripts/registry_verify.py --full — all 4 checks pass (dashboard prose / release manifest sections / filter_rules consistency / site data registry totals)
• ✅ bundle exec jekyll build — exit 0 in 437s
• ✅ Spot-check rendered HTML — all 14 pages render <details class="result-plain-language verify-plain-language" open> accordion as expected
• ✅ No forbidden strings; pre-commit hook passed
• ✅ No baseline refresh needed (v3.3 doesn't touch verify/release-manifest.md, so release_manifest_sections.yml baseline remains valid)

Test plan

• CI green on jekyll build
• CI green on Registry Verify (no baseline drift expected)
• Visit /verify/formal-verification-stack/ — confirm green accordion expanded by default
• Visit /verify/how-to-audit/ — confirm hub accordion + 6 reviewer cards
• Click ▾ toggle — confirm collapse → expand cycle works (native <details>, no JS)
• Spot-check /verify/tcb/ — plain-language explains "every formal verification system trusts something"
• Mobile breakpoint sanity check on one technical page + one reviewer page

Sequencing

Depends on site#23 (v3.0) + site#24 (v3.1) — both already merged.

Next phase

v3.2 — Domain-verification hub redesign (deferred behind v3.3 by user choice; both phases independent).
v3.4 — Glossary cross-links + cross-lane integration + mobile audit.

🤖 Generated with Claude Code