How a docket is built
Every docket follows the same four-step spine, while the evidence routes vary by claim. State of Proof does not certify papers or replace peer review; it records what has been examined, what held within a stated scope, and what remains open.
Lock the exact source.
Every docket pins one artifact: a version and a hash. All evidence refers to that artifact and nothing else. When the source changes, the lock moves visibly and affected checks re-queue.
yields: Source Lock — version · hash · dateMap the claim and its dependencies.
The central statement, its lemmas, and everything they lean on become an explicit graph. Mapping names the load-bearing steps — the ones whose failure would re-scope the whole claim.
yields: claim map · load-bearing stepsTest the load-bearing steps.
Four Evidence Routes, each scoped and replayable where the source permits: computational reproduction, formal correspondence, literature pinning, and expert review. A route produces evidence only about the step it actually touched.
Publish the evidence and the remaining uncertainty.
Statuses per route and per scope, Open Steps named precisely enough for an expert to pick one up, and every material update recorded as a State Change. History stays visible.
yields: statuses · Open Steps · State ChangesThere is no overall score.
Different parts of the same argument may hold different evidence states — a reproduced computation next to an open expert question. A docket therefore carries several statuses at once, each naming its own scope.
Statuses describe evidence collected for a defined scope. They are not peer-review decisions, publication recommendations, or certificates of mathematical truth.