What happened?
On 2 August 2026, the EU AI Act’s Article 50 transparency obligations became enforceable. Anthropic — a signatory of the Code of Practice on Transparency of AI-generated Content — states that Claude models launched on or after that date will ship with machine-readable marking from day one.
Two layers:
- Embedded text watermarks — imperceptible signals woven into generated text. Invisible to readers; intended to travel with copy-paste and survive some light editing.
- Signed provenance metadata on files — C2PA Content Credentials on supported types (e.g. PNG, JPG, SVG), recording that Claude processed the file.
Marks apply across Claude products and cloud partners (API, claude.ai, Claude Code, and major clouds) worldwide, not only EU traffic — with the usual caveat that some surfaces may not support every mark type.
Models released before 2 August sit in a transition window: Anthropic says it is working to backfill marking. Detection tooling for third parties is still rolling out (“forthcoming documentation”).
Why this is interesting
- Regulation forced a product surface — Article 50 does not ask labs to “be transparent in a blog post.” It requires machine-readable marking plus a path to detection. Watermarking and C2PA are no longer research demos; they are shipping obligations for anyone selling generative systems into Europe.
- Text is the hard case — Images and video can carry C2PA manifests and pixel-space watermarks. Free-form chat text has no durable container. Anthropic’s answer is a mark inside the token stream — which is exactly where robustness is weakest (paraphrase, translation, heavy edit, short snippets).
- Signal ≠ verdict — Anthropic is explicit: a detected mark means content may have been processed by Claude, not that Claude originated the idea, and not that the text is unaltered. Absence of a mark proves almost nothing (old model, stripped metadata, aggressive rewrite).
- Agentic systems inherit the mark — When Claude Code or an API agent writes a README, a PR description, or marketing copy, the watermark rides along if the model is in the marked cohort. Downstream deployers still have their own Article 50 duties; the lab mark is necessary infrastructure, not a free pass.
- The arms race is removal, not detection theater — Text watermarks that survive casual copy-paste fail against deliberate scrubbing. Industry commentary has been blunt: perfect, unremovable text watermarks are theoretically ugly. Expect a market for cleaners — and a parallel market for auditors who treat provenance as one weak signal among many.
What it means in practice
| Cohort | Expectation |
|---|---|
| New Claude models (launch ≥ 2 Aug 2026) | Text watermark + C2PA on supported files |
| Pre-cutoff Claude models | Transition; marking not guaranteed yet |
| Heavily edited / short text | Detection may fail even if originally marked |
| Builders embedding Claude | Still assess your deployer obligations under Article 50 |
Provenance is becoming part of the default stack — like TLS certificates for content origin, incomplete and stripable, but increasingly the cost of doing business in regulated markets. The interesting question is not whether watermarks exist. It is whether enterprises and platforms will treat a missing mark as suspicious by default, the same way browsers treat missing HTTPS.