Book a demo

Technical

Why we put the guardrails in the playbook, not the model

Model level safety is necessary and insufficient. Blast radius, step budgets and read write separation belong in the workflow definition where an auditor can read them.

Ollie, founder

8 minute read

Frame the distinction: model behaviour is probabilistic, workflow scope is declarative. Only one of those can be audited.

Walk through the four constraints declared per playbook: tools, step budget, timeout, blast radius.

Explain read write separation at connector level and why it survives a model being wrong.

Cover the failure path: what happens when a workflow exceeds budget or cannot evidence its reasoning.

Close on the accreditation angle. A reviewer can read a playbook. They cannot read a model.

Get started

Bring a week of alerts nobody got to.

Book a demo