Operating manual
Tag: Agent Governance
A focused reading path for Agent Governance: related field notes, evidence trails, and operating questions from the archive.
- agent-work-needs-chain-of-custody-not-just-bigger-models.md
Agent Work Needs Chain-of-Custody, Not Just Bigger Models
A four-question acceptance test for trusting agent work: who authorized it, what state crossed the handoff, what evidence proves completion, and what recovery path exists.
open artifact → - agent-work-needs-chain-of-custody-not-just-capability.md
Agent Work Needs Chain-of-Custody, Not Just Capability
A four-question acceptance test for trusting agent work: who authorized it, what state crossed the handoff, what evidence proves completion, and what recovery path exists.
open artifact → - agent-teams-need-governance-before-they-need-another-protocol.md
Agent teams need governance before they need another protocol
Protocols make agent collaboration possible. Governance makes it safe enough to delegate: authority, state boundaries, evidence, review, and rollback.
open artifact → - the-agent-stack-is-getting-protocols-before-it-gets-governance.md
The Agent Stack Is Getting Protocols Before It Gets Governance
MCP, A2A, and agent SDKs make agents easier to connect. Production trust depends on the control layer above them: authority, review, evidence, recovery.
open artifact → - the-agent-stack-governance-checklist-authority-review-provenance-and-handoffs.md
The Agent-Stack Governance Checklist: Authority, Review, Provenance, and Handoffs
A practical checklist for designing authority, review, provenance, and handoff gates around MCP, A2A, and agent SDK workflows before they touch production work.
open artifact → - protocols-make-agent-exchange-legible-governance-still-lives-above-the-protocol.md
Protocols Make Agent Exchange Legible. Governance Still Lives Above the Protocol.
A2A and MCP make agent exchange easier to standardize, but they do not decide authority, review, provenance, memory, escalation, or accountability.
open artifact →