Governance · Depth page — for buyers who want the mechanics spelled out
How the council works.
The landing page previews the council and the chairman ruling. Below is the depth version: the five agents and what each argues, the three rulings the chair can issue and what happens to dissent on each, and the rule that ties the run back to you — the named human on the case file — with a typed reason attached before any stage advance.
§ 01 · The council
Five agents with fixed remits, opening objections by default.
Each agent is tuned to a single angle and opens dissent first, demands evidence next, and only then supports. The five are deliberately not optimisable away from one another — opposing defaults is the point.
§ 02 · The chairman’s ruling
Build · Test first · Walk away — and the dissent is filed before the forge advances.
The chair never overrides an unresolved objection. When the council cannot settle, and any verdict is contested, the case is held at the current stage and the dissent is written into the audit trail before the run moves on.
§ 03 · The human tiebreaker
When the council cannot settle, the named human decides — with a typed reason attached.
The named human approver attached to the case file signs the ruling — approve, return, or refuse — with a typed reason recorded verbatim. The same named-human + typed-reason mechanic applies to every stage gate, not only to the chair’s tiebreak.
Want to see the whole pipeline on a real case file? Read the sample brief — a worked example with five named human approvers, from the verbatim intake to the Software Build receipt.
Still want the shape in the words of a regulated buyer? Read the FAQ or leave a one-line brief to start a run the way a regulated buyer actually does.
Ready to brief a real council? Request a council walkthrough — an at-depth form for regulated buyers who are past the front-door brief and want a pre-procurement engagement routed by an actual human.