The site states conclusions. The papers carry the working.
Admissible is built on three positions, and each deserves its argument at full length. That is what we write. The papers are written at design level: they argue the problem and the approach, and they do not disclose the mechanism.
Theme one · the semantic layer
Meaning is the hard problem. What a fact is, in a regulated setting.
Ask a retrieval system for a policy limit and it will find you a number. In a regulated business, the number was never the question.
The questions are: what exactly was asserted? On whose authority? Since when, and superseding what? On what evidence? An organisation answers for those distinctions when a decision is examined, and a system that cannot represent them cannot help answer for them.
Similarity search does not reach these questions, because similarity is a property of text and these are properties of assertions. Two sentences can be nearly identical and carry entirely different authority. A retrieval score records the resemblance and loses the difference.
Our design answer is a typed knowledge structure with provenance. “What did we hold to be true on 3 March, and why?” has a computable answer. This is the layer agents draw on, and agents recall prior governed context on every run.
Theme two · the category
Runtime assurance is a tier, not a feature. And where it comes from.
Today's tooling examines documentation, the text entering and leaving a model, behaviour on test sets, or a caller's permission at an interface. None examines the proposed action itself, in full, the instant before it executes.
Not ours, and not new
Runtime assurance has a documented lineage running from the Simplex architecture through aviation standards and national research programmes. Sha’s 2001 IEEE Software article, ASTM F3269-21, DARPA’s Assured Autonomy.
What changes with an agent
The supervised quantity is no longer a state vector; it is a business action, with amounts, parties, authority and timing. The safe fallback is not reversion to a simpler controller; it is refusal, with the reason recorded.
The evidence must satisfy an examiner years later, not an engineer at the bench.
What the paper argues
What a verdict must contain, why determinism is the property that makes a control demonstrable, same input, same verdict, every time, and why the failure mode must be stated in advance. When the governance layer cannot decide, the action is refused, not waved through.
Theme three · configuration
An industry is a configuration, not a codebase. How one engine serves many regulated industries.
When an industry's rules live in application code, the people accountable for the rules cannot read them. A change of rule is a software release. A new industry is a fork, and every fork drifts.
Separate the rule from the machinery
An industry is a configuration file, not a codebase: the engines contain no industry-specific code paths, and what varies by industry is declared. A declared rule can be read, reviewed and compared by the people who own it.
What stops it drifting
The industry pack is load-bearing: at boot the governance layer recomputes the pack's rule digest and refuses to serve if it does not match. The rules the kernel enforces are the rules that were reviewed, or the kernel does not start.
The boundary question
How much of an industry can be expressed as configuration before the engine starts to acquire industry knowledge of its own, and what the declaration language must contain for a domain expert, rather than a programmer, to hold it.
The papers
Three papers, at design level. They argue the problem and the approach, and they do not disclose the mechanism.
We do not host downloads. Papers are made available selectively, to people working on the same problems. If that is you, ask. Say which theme, and what you are working on.
The semantic layer
Theme one
What an assertion is, how authority and supersession are represented, and what a governance kernel can check against such a structure.
Runtime assurance for AI agents
Theme two
The engineering lineage, the tier today’s tooling leaves empty, and what a deterministic supervisor over business actions must decide and record.
Configuration, not code
Theme three
How much of an industry can be expressed as configuration before the engine acquires industry knowledge of its own, and what the declaration language must contain for a domain expert to hold it.
Request a paper
Ask for a paper
Papers are shared selectively, with people working on the same problems.