Operating manual
Tag: ai-agents
A focused reading path for ai-agents: related field notes, evidence trails, and operating questions from the archive.
- the-authority-envelope-every-agent-handoff-should-carry.md
The Authority Envelope Every Agent Handoff Should Carry
Agent handoffs do not become trustworthy because two systems can talk. They become trustworthy when every handoff carries authority, state, evidence, risk, and the next allowed action.
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-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-next-agent-bottleneck-is-operational-control-not-model-capability.md
The next agent bottleneck is operational control, not model capability
Frontier models keep improving. The agent bottleneck is moving to state, permissions, evals, recovery, and proof that work actually shipped.
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 →