Source support
Stable ID, title, publisher, author where relevant, canonical URL or archive ID, publication/access dates, source type, jurisdiction, issue IDs, rights note, primary/secondary designation, status, and replacement/retirement data.
Source RegisterSources · Claims · Corrections · Review
Evidence paths before evidence claims.
Build 13 creates the governed trust infrastructure for SourceRecords, ClaimRecords, SourceUse links, corrections, and editorial review without falsely marking any current issue record verified or publishable.
Evidence coverage summary
Structured, still unsourced.
The registry currently contains 0 governed SourceRecords, 0 ClaimRecords, and 0 reviewed claims. All 88 issue paths remain unresolved for sourcing.
0SourceRecords
0ClaimRecords
88Unresolved issues
Editorial states
No automatic promotion.
Codex-created records can be drafted, marked needs_source, or marked needs_review. They cannot be promoted to reviewed, disputed, retired, rejected, or publishable merely because a schema validates.
Exact public wording
Claims distinguish fact, organizational position, survey result, research finding, interpretation, implication, contested claim, and open question. Every displayed claim must trace through SourceUse to a SourceRecord.
Auditable state
Review states are draft, needs_source, needs_review, reviewed, disputed, retired, and rejected. Current cards remain source-ready structure, not verified evidence.
Correction request
Send a correction without creating a profile.
Use this form as a local prompt for what to include. It does not store a submission in browser storage, create a public identity, require protected attributes, or request political affiliation. Contact information is optional unless you want a reply.