Skip to content

Grand Challenge Reader Guide

A reading protocol for reconstructing the object, locating the obstruction, testing the claim boundary, and identifying the next move.

The programme is built for readers, not only for solvers. A mathematical artifact succeeds when another serious reader can reconstruct what was attempted without guessing what the author meant.

The author promises to mark uncertainty. The reader promises to respect partial progress when it is honestly bounded.

Four questions govern the reading

01

What is the object?

Identify the ingredients, examples, non-examples, ambient category, and exact formulation being preserved.

Do not let machinery arrive before the mathematical object.
02

Where is the obstruction?

Find the point where naive reasoning fails: explosion, singularity, non-compactness, missing invariant, undecidability, or boundary pathology.

A Work Package should teach the difficulty, not hide it.
03

What is the claim boundary?

Separate what is proved, formalized, exactly computed, literature-derived, heuristic, conjectural, failed, superseded, or refuted.

Status determines what kind of reliance is permitted.
04

What is the next move?

Demand a finite obligation: a lemma, certificate replay, counterexample search, formal definition, or residual domain reduction.

“More work is needed” is not a next move.

Read through the correct lens

New contributorCan I reconstruct the landscape?

Begin with the Showcase, Domain Catalogue, Programme Atlas, and source map. Learn the nouns before proposing a route.

Campaign authorIs the obligation sharp enough to attack?

Inspect definitions, reductions, dependencies, failed routes, and promotion conditions.

Formalization leadIs the intended statement encoded?

Compare human semantics, formal statement, assumptions, imports, and replay environment.

Skeptical reviewerWhat could downgrade this claim?

Test the support type, active assumptions, independent artifact, and failure condition.

Anatomy of a serious artifact

01Orientation

Problem statement, source reconstruction, status, terminology.

02Mathematical core

Definitions, examples, invariants, normal forms, diagrams.

03Obstruction register

Known barriers, boundary cases, complexity, failed heuristics.

04Theorem spine

Dependency graph from local obligations to target claim.

05Evidence ledger

Proofs, computations, certificates, citations, and status labels.

06Continuity and handoff

Authoritative artifact, exact next task, promotion condition, and certification route.

Reading order

For the programme

  1. Showcase for the apparatus in one view.
  2. Programme Domain Catalogue for the current campaign portfolio.
  3. Programme Charter for obligations governing every artifact.
  4. Programme Atlas for the transformation from question to checked claim.
  5. Claim Boundary Doctrine for support classes and promotion.
  6. Programme Status Taxonomy to distinguish claims, artifact lifecycle, and campaign disposition.
  7. Agent Council for review and continuity responsibilities.
  8. The three pillar specifications for operational detail.

For a domain

  1. Begin at its public landing page in the Domain Catalogue.
  2. Follow the canonical master-plan link; do not infer authority from the landing page alone.
  3. Reconstruct the source boundary, exact target, and foundational profile.
  4. Follow Work Packages in dependency order, not merely chronological order.
  5. Read the claim ledger before trusting a prose summary.
  6. Inspect review records and unresolved obligations.
  7. Inspect the proof, replay, or certification packet before treating a result as promoted.
  8. Check whether a status word describes a mathematical claim, an artifact lifecycle state, or a campaign disposition.

For a solved-problem archive

  1. Confirm that the target theorem is already classical.
  2. Identify which proof route is reconstructed and which sources are imported.
  3. Separate source concordance, theorem-interface reconstruction, bounded certificates, and complete proof verification.
  4. Read every retained exclusion: no novelty, no independent proof, no full formalization, or other campaign-specific boundary.

The final test

A reader should be able to close the artifact and answer, in plain language:

What object did we study? Why was it difficult? What changed? What may I now rely upon? What must happen next?

The programme's work is not merely to solve. It is to reduce confusion in a form that survives contact with proof, review, and revision.