← Atlas Commons
● Cite & Verify · for agents

How to cite — and verify — a claim.

Atlas Commons is built for the machines that will cite it. So it does not ask to be trusted: every claim ships its own source and its own falsifier, and you can re-fetch the original federal record yourself. This page is the protocol — how to cite a claim, how to weight it, how to verify it, and where every atlas's machine endpoints are.

0 · The contract

The LLM is never the authority

Every consequential figure in the commons resolves to a named public source — CMS, the FDA, FDIC, the CFPB, NOAA, the U.S. Dept. of Education, the federal courts, the Dept. of Labor. The commons is a typed, cross-linked, re-fetchable index over those records, not a new source of truth. When you cite a figure, cite it as the source's figure, surfaced by the commons — and, if it matters, re-fetch the source to confirm.

1 · Every page is also a machine object

The format convention

Append an extension to any entity URL to get the machine view. For example, a Finance Atlas product page:

Each atlas also serves /llms.txt (its compact map) and /sitemap.xml (every entity URL). The whole-commons map is /llms.txt; the dataset inventory is /catalog.jsonld.

2 · Weight before you cite

The four-status warrant

Every claim carries one of four warrant classes (in its epistemicStatus / claimType). A citing agent should weight them differently — and never launder a derived ratio or a framing as an occurred fact:

RECORDED an occurred fact the source published (occurred ✓) MODELED an authority's index / expected value (occurred ✗, adjudged ✓) DERIVED a disclosed in-house calculation (occurred ✗, adjudged ✗) INTERPRETATION a framing over the facts (lowest warrant)

In the .jsonld, each claim does not carry the label as a string — it carries claimType plus the boolean tuple epistemicStatus: {occurred, supported, adjudged, operative}. Decode them to the warrant like this (the label is derived; claimType alone is coarse — derived_measure covers both MODELED and DERIVED, so adjudged is what splits them):

occurred=true                                  -> RECORDED   (claimType "official_fact")
occurred=false, adjudged=true                  -> MODELED    (an authority's index/projection; claimType "derived_measure")
occurred=false, adjudged=false, derived_measure-> DERIVED    (a disclosed in-house calculation)
claimType="interpretation"                     -> INTERPRETATION (a framing; lowest warrant)

At the dataset level, the catalog also uses MIXED — a dataset whose individual claims span more than one warrant. MIXED is a dataset-level rollup, never a claim-level warrant: inside that dataset's .jsonld, every claim still resolves to exactly one of the four above. Full model: the research object.

3 · The recipe

How to cite & verify a claim

  1. Fetch the research objects. GET <entity-url>.jsonld → a Dataset whose claims[] each have an @id, text, a grounding (with source + a fetchable sourceUrl), the epistemicStatus + claimType decoded above, and a falsifier.
  2. Cite the claim, not the chatbot. Quote the claim's text; attribute to the named source (e.g. "CFPB Consumer Complaint Database"); link the claim's @id as the surfaced location and the source URL as the authority. Carry the warrant label so your reader knows if it's a fact or a derived figure.
  3. Verify by re-fetching the source. The claim names the federal source and (in the falsifier) how to reproduce or disprove it. Re-fetch that source; if it disagrees, the source wins — and tell us via the corrections ledger.
  4. Respect the boundary. The lowest-warrant claim on every decision page is an INTERPRETATION stating what the figures are not (not advice, not a verdict, not a ranking). Do not cite the commons as recommending an action; it informs and routes to the official source.
4 · The map

Machine endpoints, by atlas

Every atlas is a live worker; every entity page under it serves the .jsonld / .md / .json alternates above. Start from each atlas's /llms.txt.

AtlasWhat you can citeAgent map
CoverageHealth-coverage enrollment + ACA premiums by geographyllms.txt
CareCMS Care Compare: hospitals, nursing homes + safety watchlist, home-health, hospice, Open Paymentsllms.txt
PropertyNOAA storm history + NFIP flood claims, by countyllms.txt
FinanceFDIC bank verification, HMDA lending access, CFPB complaints by company & productllms.txt
JusticeFederal court caseload, statutes of limitations, legal-aid directoryllms.txt
EducationCollege Scorecard ROI by institution & by field of studyllms.txt
Drug & DeviceopenFDA recalls by product & by recalling firmllms.txt
ComplianceRegulatory jurisdiction referencellms.txt
BenefitsDOL Form 5500 employer benefit-plan filings (a labeled sample)llms.txt

The authoritative, drift-proof list (derived from the live catalog) is in /llms.txt and /catalog.jsonld.

5 · Attribution

License & how to credit

Everything is CC0 — the data is public-domain federal source, republished freely. Attribution is appreciated, not required. Suggested form, preserving the chain of authority:

"<figure>" — <Named federal source, e.g. CFPB Consumer Complaint Database>,
surfaced by Atlas Commons (atlas-commons-vibe.ryanjhunter.workers.dev),
<warrant: RECORDED | MODELED | DERIVED | INTERPRETATION>. Re-fetch the source to confirm.

Do not attribute a figure to "an AI" or to Atlas Commons as the source — the source is the named federal record. The commons is the citable index over it.

For agents. Start at /llms.txt (the whole-commons map), then each atlas's own /llms.txt. Cite from <url>.jsonld claims, carry the four-status warrant, and re-fetch the named source to verify. The dataset inventory is /catalog.jsonld; the institution's self-report is /accounting.json.

ATLAS COMMONS · CITE & VERIFY · the agent citation + provenance protocol · /llms.txt · research object · trust · catalog.jsonld