Operate Runs
Use safe-point controls and durable journal evidence without rewriting committed execution history.
Before you begin
Open the exact Run address and inspect its current scheduler state, terminal status, journal head, pinned Agent, Resource snapshot, budget, and open waits. Controls require specific Policy actions such as run:pause, run:resume, run:cancel, or run:truncate.
Steps
- Use Pause to stop at the next safe point while preserving durable state.
- Use Resume to continue from the recorded scheduler state.
- Use Interrupt to add operator guidance before the next safe boundary.
- Use Rebind only when the new Resource map satisfies deployment contracts and scoped authority.
- Use Rewind history to branch from an earlier fact with explicit continuation guidance.
- Use Cancel when future work must stop; committed facts remain recorded.
Verify
After a control, confirm the receipt is durable, the scheduler state matches the request, and the journal records the transition. A timeout or uncertain Resource outcome requires reconciliation evidence rather than blind repetition.
Next steps
Inspect Agent operations for deployment identity or Channel operations for delivery evidence.