How weekly reports work. i
Public report history includes published versions, superseded corrections, retracted tombstones, and a weekly Atom feed. Every frozen version pins named human decisions, exact chain versions, public evidence hashes, and a research snapshot.
Evidence boundary: A superseded version remains available for audit and points to its replacement. A retracted version remains as a tombstone. Upstream prepares evidence and citations but never writes or approves the conclusion.
Next useful action: Open a published version to audit its history, or subscribe to the weekly feed. An authorized editor opens an assigned draft in the analyst workspace.
Journey context 2 active, 3 steps ⌄ Current route guide: How weekly reports work Active journeys: Read a stable weekly account Publish correct research View all journeys 1 Review the latest frozen public version and correction history before opening an editable draft. 2 Read its source cutoff, content hash, and human-authored narrative. 3 Subscribe to the Atom feed for new published versions, then trace each finding into its cited chain and public evidence. Hide explanations Current route guide: How weekly reports work Active journeys: Read a stable weekly account Publish correct research View all journeys 1 Review the latest frozen public version and correction history before opening an editable draft. 2 Read its source cutoff, content hash, and human-authored narrative. 3 Subscribe to the Atom feed for new published versions, then trace each finding into its cited chain and public evidence. Next useful action: Open a published version to audit its history, or subscribe to the weekly feed. An authorized editor opens an assigned draft in the analyst workspace.