Acquire
Collect primary policy records first, then specialist trackers, reporting and public discourse. Keep the original file, URL, publication time and retrieval time. Open the operative text before writing about it.
AI Tribune is a journalistic outlet for AI policy. A reader should finish a policy page knowing how the instrument works, then be able to move from any conclusion to the exact passage, classification decision and correction history behind it.
Each policy vehicle gets an in-house article with full breadth and depth: what the instrument is, how its duties operate, who is named, what the keyed passages say, what changed over time, what the instrument does not cover, and what this record cannot yet prove. Multilateral instruments stay multilateral. They are not treated as countries. Thin stubs and link-only pages fail the desk standard.
Collect primary policy records first, then specialist trackers, reporting and public discourse. Keep the original file, URL, publication time and retrieval time. Open the operative text before writing about it.
Turn documents into passages, claims, actors, asks, policy vehicles and events. Every extracted claim keeps an exact quotation and document locator.
Match entities and remove duplicate records without erasing aliases or historical names. Canonical records sit above source-specific mentions after human review. Jurisdictions are countries, the EU and California only.
Label direct-source findings separately from cross-source analysis. Keep the evidence set and review history used for each classification.
Policy pages are journalistic briefings, not indexes. Standing, mechanism, who is bound, keyed passages, chronology, scope boundary and limits must be on the page so a reader does not need the PDF to understand the instrument.
Ship feeds, timelines and articles from the same evidence graph. Presentation can change without silently changing the underlying record. Outbound originals support verification; they do not replace the briefing.
Append corrections and superseding evidence. Never rewrite the audit history. Readers can see what changed, when, why and by whom.
Material corrections create a new version linked to the superseded statement. Minor presentational fixes are logged separately. Uncertainty is stated in plain language.