Operating manual
Tag: mcp
A focused reading path for mcp: related field notes, evidence trails, and operating questions from the archive.
- 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-is-getting-protocols-before-it-gets-accountability.md
Accountability Starts After the Agent Handoff
MCP and A2A can move work between agents. Accountability starts when the receiving system can prove who authorized the work, what changed, what evidence survived, and who owns rollback.
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 →