The corpusThe licenceThe 21The aggregateThe graphSourcesHow to reach themThe vaultMethod
Published vault 2 of 2
World News Day 2026 · the outreach
The append-only working vault the agent at riskmandate.ai collaborates in: targets, a protocol, and an action log with a closed verb list.
Why this one. A second provenance chain for the things we DO, kept apart from the evidence of what somebody else published, because they fail in different ways.
Open it yourself. The key is the whole credential. No account, nothing to install, and no write capability in it.
sgit_public_read_a8a49b00593d44b72e879a8d642c51ee2f52a9d4da17651ed1b70062c43a12c1:clsc1dg4
In the official UI: open it read-only in a new tab → · From the CLI: sgit clone sgit_public_read_a8a49b00593d44b72e879a8d642c51ee2f52a9d4da17651ed1b70062c43a12c1:clsc1dg4
A read key is derived one-way from the vault key and cannot become write access. The vault key is in no file in this repository and never will be; the whole-site gate fails the build on anything shaped like one.
Beta, agent-produced. The fetching, extraction, classification and drafting here are done by software agents against frozen bytes. Nothing on this page is a legal opinion, and there has been no legal review. If you are deciding whether you may republish one of these pieces, read the terms on the piece itself and ask the publisher — that is the point we are making.
We hold all twenty-one pieces and republish none of them. Every article is linked to its original on worldnewsday.org. What is published here is the description: who wrote it, under what terms, what it links to, what words it contains. The prose belongs to the people who wrote it, and the gate on this section fails the build if twelve consecutive words of any piece appear on any page we generate.
Every number walks back to bytes we hold. Each page was fetched once, frozen to a dated snapshot in this repository and hashed with SHA-256. The counts are re-derived from those bytes by a second program before anything ships. The register → · The method →
What is in it
| Path | What it holds |
|---|---|
targets/ | One file per organisation: who writes from it, the established route, the frozen pages the route came from with their hashes, and why there is no route where there is none. |
actions/ | Append-only, with a JSON schema and a closed list of verbs. Deliberately empty at handover. |
protocol.md | The rules of engagement, in full. It binds the collaborating agent as tightly as the gates bind us. |
brief.md | What we are asking for, what we are not asking for, and the tone. Three small asks, all on the publisher's side. |
evidence.md | How to verify any claim in here against the corpus vault. |
What it demonstrates
| Mechanism | How |
|---|---|
| A second provenance chain, kept apart on purpose | The corpus vault is finished and safe to hand to anyone including the people it describes. This one holds who we are contacting and what we plan to say. Different claims, different failure modes, different audiences. |
| An agent bound by a protocol it did not write | No personal contact detail for any natural person; every action names what it stands on by hash or URL; append, never edit; escalate rather than commit the newsroom to anything. |
| Rules enforced before the vault is pushed | The section gate scans this vault's contents for any address that is not an organisation's role address, by the same published two-part rule the contacts map uses. |
| Generated, not kept by hand | build/outreach.py writes the whole thing from the same frozen bytes as everything else, so anyone can rebuild it and diff rather than trust it. |
What the vault says about itself
- Nothing has been sent. The action log is empty at handover and says so.
- Silence is data: a no-response is recorded explicitly rather than left as an absent file.
- A wrong action is corrected by a new action naming it. The original stays.
- The collaborating agent may draft, send through published routes and record. It may not commit the newsroom to anything or publish to the site.
The audit, honestly
What was checked, and when. On 2026-09-29, the published vault at obj-cas-imm-27be78556362. The credential classified as read-only, published on purpose. A clone made with that key alone — no token — was scanned file by file: 36 text files, against 8 patterns (vault-key shapes, every sgit_ prefix, AWS and OpenAI key shapes, bearer tokens, private-key blocks, and email addresses).
What was found: 22 hits, 22 cleared, 0 unexplained. Ruling a hit out is the work, so every one carries the rule that cleared it. A scanner that reports hits and no verdicts has moved the job to the reader.
Every hit, with its verdict
| File | Match | Verdict |
|---|---|---|
agent-brief.md | anj@anj.org.br | published on purpose: an organisation's role address, cleared by the rule in data/contact-rules.json |
agent-brief.md | editors@coveringclimatenow.org | published on purpose: an organisation's role address, cleared by the rule in data/contact-rules.json |
agent-brief.md | info@haitiantimes.com | published on purpose: an organisation's role address, cleared by the rule in data/contact-rules.json |
agent-brief.md | submissions@haitiantimes.com | published on purpose: an organisation's role address, cleared by the rule in data/contact-rules.json |
agent-brief.md | desk@myparaluman.com | published on purpose: an organisation's role address, cleared by the rule in data/contact-rules.json |
agent-brief.md | desk@myparaluman.ph | published on purpose: an organisation's role address, cleared by the rule in data/contact-rules.json |
agent-brief.md | editor@thequint.com | published on purpose: an organisation's role address, cleared by the rule in data/contact-rules.json |
agent-brief.md | info@reportlocal.org | published on purpose: an organisation's role address, cleared by the rule in data/contact-rules.json |
agent-brief.md | editor@thequint.com | published on purpose: an organisation's role address, cleared by the rule in data/contact-rules.json |
agent-brief.md | prensa@vocento.com | published on purpose: an organisation's role address, cleared by the rule in data/contact-rules.json |
agent-brief.md | info@confidencial.digital | published on purpose: an organisation's role address, cleared by the rule in data/contact-rules.json |
targets/brazilian-newspaper-association-anj.json | anj@anj.org.br | published on purpose: an organisation's role address, cleared by the rule in data/contact-rules.json |
targets/confidencial-digital.json | info@confidencial.digital | published on purpose: an organisation's role address, cleared by the rule in data/contact-rules.json |
targets/covering-climate-now.json | editors@coveringclimatenow.org | published on purpose: an organisation's role address, cleared by the rule in data/contact-rules.json |
targets/haitian-times.json | info@haitiantimes.com | published on purpose: an organisation's role address, cleared by the rule in data/contact-rules.json |
targets/haitian-times.json | submissions@haitiantimes.com | published on purpose: an organisation's role address, cleared by the rule in data/contact-rules.json |
targets/paraluman-news.json | desk@myparaluman.com | published on purpose: an organisation's role address, cleared by the rule in data/contact-rules.json |
targets/paraluman-news.json | desk@myparaluman.ph | published on purpose: an organisation's role address, cleared by the rule in data/contact-rules.json |
targets/quint-digital-limited.json | editor@thequint.com | published on purpose: an organisation's role address, cleared by the rule in data/contact-rules.json |
targets/the-groundtruth-project.json | info@reportlocal.org | published on purpose: an organisation's role address, cleared by the rule in data/contact-rules.json |
targets/the-quint.json | editor@thequint.com | published on purpose: an organisation's role address, cleared by the rule in data/contact-rules.json |
targets/vocento.json | prensa@vocento.com | published on purpose: an organisation's role address, cleared by the rule in data/contact-rules.json |
The negative control. The same clone attempted with an all-zeros read key fails, as it must — exit code 1. A wrong key cannot even find the vault index, because the index address is derived from the key.
What a clean scan means: nothing matching those patterns is in the current files of the published vault. It is not a statement about its history, and not a promise that nothing sensitive sits in a file matching no pattern.
Derived facts
From a read-key clone, read-only, no token, no repository — because the repository is not what was published:
- Files: 36 · plaintext size: 0.06 MB
- Commits: 5 · HEAD:
obj-cas-imm-27be78556362 - Top level:
README.md,_page.json,actions/,agent-brief.md,brief.md,evidence.md,protocol.md,state.json,targets/ - Opens as a page: yes,
_page.jsonat the root · README: yes
Notes
Where this sits. Beside the corpus vault, and in the same convention as sgit.ai’s published vaults, whose method this follows. Write-key status: held outside this repository, not escrowed anywhere it can be published. A vault whose write key is lost is frozen — readable forever, never correctable — so that status is worth stating where a reader will see it.
For an agent
The machine surface for this page is ../data/outreach-vault.json for the credential and ../data/vault-audit.json for the audit and the derived facts — both produced by build/vault_audit.py from the published read key alone. The key on this page grants read and only read.