The agentic policy workshop, and designing and building the software.
Governance programmes and agent products usually govern the model, the prompt, the output, or a sample of process steps and paths. They do not fix, outside the run, what every acceptable action must satisfy, which assumptions claims depend on, and what remains to be trusted. Simply allowing an action to run does not settle any of that.
The Compliance Operator is the product that enforces a stated policy before a tool call runs. The workshop facilitates how you write, for one workflow, the policy that the product will enforce. The notation is in the glossary, Trust and Proof, Goal-Relative Assurance, and Agentic Process Governance.
For one workflow, write what every acceptable action must satisfy, which assumptions that claim depends on, and what is still trusted. That is the authority map. It is what the Compliance Operator enforces.
The agentic governance and policy workshop →We build high-assurance software in Lean, for financial markets and other regulated industries. The engagement states the same limit the workshop writes, then builds the gate: what we will build, what the proof shows, which assumptions it uses, and what is still trusted.
Talk about a software engagement →