Four charts. One scheduler.

Compile the current runtime plan, drain commands first on every tick, respect stop, pause, and usage-governance gates, claim one stage at a time, then let the runtime own result application and authoritative state mutation.

Planning starts from incident or spec claims, can resume an active stage, and falls back to mechanic only when blocked routing and retry budgets say it should.

The default execution loop is sequential on purpose: verification, repair, recovery escalation, planning handoff, and update all happen under one visible runtime contract.

Successful closure stamps the target and clears the active stage. Remediation or blocked outcomes leave the target open and push the runtime back into accountable work.