What does the proof reveal?

A governed call is inspected, verified, settled, and signed. Repeated work can become more efficient or deterministic as the record learns the workload. On the reference workload, 17% of calls reached zero model spend.

Inspect the signed record.

Q: What does the receipt hash represent?

Each receipt hash, for example 0x9f27e4, represents a tamper-evident signed record of the call: the intelligence used, the cost, the policy decision, and the verification result. Receipts are hash-chained so any alteration to a historical record is detectable.

Run one call. Toggle governance. Inspect the evidence that survives.

Ungoverned enterprise default

$47.00 / agent-day

Cost only. No verified outcome or signed record.

Governed through tiers

$6.10 / agent-day

Inspected. Verified. Settled. Signed.

One call. Two outcomes. waiting for a call

with tierssigned record

01requesttask enters

02runtime inspectionpolicy + session

03price discoveryquality bar

04verifyoutcome checked

05signed receiptevidence closes

without tiersno durable record

01requesttask enters

02enterprise defaultuninspected

03outputno verification

04no receiptpostmortem only

Run a call to watch the record close around it.governance on

Static reference proof

JavaScript is unavailable, so the controls above cannot run. These representative outcomes and receipt fields preserve the evidence needed for inspection.

Governed callVerified, settled at $0.0041, and signed.

Security failureBlocked before intelligence, settled at $0.0000, and signed.

Governance offList-price output with no verification and no signed receipt.

task: extract the governing-law clauses from the attached contract
policy: cleared
intelligence: frontier intelligence · model-h45 · quality bar met
cost: $0.0041
inspection: clean · session inspected
verification: pass · 0.97 confidence
previous hash: 9c41...e2af
receipt hash: 0x9f27e4
signature: ed25519 · 0x9f27e4 · signed
chain status: verified · previous hash linked

Download the static receipt JSON

WITHOUT tiers

$0.0000

WITH tiers

$0.0000

SAVED

$0.0000

you@prod ~ tiers session

GOVERNED

Signed receiptwaiting for a call

Nothing signed yet. Run a governed call above to populate the receipt. The displayed artifact is simulated reference-workload evidence.

Simulated session using verified reference-workload figures. The receipt schema and interaction are representative; results vary by workload.

For fourteen days, the same workload ran in parallel through a governed path and an ungoverned enterprise default. Both streams were recorded and cryptographically signed. Results vary by workload.

What the toggle reveals

What becomes more efficient over time?

Repeated work can become more efficient, specialized, or deterministic as the record learns the workload. Frontier intelligence remains available when it is the right tool.

When can work become deterministic?

When a repeated pattern can be verified against a stable quality bar, it can move toward deterministic execution. On the reference workload, 17% of calls reached zero model spend.

Repeated computation

Repeated computation: cached.

Unverified outputs

Unverified outputs: caught before propagation.

How does the injection attempt work?

The demo fetches a vendor documentation page containing an embedded prompt injection. With governance on, tiers detects and blocks the payload before it reaches an intelligence source, records the block in a signed receipt, and charges $0.0000. With governance off, the instruction reaches the source.

What does the receipt hash represent?

Each receipt hash, for example 0x9f27e4, represents a tamper-evident signed record of the call: the intelligence used, the cost, the policy decision, and the verification result. Receipts are hash-chained so any alteration to a historical record is detectable.

The system learns from every governed call. The 87% is a point on the learning curve, not the end of it. The value compounds because the record gets more specific to your work over time.

Talk to the founders