Home / Articles / Approved business mandates / Versions / v1.1.0
Approved business mandates: what changed in v1.1.0
From v1.0.0 (2026-10-21, d9d4562f2) to v1.1.0 (2026-10-21, c11b2fe2c), paragraph by paragraph.
10 paragraphs added, 0 removed, 0 changed in place, 63 unchanged. About 366 words added and 0 removed. Insertions are marked like this, deletions like this; unchanged runs are folded to one line; figures appear as their file names.
51 unchanged paragraphs, under In short {#in-short}, Where this came from {#review}, Approved business mandates {#mandates}…
Room to grow {#grow}
[figure bm-grow.webp] Room to grow: capture the process and its approved rules, then the behaviour policy, both the focus now; and, already explored in published articles, the decision policy, the workflow policy, and approval at altitude with precedent. | concept
One thing the review does not see, because it read only this exchange, is that we have already gone further than the behaviour policy in our published work. That matters, because it is part of our strength: we can evolve with a customer into more advanced cases, or give them the tools to evolve on their own.
• Three policies for an agent. The behaviour policy says what an agent may do. An Agent Decision Policy says, at a branch point, who chooses, on what evidence and within what limits. An Agent Workflow Policy says in what order things happen, with which checks between the steps.
• Allowed is not right and the Northstar twin. A refund that every control allowed and was still wrong, played through four designs, which is the sequence problem the review raises, worked on an example.
• Approve at altitude. Decisions at every level, from strategy to one agent's step, where each level may narrow the one above and never widen it, so an owner signs off once instead of two hundred times.
• Case law for agents. Principles from the top and precedent from the cases, for the decisions nobody predicted.
• Three decisions, mapped. All three policies on real scenarios, including this newsroom's own release.
We are in the product-market-fit phase, and we do not know every direction this will go. So the order matters. The focus now, especially for RiskMandate, is the first step: getting people to use the behaviour policies, and learning the best way to do it. Start by capturing an existing business process and the rules it already approves, then write the policies around it. The decision and workflow policies are the evolution path, already explored and published, for the customers whose cases need them.
10 unchanged paragraphs, under What changes now {#next}, What this does not claim {#limits}
• The advanced policies are explored, not deployed. Decision and workflow policies are in published articles, not yet in a customer's workflow.
2 unchanged paragraphs, under Where this comes from {#sources}