Design notes
Design
Design notes for the supervisor architecture's core contracts.
Contract-level documentation for the parts of the runtime that callers depend on.
| Page | Contract |
|---|---|
| Provider contract | Capability records, stateful vs. stateless, resolution and validation |
| Declarative provider bindings | Config-only provider onboarding for compatible CLI framings |
| Config virtual layers | USER/PROJECTS layering, changes vs. overrides, conflict diffing |
| Orchestrator-verified completion and A2A | Why a worker never marks its own work done, and the A2A vocabulary that carries evidence |
| Deterministic execution | What is reproducible about a run — and what deliberately is not |
| Exact provider identity | What identifies one invocation, why strict binding compares the resolved model, and what the record does not prove |
| Plan-adaptive concurrency | How readiness, leaf-group partitioning, and output reservations decide what runs at once |
| Provider write containment | What actually stops a provider writing outside the checkout, and where that guarantee does not yet hold |
| Canonical enforcement policy | Shared finite lifecycle, acceptance predicates, waits, budgets, and adapter parity |
| Generated enforcement adapters | Absolute hook commands, managed-session boundary, atomic bundles, and Stop verification |
