A flight recorder
proves what crashed.
A clearance
stops the takeoff.

Imprimatur is the control. Here is where it sits among the others.

Pick what you actually run: text, voice, video, documents, or payments. The matrix shows which primitives operate on it and what each one proves. Imprimatur is the only one that binds a clearance before the call. The rest prove what happened after.

A clearance issues only when
all four are satisfied.

Each pre-condition is a named, signed leaf. The four are folded into a single Merkle commitment, the precond_root, using the same construction as Hive's batch receipts. Two calls with an identical satisfied set share a root and laterate off one clearance.

It proves your checks ran.
It does not certify the law.

This is the line that keeps the primitive defensible. The enterprise defines the policy. Hive enforces it and signs that the enforcement ran and passed. Hive is not a truth oracle for legality.

A hard gate, or a passport
that travels with the call.

# present a clearance + the call about to run
{ "clearance": { ... }, "sig_b64u": "…", "call": { "model": "…" } }
# -> { "decision": "ALLOW" }  or  { "decision": "REFUSE", "reason": … }

# fetch + passport-verify a clearance
# -> { "verification": { "valid": true, "sig_ok": true, "root_ok": true } }

A gate that only says no is a filter.
This one is a warden.

Every decision carries a consequence, and the consequence differs by what failed and how often. A filter throws away the calls it blocks. The warden keeps them, counts them, and rings the bell when the pattern emerges. The same control that blocks bad calls also earns trust, repairs the fixable, and raises an alarm on the threatening.

The line that sells to a CISO: “I don't just stop the bad calls. I tell you which of your agents keep trying to make them.”

Capture law, encoded as policy.
The check signed, never the route.

Audio and video are among the most legally protected data classes there are: recording consent, biometric, retention, all varying by state and country. Every vendor running AI on recordings carries this exposure, and none can prove compliance today. Jurisdictional Clearance turns the capture law of where a recording came from into a counsel-authored policy the gate checks and signs. So a vendor can prove every inference was cleared against the applicable rule, while Hive never decides what the rule is.

Hive is a provenance provider, never a rule-maker. Counsel encodes the law into versioned policy. Hive checks the inference against it and signs the result: cleared_against_policy_vN_for_jurisdiction_X. Never legal, never admissible. That boundary is the whole product's safety.

In every row the left column is counsel's work product; the right is Hive's signed fact about the process. Hive never fills the left column. The clearance binds which policy version was in force, so the record is exact.

The receipts are for the platform.
The gate is for the regulated buyer.

Every other primitive on the Stack is sold to the platform serving inference. Imprimatur is sold to the regulated enterprise that consumes inference and has to prove control before the model fires, in regimes where an after-the-fact log isn't enough.

A clearance is worth more
than the receipt that follows it.

Issuing a clearance runs four pre-condition checks and signs a control. That's categorically more than emitting a receipt, and it's priced accordingly: roughly 7× a SiGR signature. Checking a clearance is free for anyone, offline, with no secret. Reuse via precond_root is free. An identical satisfied set laterates off the existing clearance. The meter is the wedge. For a regulated buyer the annual license is the close.

A clearance is not a receipt. Per-attestation signing is metered separately at $0.0002 on the canonical pricing page; the rate above prices the gated control that issues it.

Graduated by band, like cloud egress. Reuse via precond_root never bills twice. Hardened add-ons, PQ clearance signatures and ledger anchoring of the clearance log, carry the same volume discount on a higher base. Sovereign floor negotiable.

Pre-execution control is a new rail.
The first to lay it owns the toll.

A regulated enterprise running agents at scale issues a clearance on every gated call. At control prices, the rail compounds fast. And once one regulated buyer requires it in an RFP, the requirement propagates to its peers within a cycle.

Pilot the gate now.
License it when it's load-bearing.

Two paths, one rail. Run a scoped pilot against your own policy, or book a license when the gate becomes the control your auditors and customers depend on.