Prepare an editorial briefing
Build a source-linked draft for a real author and reviewer.
This tool stores a draft only on this device and exports an editorial submission. It does not publish, email or mark the draft reviewed. The operator validates the submission in config/briefings.yaml; a named reviewer must attest to a review before publication.
Loading a research draft does not save over a local draft. The automated author is cleared so a real author can revise and take responsibility for the final text.
- Write an original explanation with a clear scope and identified author.
- Link the original evidence and the dataset version used.
- Have a real reviewer check sources, dates, identities, uncertainty and counts.
- Record the reviewer’s identity, attestation and actual review time in the operator workflow. Drafts and incomplete reviews stay unpublished.
The exported JSON document is valid YAML 1.2 and always has review_status=draft. A browser action cannot establish a real review or reviewer attestation.
After editing the operator’s configured submission, the actual author and reviewer can attest the exact final content through python -m pipeline.build_briefings --attest ISSUE_ID --author "Author name" --reviewer "Reviewer name" --confirm-human-review. That attestation is valid only after the people named have personally reviewed the final text and linked evidence. Later edits invalidate the attested hash.
Operator measurement status
Search Console and Bing metrics belong in the private operator dashboard. Public connection status shows only whether a provider is connected and when it was updated.
Published reviewed briefings · Correction workflow
Content updated · sources and retrieval health are documented on the coverage dashboard.