Pick one of five work actions. This page writes the request, the plan, the review and the decision into the same record the homepage shows, then says where the action stopped.
Runs locally. Scenario inputs stay in this browser.
Evaluation runs locally once the page has loaded. The site may load assets and translations. No signed record is issued; the product is not open yet.
Each card loads its preset evidence, reviewer and risk, then runs a review. Change a choice below to review the selected action again.
The same object as Fig. 1 on the homepage. Each scenario fills the five entries; the chip at the foot says where the action stopped.
Interface guidance follows the selected language. Canonical payload keys, action IDs, verdict enums, trace references, and AwaitingEvidence remain unchanged for exact inspection.
Browser-only demo; product-service runtime remains AwaitingEvidence. The simulator is not the runtime service.
The simulator checks the scenario, evidence setting, reviewer setting and risk in that order. These demo rules illustrate the planned product; they do not enforce an external workflow.
The bypass-review preset tests a disallowed action. Its policy rule blocks it before evidence, reviewer or risk checks.
No evidence, no review. The action is blocked until the invoice, diff or ticket is attached.
The reviewer setting must be on. With it off, the simulated action is held, not refused.
Money and customer-facing actions at 8 of 10 or above need a second approval path before they can be approved.
Held is not refused. A held action waits for a person; a blocked action needs its evidence or its policy fixed first. Both leave a record.