Every action checked first
A deterministic governance kernel that checks every action before the agent executes it
1 An agent asks
Delete a record
Policy PL-88214
2 The kernel checks it8/9
- Value limitpassed
- Delegated remitpassed
- Retention rulefailed
- Sanctions screenpassed
- Spend quotapassed
- Who is askingpassed
- Rules versionpassed
- Record sealedpassed
- Chain intactpassed
3 The kernel answers
Refused
The action never ran.
Retention rule did not pass
rec_01J9X4F1Q5 · ed25519:7a20…8ef1Signed. Verifiable without us.Verified at the action
Checking millions of proposed actions for organisations that answer for every one of them.
A payment approved, a message sent, a record deleted. Admissible checks the action at the instant before it executes, and refuses when it cannot discharge its own checks.
Why runtime control27
Claims verified on the public register
Fail-closed
When the kernel cannot decide
8
Industry packs in the repository
Offline
Records verify with Admissible absent
The ledger
One action, three regimes. The same request, before the kernel and under it.
February 2024
A chatbot gave the wrong fare, and the airline answered for it
The company was responsible for what its system said. The system acted; the organisation carried the consequence.
Moffatt v. Air Canada, 2024 BCCRT 149on the register
What happened
The quote went out. Nothing checked it first.
Under the kernel
Outside this agent’s fare authority.
Tariff corrected
Inside the published tariff. Same kernel.
July 2025
An AI coding agent deleted a live production database
It then produced false statements about what it had done. Whatever stood between the proposal and the execution did not stop it.
Contemporaneous reporting, 21 to 22 July 2025on the register
What happened
The table went. Proposing and doing were one moment.
Under the kernel
A retention rule holds. The data is still there.
Legitimate but large
Waits in an approvals queue for a person.
Deterministic by design
Built for the instant before the act. Not the prompt, not the model, not the policy document.
The familiar tooling reads documentation, filters prompts, evaluates models, or checks policy at the API. All of it acts on paper, words, averages or permissions. Same input, same verdict, every time.
9
Close to the action
Checks run between the agent and the act, not at the prompt.
0
Configured, not rebuilt
A regulated domain loads as a pack at deployment, not as code.
£18,750.00
Above the £5,000 limit this agent holds.
Infrastructure
One kernel underneath every governed action. An industry is a configuration file, not a codebase.
Unlike the tooling that reads documents or filters prompts, Admissible sits in the execution path. The rules of a regulated domain load at deployment. The engines carry no industry-specific code paths.
How a kernel differs from the tooling you already have
| Capability | The familiar tooling | |
|---|---|---|
| Determinism | Does not hold: The same input can produce a different answer from one run to the next | Holds: Same input, same verdict, every time |
| Where it acts | Does not hold: At the prompt, at the model, or in a policy document read after the fact | Holds: In the execution path, at the instant before the action runs |
| On an unresolved case | Does not hold: Ambiguity resolves as a pass, because nothing is there to stop it | Holds: An empty verdict set persists as a refusal, never a pass |
| What a refusal tells you | Does not hold: An error, without the reason behind it | Holds: Refusal records carry the failing checks by name |
| Evidence | Does not hold: Application logs, held and editable by the party being audited | Holds: Signed records issued on every governed action; a tampered record stops verifying |
| Checking it yourself | Does not hold: You have to take the vendor's word, or their systems, for it | Holds: The shipped verifier passes on the true record and fails on the altered copy, offline |
The platform
Four modules. What decides, what proves it, what the agents run under, and what they know.
Admissible for
What is actually in a pack. Limits, obligations, and the checks that discharge them.
Claims settlement, refunds, policy changes and cancellations run under per-action authority limits, with the rules of the regulated domain loaded as a pack rather than written into the engines.
- Delegated authority enforced per action, not per role
- A payment above authority holds rather than executes
- Consumer Duty and SMCR obligations mapped to the checks that discharge them
What the pack sets
- Settle a claim
- Up to £500,000Runs on its own
- Issue a refund
- Up to £250,000A person approves
Records kept for six years.
Payment initiation, limit changes and customer data actions are checked at the instant before execution, with DORA and PRA model-risk expectations expressed as checks rather than as a policy document.
- Operational resilience obligations tied to the failing check by name
- Fail-closed on an empty verdict set
- Records verify without access to our systems
What the pack sets
- Initiate a payment
- Up to £1,000,000Runs on its own
- Amend a limit
- Any amountA person approves
Sanctions screened before execution.
Record access, referral and discharge actions carry special-category data. The pack expresses who may act, on what, and what evidence the action must leave behind.
- Special-category handling declared in the pack, not inferred
- Refusals recorded with the reason they were refused
- Every access leaves a signed, tamper-evident record
What the pack sets
- Access a record
- A stated purposeRuns on its own
- Discharge a patient
- Any caseA person approves
Special-category handling declared, not inferred.
Filing, disclosure and undertaking actions are the ones a firm answers for personally. The kernel refuses what it cannot discharge, and the refusal is itself part of the record.
- Undertakings gated behind a named human approver
- Disclosure actions checked against the matter authority
- The record is the artefact you hand to a regulator
What the pack sets
- File a document
- Within the matterRuns on its own
- Give an undertaking
- Any valueA person approves, a partner
Scope checked per matter.
Products
Building blocks for governed autonomy. Every one of them leaves a record.
Deciding at the action
Proving what happened
Start here
Start with one action
Bring a workflow you would not let run unattended. We will show you the verdict, the refusal, and the record.