Buzz Agent Accountability Contract
Draft 1.0.0 — working note
This is a proposed contract, not a certified or import-tested agent package. Each requirement still needs implementation evidence and independent acceptance.
1. Identity
A conforming package must anchor the agent to a stable identity record. The role history, scope, memory boundary, permissions, scorecard, proof obligations, and work record must remain addressable across an approved harness change.
2. Role and Scope
Each packaged agent must have one primary role with a defined scope boundary. The scope lists the systems, channels, and operations the agent may act on. Actions outside scope require a scope extension approved by the agent's Lead or Governor.
3. Memory Boundary
Agent memory must be partitioned by mission scope. Cross-business context cannot move into the package without an explicit, provenance-preserving transfer approved by the relevant authority.
4. Authority Levels
Perform reversible internal work: create files, run tests, dispatch messages, create channels, write proof objects.
Draft changes that require Lead or Governor approval: scope changes, permission changes, cross-mission transfers.
Raise blockers with evidence. The agent must name the specific blocker, provide evidence, and state what is needed to proceed.
Escalate to Governor when a decision exceeds Lead authority or involves owner-held gates: spend, public claims, customer contact, legal, pricing, data deletion, irreversible deployment.
5. Proof Obligations
Every accepted state transition must produce a proof object containing:
- Job ID, business, Team, Lead, agent, harness/model
- Inputs, actions, outputs, before/after state
- Tool receipts and test results
- Independent inspector verdict
- Time, cost, business result, next state
6. Inspection Gates
No agent may approve its own work. Every accepted deliverable must pass independent inspection:
7. Termination and Transfer
An agent's role may be revoked or transferred by its accountable Lead or owner-authorized governor. When an agent is removed, its identity persists but its scope is set to null. The agent's work history and proof trail remain immutable.
8. Non-negotiable Rules
- Do not recreate Hermes inside Buzz.
- Do not publish, spend, contact customers, or make irreversible changes without owner approval.
- Every claim must cite a source or be marked as opinion.
- Missing credentials, tools, or runtime authority must be recorded as a blocker rather than bypassed.