ACTIVE  ·  BUILDING  ·  v2026.11.20 BUILD 2026-11-20  ·  JL:IOTA:001
No. 126 · 2026-08-16

Build Provenance Into the Workflow

Claude's watermark answers one narrow question. Your workflow still has to answer the rest.

DISPATCH  ·  LOGGED WITH MAI

Anthropic says future Claude models will watermark text. A statistical pattern in the word choices that can later show Claude was probably involved, without a visible mark or metadata.

The easy read is compliance. The useful read is workflow.

A watermark can tell you a model touched a piece of text. It cannot tell you who asked for it, what source material it used, who edited it, whether legal saw it, or why it ended up in the CMS without a disclosure note.

That is the part companies keep trying to skip. Detection identifies involvement after the work escapes. Governance belongs upstream: in intake, review, asset records, approval queues, and handoffs between tools.

Every customer-facing content path now needs provenance attached to the asset. Which system touched it. What it did. Who reviewed it. What label, if any, belongs on the final thing.

The watermark flags possible involvement; provenance controls belong upstream. If it tells you something you did not already know about your own content, the failure happened upstream.

LOGGED WITH MAI  ·  2026-08-16  ·  No. 126
← All Dispatches