Notas del episodio
Your team has thirty minutes to publish a document. Someone asks whether AI wrote it. Nobody has checked whether it is right.
In this 20-minute AI Change Desk episode, Michael asks what a watermark can establish, what it cannot, and who still owns the publication decision. A detector can be right while the document is wrong.
Context: OpenAI's October 5 text-provenance announcement separates opt-in marking from restricted detector access. Its October 8 false-front report adds a different question: have you verified the contributor behind the submission?
Impact: a provenance result does not settle factual accuracy, authorship, ownership, or permission to publish. No detected mark is not proof of human authorship. EU Article 50 also distinguishes provider marking from deployer disclosure and substantive editorial responsibility.
Action: run one fictional workshop notice through three invented result cards: detected, not detected, and unavailable. Keep the factual error and contributor gap identical. Check the event details, the actual assistance policy, permission, and the accountable publisher before deciding what goes out.
This continues episode 48's stop-and-restart discussion by moving to the publication desk: the work is already written, but your responsibility is not finished.
The scenario and detector results are fictional, not vendor tests. OpenAI's incident and product claims remain attributed to OpenAI; multiple OpenAI pages are one source family, not independent validation. No deployed detector accuracy or organization-specific legal conclusion is claimed.
- OpenAI: Our approach to EU text provenance rules, October 5, 2026
- OpenAI: Provenance signals and detector-access limits
- OpenAI: Disrupting AI-enabled false-front operations, October 8, 2026
- European Commission: AI Act Article 50
- European Commission: Article 50 transparency FAQ
The narration records an October 10 source check. These official pages were rechecked before release on October 12, 2026. Product scope and access rules can change.
AI-assisted tools were used in parts of the research and production workflow. Final editorial judgment, risk posture, and release approval stayed human-led. This is operational guidance, not legal advice. These are my opinions and are not representative of any organization.
My current role includes privacy work, so you will hear me pay closer attention to purpose, access, retention, deletion, and accountability. I will not discuss nonpublic work here. These are my personal views and do not represent the State of Oregon or any other organization.