The challenge
Automation that acts on its own is only useful if the business can trust it. Regulators, auditors and boards ask the same questions: who decided, on what evidence, and can it be undone. Most automation cannot answer, because it was never built to keep the record.
Our approach
Build the governance in, not on. Every automatic action runs inside rules a person has switched on, carries the evidence it acted on, and leaves a record that cannot be edited afterwards.
- Advisory by default: each suggestion records its inputs and can be accepted, edited or rejected, and the decision is logged
- Autonomy rules switched on per site by a person, such as holding a line after repeated quality failures
- An append-only audit trail on every change, with who, when, from where and which request
- Deterministic gates between any model and any action that matters: no figure is filed and no control action is taken without passing them
What we built
The same governance model runs across our own platforms. In WAJD Forge, autonomy rules and the audit log cover production, quality, payments and dispatch. In UpBasis, approval and the client's signature bind to a fingerprint of the exact figures, so any later change voids both and sends the job back for review. In our HERMES-OT research, a deterministic safety layer sits between the reasoning models and any control action on the plant.
Where it stands
Live in UpBasis and built into WAJD Forge today. HERMES-OT applies the same principle to plant cyber defence as published research with a working prototype.