YOUR POLICIES. EVERY NEXT STEP.
See control in motion.
Run a workload, change a rule, and follow the decision.
- 1Run sample
- 2Update policy
- 3Inspect evidence
Keep the next action inside its region.
A regional restriction changes while a mixed queue is already in motion. See which work can continue, which results are held, and what cannot be recalled.
Released successfully
Includes failed attempts
Unsettled external work
Requires a next decision
Workload queue 6
A small queue. A consequential policy change.
| Workload | Endpoint | State | Policy | Est. |
|---|
Dispatch, retry, and result release are separate protected actions. A new policy is checked at the next supported boundary.
Policy comparison
Compare the next-action rules before applying the update.
| Protected action | v12 Before | v13 After update |
|---|
Inspect active policy details
Before dispatchEvaluate the current policy before sending a new request.
Before retry or fallbackRecheck eligibility and reserve the new attempt's exposure.
Before result releaseApply the current release rule, even if execution used an earlier version.
External work already accepted may continue. This simulation holds the next protected action and retains unsettled cost reservations; it does not claim to undo a request or an earlier data transfer.
Decision evidence
Every transition keeps its policy version and reason.
Illustrative evidence, generated in this browser session. No external requests.
JSON includes the complete snapshot. CSV contains the decision ledger, with settled and reserved cost at each event.
SCENARIO COMPLETE