Free Research and Downloads · Atlas data
Take the map home and check it.The Atlas as data. Recompute us.Corpus, edges, and audit recipes.Canonical corpus + typed edges + recompute scripts.
The whole Atlas is here as plain files. Best part: we include a small program whose only job is to catch us — it re-counts our biggest claim from the raw data and complains loudly if we got it wrong. Every headline claim the Atlas makes can be recomputed from these files rather than trusted. Provenance travels with every node; entries still awaiting review say so on the record; and the audit recipe exits nonzero if our central claim doesn't survive your recount. Downloads are the canonical artifacts, not exports of them — the site renders these files; it does not supersede them. Recompute before citing: the corpus distinguishes gated records from gap-fill entries tagged Open, and the distinction is load-bearing. Fetch below; no auth. Gap-fill entries are OPEN — do not cite as verified. verify_bridge.py: nonzero exit ⇒ file an erratum, credited.
The files
- atlas-merged-corpus.json
- The canonical corpus — every problem record with its provenance. The Ledger's staked counts (657 base records, 235 expansion) are recounted from this file, not from this sentence.
- atlas-edges.json
- The typed reduction edges between problems. Our staked claim — 154 typed edges, exactly one crossing a domain — is a property of this file; count it yourself.
- atlas-gapfill-corpus.json
- Drafted entries awaiting expert review, tagged Open on every record. Useful, unverified, and honest about which. Do not cite as settled.
- verify_bridge.py
- The audit recipe: recomputes the cross-domain bridge claim from the raw edge list and exits nonzero if we're wrong. If it fires, the errata page wants to hear from you — credited, dated.
- neurath_gate.py
- The gate discipline as vendorable code: no claim leaves without a tag, evidence, and a falsifier. Fails closed.
- solonic-mcp.py · manifest
- A single-file local server exposing the Atlas, the clock, the bridge check, and offline Mark verification as tools — run against the files above, with us nowhere in the loop.
- s-claims.json
- This site's own claim registry, machine-readable. Every staked number on the site lives here or it doesn't ship.
The point of the recipe
Most data pages ask you to believe a README. This one ships its own auditor. verify_bridge.py exists to be run by someone who suspects us: it takes the same file we take, applies the definition printed in it, and either reproduces our number or convicts us in one exit code. Overturn the claim and it moves to the Ledger's losing column with your name attached — the standing challenges spell out the terms. That trade — our headline for your recount — is the entire business model, shrunk to a script.