Operations begins where observation ends: an operator chooses an explicit disposition against exact retained authority, and the engine records the resulting state change.
Commands need stronger coordinates than dashboards
Seeing that an instance is Faulted or Parked is evidence. Replaying its retained stimulus, interrupting the root, or redriving outbound delivery is a command. Each operation must address the exact root, Park journal, incident, or delivery intent it is meant to change and must refuse when that authority is stale.
StatechartOps owns these operator-facing decisions. It does not expose a generic “set status” or
let a UI reconstruct recovery input from logs. The command consumes structured engine authority;
the next committed facts explain what it changed.
Start with parked instances
The current guide keeps incident evidence and Park commands together so one worked example can show the handoff. Semantically, the incident belongs to Observability; only the operator disposition belongs here.
Know the current public boundary
Park replay and interruption have public operator surfaces. Outbound-delivery redrive belongs in this category too, but it should not receive a canonical how-to page until its public operator contract is stable. Internal storage functions are not documentation APIs.
Next, Incidents & Parking follows one exact failure from immutable evidence to an explicit operational decision.