Catalog standard
Before a famous problem is presented as current.
Uploading a Lean statement creates a source-pinned record. It does not establish that a problem is still open, canonically formulated, or updated with the newest result.
- 01Canonical name · variant · source
Identify the mathematical object
Name the canonical problem, origin, accepted variants, and exact informal statement. Similar names must not collapse different conjectures.
- 02Prior-work map · milestone DAG
Map the work that came before
Record the original source, best known results, solved cases, nearby counterexamples, and references contributors should read first.
- 03Freshness date · review evidence
Check the frontier is current
Attach an as-of date, searched primary sources, reviewer, and unresolved conflicts. A stale review remains visibly stale.
- 04Statement hash · Lean environment
Pin the formal target
Freeze the Lean declaration, source revision, toolchain, dependencies, hashes, and license; then review statement fidelity.
- 05Claim-by-claim attestations
Keep every claim separate
Kernel acceptance, statement fidelity, literature novelty, independent review, and usefulness answer different questions.
Statement and environment are reproducible.
Prior work and status were checked as of a stated date.
Specific formal and review claims carry independent evidence.
Current boundary
Source-pinned does not mean frontier-reviewed.
Many records are source-pinned imports and explicitly remain frontier-unreviewed. Proofweave does not convert upstream labels into its own mathematical attestation.