ChiefLab Execution Contract
Any tool that follows this contract is an operator. Operators interoperate, persist state, gate execution behind human approval, and report measurement back into shared memory. Stateless LLMs draft; operators close the loop.
Versions
Why this exists
ChiefLab is the execution layer for agents doing business work. The contract names the irreducible stateful primitives — workspace memory, approval state, signed review URLs, idempotency, run lineage, cross-launch measurement — that a stateless LLM cannot replicate.
The point of versioning the contract publicly is generality. If only ChiefLab follows it, it's a single product's API surface. If a second operator follows it (and a third, and a fourth), it's infrastructure.
Conformant operators
ChiefLab ships eight reference implementations: six in v0.1 (chieflab-launch, chieflab-post, chieflab-email, chieflab-measure, chieflab-brain, chieflab-connect) plus chieflab-reply (inbound reply loop) and chieflab-outbound (cold first-touch) added post-v0.1. The live registry is at /.well-known/mcp.json under operators.
Building an operator that follows this contract? Email hi@chieflab.io and we'll list it.
Feedback
The spec is in draft status. We want feedback before locking v1.0. Open an issue at github.com/bdentech/chiefmo-agent, email hi@chieflab.io, or DM @chieflab on X.