Home / About / Engineering / 044: The verifier's record drawn at the story, and asked for on every run
Engineering · done
044: The verifier's record drawn at the story, and asked for on every run
The verifier's record drawn at the story, and asked for on every run
| Id | 044 |
| Status | done |
| Kind | Story |
| Priority | high |
| Created | 2026-10-13T15:10:00Z |
| Source | the owner's voice memo of 13 October 2026: one more round, maybe a different model, to check independence, claims, verifications and facts; the mappings should be very factual, the analysis on top |
| Release | v0.12.20 |
| Effort | small |
| File | admin/engineering/issues/done/044-the-verifier-at-the-story.md |
Scenario
Given the vault carries data/factcheck-<date>.json
When the file has results[] rows with a story id
Then each row is drawn at its story: the date, the quote's state, the verdict and the fix
And the file's own words (who checked, how, what was not checked) are in the edition's header
Given the file has only a prose result, as the first editions do
Then the prose is drawn in the header as it is
Outcome
Shipped in v0.12.20 on this side: wire/wire.js reads every data/factcheck-*.json; the contract on each how page names it as optional; the charter's third round and the brief's schema (wire-factcheck/v1, one row per story) ask the desks for it on every run. The vault side is the desks'.
For an agent
Issue 044 on newsroom.sgit.ai: The verifier's record drawn at the story, and asked for on every run. Status done, kind story, priority high, release v0.12.20. Source file admin/engineering/issues/done/044-the-verifier-at-the-story.md.