Platform · rules tier
The Rules Tier is the first layer of the Triodian platform. An agent's commands, the types and ranges of their arguments, and the format of its output are declared up front. Each call is accepted or rejected against that declaration, the same way on every replay, and each verdict is written to a hash-linked ledger that a third party can verify without trusting Triodian or the operator.
What it does
Acceptance is binary. A call is in the declared set or it is not; its arguments are in range or they are not; its output matches the declared format or it does not. There is no score and no threshold, so two people running the same inputs get the same verdict, bit for bit.
An agent may use only the commands it was given: read a policy, look up a claim, issue a refund. A call outside the set is rejected before anything runs.
Each argument has a declared type and bounds. A refund command declared up to $5,000 rejects $48,000, and the ledger records why.
Where the output feeds another system, it must match the declared format. A malformed reply is never passed on.
How it works
Nothing is learned and nothing is judged. The policy is a declaration, the check is a comparison against it, and the record is a signature over the result.
The command set, argument types and ranges, and output schema are written down and given a policy version. A change is a new version, never a silent edit.
Every output and tool call is compared with the declaration after the model produces it. Windowed aggregates count what passed and failed over time.
Each verdict becomes a compliance token bound to the policy version, appended to a hash-linked ledger. A standalone verifier lets a third party check the chain: an altered, missing or reordered entry is detected every time.
What the tier contains
The ledger, token and verifier are built first. The products sign into it, and so does everything the platform adds later.
Output must conform to a declared grammar or schema.
An agent may use only commands in a declared set, with typed arguments.
Both, with verdicts that replay identically and a signed record bound to the policy version.
A provider's disclosures, attestations and change notices, signed by the provider, co-signed by the customer and written to the same ledger. A change notice is linked to the declaration it changes.
What it does not do
A call can be in the set, in range and in format, and still be the wrong thing to do. Governing meaning is the semantic check in Attested Semantic Compare.
Many conformant outputs can still drift together. That is what the Aggregate Drift Service watches.
Where an insider or a capable adversary is in scope, the rung is the hardware appliance.
Evidence rung it fills
That an output met a declared policy.
The Rules Tier supplies both halves: the accept or reject decision, and the tamper-evident record per output that an auditor or supervisor can rely on. Its ledger is the evidence layer every later Triodian product signs into.
Related
The next rung
Adds a meaning check beside the rules check, for actions whose rightness is not a matter of form.
The set, not the call
Many calls can each pass and still drift together. The drift service watches the set.
How we grade claims
What is demonstrated, built, designed or still a hypothesis.
Status legend →Get in touch
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 →