Repository Documents

The Pages site is the public front door. The full governed programme pack remains in the repository root and campaign directories. Root documents and campaign source pointers are repository-only unless a rendered page explicitly links to them.

Do not infer Pages URLs for root or campaign files. Use the canonical GitHub links below.

Architecture and execution pillars

• Architecture Overview
• MATHFORGE specification
• MATHSOLVE specification
• MATHCERT specification

Standards and governance

• Grand Challenge Work Package Standard
• Canonical Pedagogy Standard pointer
• Claim Ledger Standard
• Certification Ladder
• Classification Discovery Standard
• Handoff Standard
• Governance
• Thurstonian Ethos
• Domain Registry
• ADR-0010 Documentary Authority
• ADR-0011 Full Workflow Coverage
• ADR-0012 Self-Authenticating Workflow Coverage
• Programme Workflow Coverage

Canonical claim ledgers use the versioned schema and an explicit central registry. Schema-bound Agent Council reviews likewise require both schema conformance and central registration. Programme policy adversarially detects omitted canonical ledgers and omitted discoverable reviews.

Canonical domains

• Domain 01 · Union-Closed Sets
• Domain 02 · Navier–Stokes Critical Integrability
• Domain 03 · Hodge Conjecture
• Domain 04 · Birch–Swinnerton-Dyer
• Domain 05 · Poincaré Reconstruction
• Domain 06 · Yang–Mills Existence and Mass Gap
• Domain 07 · P versus NP
• Domain 08 · Riemann Hypothesis

Domains 06–08 begin with integrated root WP00 dossiers rather than separate master-plan files. A later governed master plan may supersede those canonical entries only through an explicit registry and decision update.

Historical filename note: the detailed BSD plan remains recoverable under DOMAIN_03_BIRCH_SWINNERTON_DYER_MASTER_PLAN.md. The mislabelled development-stage DOMAIN_04_POINCARE_RECONSTRUCTION_MASTER_PLAN.md was removed in PR #96; the canonical Poincaré entry is DOMAIN_05_POINCARE_RECONSTRUCTION_MASTER_PLAN.md. ADR-0005 and ADR-0006 govern the canonical numbering.

Campaign directories

• Union-Closed
• Union-Closed documentary source lock
• Navier–Stokes
• Hodge
• Birch–Swinnerton-Dyer
• Poincaré Reconstruction
• P versus NP
• Riemann Hypothesis

UC-DOC-WP00 has completed its source lock and trust-spine repair. Its source pointer remains under the campaign and outside the generated site; public candidate metadata do not imply manifest membership or web-edition publication.

Yang–Mills currently uses its integrated root WP00 as the complete campaign entry.

Riemann Hypothesis post-WP00 records:

• WP01/WP02 integration dossier
• WP01 false-proof atlas
• WP02 theorem ledger
• Post-merge retained-blocker disposition

RH-WP01 and RH-WP02 are implemented, merged, and CI-passed but remain formally unpromoted while their blocking legacy review dispositions remain in force.

Documentary Library and release authority

• Documentary Library
• Admitted-edition manifest
• Pre-admission candidate registry
• Source-record policy
• Poincaré reference web edition
• Reusable web-edition schema
• Poincaré edition record

ARTIFACT_MANIFEST.json is the sole authority for admitted public editions. DOCUMENTARY_CANDIDATES.json records source-locked projects before admission but cannot confer collection membership. Candidate source pointers remain repository-only until the page, edition record, assets, public source record, index, navigation, and manifest volume enter atomically.

The checksum-locked complete illustrated source bundle is the authoritative documentary source artifact, and the checksum-locked PDF is the rendered edition. Entries marked metadata_only have governed identities but no asserted stable public release locator. Documentary machine status separates claim status, problem class, and reader-facing display wording.

Union-Closed formal and exact baseline

• WP01 Union-Closed Status Spine
• WP02 Union-Closed Lean Handoff
• Pinned cross-repository evidence
• External MATHCERT implementation
• UC-DOC-WP00 canonical claim ledger
• UC-DOC-WP00 schema-bound review

The Union-Closed formal implementation is external, not a local MathCert/ directory. The global programme policy checks out the exact MATHCERT commit in the evidence record and runs its complete certification gate. None of the bounded, formal, documentary, or source-lock artifacts proves Frankl's conjecture.

Workflow and publication controls

• Global programme policy
• Campaign replay registry
• Campaign executable validator
• CI policy reachability validator
• Workflow inventory validator
• Workflow semantic validator
• Policy dependency declaration
• Documentation dependency declaration
• Pages deployment gate

The global policy independently discovers campaign executables, proves executable CI controls reachable from operative workflow roots, runs all governed replay and formal gates, and validates parsed workflow semantics. All jobs use fixed Ubuntu runners and checked-in exact top-level dependency pins. Pages deploys only a successful policy-validated SHA that remains the current main tip; a newer commit cancels or rejects stale publication. The dependency declarations are not represented as a complete transitive hash lock.

Inventory and public entry points

• Current File Manifest
• Repository README
• Public Domain Catalogue
• Campaign Promotion Register
• Programme Status Taxonomy

Authority rule

The domain registry identifies canonical domain entries and public pages. The Agent Council artifact ledger identifies authoritative integrated governed artifacts. Canonical claim ledgers, proof files, admitted source records, candidate source locks, governing source artifacts, and MATHCERT artifacts remain authoritative within their declared roles. Repository merge and CI can establish integration, declared-environment, reachability, and replay facts; they cannot prove the underlying open problem or override an explicit blocking review. Publication is permitted only after the successful policy-validated SHA is confirmed as the current main tip.