Grand Challenge mathematics work is organized as a three-pillar system:
MATHFORGE -> MATHSOLVE -> MATHCERT
discover organize certify
The programme exists to turn mathematical curiosity into checked understanding without confusing evidence, computation, exposition, or certification.
- MATHFORGE discovers candidate ore: source signals, problem cards, reconnaissance artifacts, finite screens, and route suggestions.
- MATHSOLVE organizes the campaign: theorem spines, work packages, proof-debt registers, exact obligations, and certification handoffs.
- MATHCERT checks the boundary: formal statements, exact replays, certificate validators, and claim ledgers.
Use these as the current source of truth before opening new doctrine or domain work:
docs/GRAND_CHALLENGE_PEDAGOGY_STANDARD.md— rails-before-research exposition standard.docs/PEDAGOGICAL_STYLE_GUIDE.md— sentence- and artifact-level style companion.docs/ACCESSIBLE_RESEARCH_GUIDE_STANDARD.md— prerequisites, examples, fixtures, challenge ladders, certification paths, and continuation graphs for accessible research handoff.docs/CHAIDEZ_PEDAGOGICAL_PROTOCOL.md— theorem-spine campaign protocol.docs/FOUNDATION_AWARE_MATH_PROGRAMME.md— structured-object and axiom-profile doctrine.docs/CLAIM_BOUNDARY_DOCTRINE.md— claim-status and proof-boundary discipline.CLASSIFICATION_DISCOVERY_STANDARD.md— external classification, discovery evidence, and knowledge graph rules.GRAND_CHALLENGE_WORK_PACKAGE_STANDARD.md— Work Package structure and review discipline.CLAIM_LEDGER_STANDARD.md— claim ledger format, support route, and promotion conditions.CERTIFICATION_LADDER.md— promotion gate from mathematical development to certified result.
docs/GRAND_CHALLENGE_READER_GUIDE.mddocs/PROGRAMME_ATLAS.mddocs/MINDERLINGS.mddocs/PEDAGOGICAL_STYLE_GUIDE.mddocs/ACCESSIBLE_RESEARCH_GUIDE_STANDARD.mdtemplates/accessible_research_guide_template.mddocs/CLAIM_BOUNDARY_DOCTRINE.mddocs/CROSS_PILLAR_LANES.mddocs/GLOSSARY.md
Additional supporting files include schemas, templates, exact finite enumerators, small audit outputs, resource notes, and Lean scaffolding for the Union-Closed domain.
- Read
docs/GRAND_CHALLENGE_READER_GUIDE.mdfor orientation. - Read
ARCHITECTURE_OVERVIEW.mdto understand the three-pillar split. - Read the current operating standards above before starting new work.
- Use
GRAND_CHALLENGE_WORK_PACKAGE_STANDARD.mdandtemplates/work_package_template.mdfor every MATHSOLVE Work Package. - Use
docs/ACCESSIBLE_RESEARCH_GUIDE_STANDARD.mdandtemplates/accessible_research_guide_template.mdwhenever a project needs a human or agentic on-ramp. - Treat
CLAIM_LEDGER_STANDARD.mdas binding. No claim should appear without a type, support route, and promotion condition. - Treat
CERTIFICATION_LADDER.mdas the promotion gate from mathematical development to certified result. - Read
docs/CROSS_PILLAR_LANES.mdwhen a recurring tactic, witness, or certificate path spans all three pillars. - Treat
CLASSIFICATION_DISCOVERY_STANDARD.mdas binding for subject mappings, knowledge graph assertions, and discovery evidence. - Treat
schemas/foundational_profile.schema.jsonas the machine-readable form of the foundation-aware profile. - Begin the first domain with
DOMAIN_01_UNION_CLOSED_MASTER_PLAN.md,WP01_UNION_CLOSED_STATUS_SPINE.md, andWP02_UNION_CLOSED_LEAN_HANDOFF.md.
This package does not claim new mathematical results. The included Union-Closed enumerator is a small exact sanity audit for universes up to size 4. It is useful infrastructure, not progress on Frankl's conjecture.
A source can motivate a claim. A computation can suggest a claim. A Work Package can organize a claim. But MATHCERT determines whether a claim is checkable.
The desired voice is ambitious, lucid, and exact. It should not sound like marketing. It should not obscure uncertainty. It should not confuse ornament with insight. Decoration is allowed only when it helps the reader see the structure.
A good artifact should leave the reader with four things:
- the object in view;
- the obstruction in focus;
- the claim boundary visible;
- the next move unmistakable.