Capability is not permission
A system that can write a payment instruction is not, by that fact, entitled to issue one. Businesses have understood this distinction for centuries: a bookkeeper can prepare a payment run, a director approves it. The control lives in the separation, not in the competence of either party.
As software begins to take multi-step action, that separation has to be rebuilt inside the software. Otherwise capability quietly becomes permission by default.
Four questions before any consequential action
We hold that any action with a real-world consequence — money moving, a message leaving the business, a record changing, a commitment being made — should be answerable on four points before it happens.
- Identity: who, specifically, is behind this request?
- Permission: are they entitled to this action on this data?
- Authority: is the action within the limits set for them, including value and scope?
- Verification: has a person confirmed it where confirmation is required, and is that confirmation recorded?
Why 'human in the loop' is not enough on its own
A general commitment to human oversight tends to degrade under volume. If every action requires the same click, the click stops carrying meaning. Useful oversight is selective: it concentrates on the actions that are consequential and lets the rest proceed.
That requires classifying actions in advance rather than asking a person to judge each one in the moment.
The audit trail is the product
After the fact, the question is never "was the model good?" It is "who authorised this, on what basis, and when?" A record of that is what allows a business to delegate work to software and still answer to a client, an auditor or a regulator.
How this shapes 8ORA
8ORA is built so that preparation and action are separate stages. Work is gathered, drafted and assembled freely; anything consequential waits. IrisKey.ai is the layer that answers the four questions above and keeps the record of the answer.
We are explicit about the current boundary: verification applies to the actions we have built it around, and we would rather name that scope than imply blanket coverage.
Written by the 8ORA team. We publish no customer names, figures or certifications we cannot evidence.