Orchestrator Contract: One‑Line SLOs for Composite Automations

Core insight: modern value often lives in composite workflows that stitch agents, services, and human steps; the failure mode is not a single bug but a mis‑expressed expectation across boundaries. The Orchestrator Contract is a tiny, machine‑readable SLO you attach to any composite automation: EndToEndLatency | SuccessRateThreshold | DegradeMode | CompensationAction | ObservabilityProbe | Owner | RollbackLeash. In ten minutes I define the contract, show three enforcement primitives you can add with minimal engineering (pre‑deploy synthetic run that must pass the contract, automatic degrade patterns plus compensating transactions, and a one‑click rollback leash tied to the contract), and give two constrained AI prompts to infer candidate SLOs from traces and to synthesize a minimal degrade script. I close with a 7‑day pilot: pick one multi‑step flow, publish its Orchestrator Contract, run synthetic scenarios, and measure mean time to contain and customer exposure. Fast action: publish tonight’s contract and subscribe. Stay agentic.