Permission

In any plant where a machine can kill somebody, there is a procedure for making it safe before a person puts their hands inside it. The energy sources are isolated, the isolation points are physically locked, and a tag carrying the name of the person who applied the lock is attached to it.

The interesting part is not the lock. It is the rule about who may remove it.

Only the person whose name is on the tag may take their lock off. Not their supervisor, not the plant manager, not the shift that comes on at six. If several people are working on the machine, each applies their own lock to the same isolation point, and it cannot be re-energised until the last of them has personally removed theirs. Where somebody has gone home with their lock still on, removing it is a documented event with its own authorisation and its own record.

Look at what that arrangement encodes. A permission, in this case the permission for a machine to hold energy, is attached to a specific physical scope. It carries the name of a person who can be found and asked. And it is revocable by that person and, absent a deliberate documented exception, by nobody else.

Notice also what it does not rely on. It does not rely on the machine being reluctant to start. There is no assumption anywhere in the procedure that the equipment will decline to energise because starting would be inappropriate. The whole apparatus is built on the opposite assumption, which is that the machine will do exactly what it is capable of doing the moment it is able to, and that the only reliable control is the one that removes the capability rather than discouraging its use.

That is permission, and it is the first of the three disciplines in the Process layer. Before a system runs, somebody with the authority to grant it decides what it may touch, on whose behalf it acts, and who may extend or withdraw that. Written as a scope rather than a policy. Owned by a name rather than a committee. Revocable in practice rather than in principle.

Part two ended by handing four things to this part of the book. Marking assisted output at the moment of creation needs somebody to be required to do it. That requirement is a permission, and this chapter is where it gets specified.

Between 26 June and 19 July 2026 there was a demonstration, at considerable scale and on the premises of the best-resourced laboratory in the industry, of what happens when a permission is granted for a purpose and is not bounded by the purpose it was granted for.