Reads the ticket, picks the tool, chooses the arguments, and decides to try again when a call errors. This is the part you built, and CTRLRun never touches it.
Sees no prompt, no reasoning, no chat. It sees one thing: the action about to leave your process, with its exact arguments. It answers whether that may execute now, and records what happened.
Stripe, your database, the Kubernetes API, an email server. None of them can tell a first attempt from a retry, and a lost reply looks exactly like a failure.
CTRLRun is not a model, a prompt layer, or a guardrail on what the agent says. It is the check on what the agent does, in the last moment before the effect is real.
No matching domain. Try “Payments” or “DevOps”.
}THE AGENT ASKS TO
{stateKey === 'mismatch' ? changed : original}
{stateKey === 'mismatch' ? 'A person approved: ' + original : 'One consequential action, in ' + domain.toLowerCase() + '.'}
EFFECT KEY{effectKey}
✓ Action recognized
{result.reason}
{result.llm}
{result.kernel}
{result.rule}
WHAT YOUR CODE SEES{result.sees}
{result.code} {result.doc.label} →
{trail.length > 0 &&Nothing here executes: this is an illustration of the decisions, with example rules that are not industry defaults. To watch the real library refuse a real call, run the released wheel in your browser: Python and CTRLRun load into the tab and every refusal there is the library's own.{physical ? ' CTRLRun governs the software authorization and execution workflow; physical safety controls remain separate.' : ''}{domain === 'Healthcare Operations' ? ' Administrative workflows only; no diagnosis or clinical decisions.' : ''}
Review where execution controls belong in your architecture.
TRY THE EXECUTION BOUNDARY
Your model chooses the action. CTRLRun decides whether it may execute.
Pick one of 48 domains, then pick the moment it goes wrong: an action the agent was never allowed to take, an approval the agent edited, a retry of something that already happened, a reply that never came back. You get the decision, the check that produced it, and the line your own code would see.
No login. No API key. No setup. Nothing here executes.
Every scenario has its own link, so you can send someone straight to the one that matters.
THIS PAGE IS AN ILLUSTRATION
Nothing on this page runs CTRLRun. It draws the decisions so you can see where they land in a domain you recognise. One page further, real Python and the released wheel load into your tab, and every refusal you read there is the library's own.
An illustration of the checks, with example rules that are not industry defaults. No code runs, no request is sent.
Real Python, the released ctrlrun wheel, in your browser. Change a refund after approving it and read the exception the library raises. Run it in your browser →
WHERE TO GO NEXT
Apache-2.0 · Runs in your environment
Where CTRLRun sits, what it checks, and what it deliberately does not do. The plain-English version, then the architecture.
pip install ctrlrun, then wrap the function that causes the effect. The quickstart adds your policy, identity and approval flow.
Approval binding, effect keys, and outcomes and AMBIGUOUS: the three the demo leans on hardest.
The medical affairs workbench puts the same kernel under a document release instead of a payment.
Not sure where the controls belong in your architecture? A focused review maps which of your agent's actions can run automatically, which need a person, and which must stop until the outcome is known.
Get an execution-safety review →