Certifiable Conformance Pack · Triodian

Evidence tier · in build

The difference between asserting conformance and demonstrating it.

The Certifiable Conformance Pack combines Structured Output Assurance and Bounded Command Governance with identical accept or reject decisions every time, and writes a tamper-evident conformance record for each output, bound to the policy version that governed it.

In build · December 2026Conventional engineering

What it does

Evidence written by the system, not about it afterwards.

Repeatable verdicts

Every accept or reject decision is identical on re-execution. Re-run the input and you get the same verdict, every time. Repeatable is not the same as correct: the record shows the declared policy was applied, not that the policy was right.

A record per output

Each output carries a signed record naming the policy version, the verdict and the time, written to a hash-linked ledger a third party can check without trusting the operator.

Specimen conformance record · illustrative only

policy_version  [email protected]
verdict         ACCEPT
timestamp       2026-07-23T04:18:07Z
substrate       software, tamper-evident
signature       3f9a1c…e7b204 · ed25519

The record names what governed, what was decided and when, bound so that any later change is detectable.

How it works

Decide, seal, record.

Check

Accept or reject

Structured Output Assurance or Bounded Command applies the declared grammar.

→

Seal

Bind to the policy

The verdict is signed with the exact policy version it was made under.

→

Record

Hash-linked ledger

Each record links to the last, so a removed or altered record is detectable.

Who it is for

Where the question is "show me", not "tell me".

Regulated entities

A bank, insurer or fund that must show a supervisor, an auditor or its board that a control over AI operated, output by output, not only that a policy exists.

Operators

A supplier asked by a customer, a funder or an insurer to evidence how its AI-driven outputs are controlled, in a form their reviewer can check for themselves.

What it does not do

Three limits, stated plainly.

It proves conformance to the grammar

Not that the grammar captures every obligation. Writing the policy is a separate, governed step.

Tamper-evident, not tamper-proof

Strong where the requirement is an auditable record. Where a privileged insider must be structurally excluded, the rung is the hardware appliance.

Single outputs, not the set

Drift across many conformant outputs is the job of the Aggregate Drift Service.

Evidence rung it fills

Attestation

That an output met a declared policy.

This is the product that fills the attestation rung on the evidence ladder. Its ledger also supports the audit rung: what was checked, against which policy version.

Get in touch

Talk to us before you build the control.

Thirty minutes on where your AI acts, what evidence it would need to leave, and whether this is the right rung.

Book a 30-minute conversation →