Intent, not unrestricted access
Agents emit structured results under contract.
ESAA / PROTOCOL 0.4.1
ESAA turns autonomous execution into a governed process: every intent is validated, recorded and projected before producing effects.
01 / WHY
Agents are probabilistic. Operational systems need deterministic rules. ESAA separates both worlds so decisions can be audited, reproduced and reviewed.
Agents emit structured results under contract.
Only the Orchestrator admits events and applies effects.
Completed tasks are not rewritten; corrections become new events.
02 / ARCHITECTURE
The append-only event store is canonical. Roadmap, issues and lessons are rebuildable projections — useful for reading, never for manual editing.
03 / WORKFLOW
Watch a task move through the protocol. Each transition admits a new event; the event store preserves history while the roadmap reflects the current state.
task.createdtask.claimed · agent-impltask.completed · 2 filesreview.approved · agent-qa04 / QUICKSTART
python -m pip install --upgrade --pre esaa-core
mkdir esaa-demo && cd esaa-demo
esaa bootstrap --profile public
esaa init
esaa verify
esaa eligibleThe first expected signal is verify_status: ok. The runtime operates locally over the governance directory and does not require MCP.
05 / RUNNERS
Provenance on every admitted event.
The same contract regardless of surface.
Deterministic automation leaves receipts too.
06 / TRUST
07 / DOCS