The Appliance: AI Governance in Hardware · Triodian

Hardware · next

When tamper-evidence is not enough, move the check into hardware.

Software controls can be bypassed by privileged software, and the record is kept by the system under review. The appliance moves the check into a dedicated hardware datapath between the model and the action it would trigger, and holds the output inside a policy declared in advance.

Prototype gating a live model · planned mid-2027First customer deployments · planned 2028Designed, not built

How it works

Four blocks, in a fixed order no software can remove.

01

Automaton engine

Holds the parsing state for each request in dedicated logic, against a policy compiled in advance.

02

Validity mask

Computes which next tokens or commands the policy accepts, at every step.

03

Default-blocking gate

Biased to block. A non-accepted output cannot commit.

04

Attestation-gated release

Output is released only when a root of trust attests the loaded policy is unmodified. A one-byte change fails.

The emission interlock

Disabled

Nothing is emitted until the device is attested.

Attest

The root of trust measures the loaded policy.

Enabled

Accepted output is released, with a token for each emission.

Blocked

A violating output is held, or returned to the model to re-propose within a bound.

Three configurations, one appliance

Size the configuration to the adversary.

The rules configuration needs no experiment. The other two each have a gate of their own, declared in advance.

ConfigurationWhat it addsGate before it shipsPlanned
RulesGrammar and command enforcement in a dedicated datapath. No software at any privilege level can bypass it.None: decidable by construction. The prototype is to be formally verified and bypass-tested against pre-defined attacks.Prototype mid-2027 · deployments 2028
DistributionA certified envelope with a stated miss rate, per constraint.A certification run per constraint.Late 2027
MeaningThe semantic check on the same interlock.A pre-registered experiment of about 10 weeks. If it fails, rules and distribution are unaffected.First half 2028

Where it fits

For when a software bypass would move money, equipment or secrets.

Regulated finance

Governed inference on-premises

Run any model, from any origin, on your own premises, with every consequential output checked in hardware.

Critical infrastructure

An AI firewall for SCADA and ICS

For operators where a software bypass would move equipment, and safety and security standards already apply to every other control.

Confidential material

A gate on what reaches frontier models

The meaning configuration, if the experiment passes.

Sovereign and defence buyers span all three.

Two ways to use it

Installed, or hosted.

Installed

A sealed appliance on your premises

General counsel mandates the evidence; the technology team runs the box, much as it runs a hardware security module.

Hosted

The same token, without the hardware

Call an appliance run for you through the open Universal Governance Protocol, and verify each token without trusting the host.

The protocol →

The honest boundary

What the appliance proves, and what it does not.

Form, not meaning. Output conforms to the attested policy. Conformance does not by itself guarantee safety, accuracy or appropriateness.

Every path, or no claim. Non-bypassable only where every consequential path passes the appliance. That is proven per deployment.

Trust relocated, not removed. It moves onto the silicon and its attestation chain, which can be inspected.

Built on the Deterministic Governance Architecture, patent pending.