Doctrine

The common explanation for decision failure is poor judgement. This is almost always wrong. The actual cause is almost always structural: the decision was made before the necessary conditions for a valid decision existed.

A valid decision requires four things: a clearly stated decision question, a verified authority to make it, a sufficient evidence base, and a resolved constraint environment. When any of these is absent, the decision is not a decision — it is a guess dressed in institutional language.

Most organisational processes do not check for these conditions. They check for consensus, for speed, and for the appearance of due diligence. These are not the same things. Consensus without evidence is groupthink. Speed without structure is exposure. The appearance of due diligence is a liability.

The solution is not better judgement. The solution is a framework that refuses to produce an output until the conditions for a valid decision are met.

There is a persistent confusion between validation and recommendation. A recommendation is an opinion — it reflects a preference shaped by assumptions, experience, and framing. A validation is a structured assessment of whether a decision meets a defined standard of evidence and authority.

VFS does not produce recommendations. It produces findings. The difference is precise: a finding states what the evidence supports, what it does not support, and where the evidence is absent. It does not tell a decision-maker what to do. It tells them what their decision is actually built on.

This distinction matters because in high-stakes environments, the liability does not attach to the recommendation — it attaches to the decision. If the decision-maker can demonstrate that their choice was based on validated evidence, they have a defensible position. If they acted on someone's opinion, they do not.

Validation is not a softer version of advice. It is a harder one. It requires more rigour, more documentation, and more willingness to issue an inconvenient finding.

The veto is the most misunderstood function in any decision system. It is treated as an obstacle — a sign that the process is broken, that someone is obstructing progress, that the system is too cautious.

This is precisely backwards. The veto is the system working correctly. It is the mechanism that prevents a structurally deficient decision from entering the record. It is not a block on action — it is a block on premature action.

A veto does not mean the decision cannot be made. It means the decision cannot be made yet. The veto creates the conditions for the decision-maker to return with the missing evidence, the resolved constraint, or the clarified authority. In doing so, it produces a better decision than would have been made without it.

The measure of a decision system is not how many decisions it approves. It is whether the decisions it approves are defensible. The veto is the mechanism that maintains that standard.

In forensic evidence, chain of custody is the documented record of who held a piece of evidence, when, under what conditions, and what they did with it. A break in the chain renders the evidence inadmissible — not because it is false, but because it cannot be verified.

Decisions require the same standard. Who framed the decision question? Who submitted the evidence? Who reviewed the constraint matrix? Who held authority at each stage? When did each event occur? These are not administrative details — they are the architecture of a decision's defensibility.

When decisions are challenged — legally, regulatorily, or institutionally — the challenge rarely goes to the substance of the conclusion first. It goes to the process. Was the right person involved? At the right stage? With the right information? A decision without a documented chain of custody cannot answer these questions.

The discipline of maintaining chain of custody in decisions is not bureaucratic. It is the difference between a decision that can be defended and one that cannot.