Agent Trip — decision layer / receipt layer

The agent owns the trip.

Every agent run separates into two things. A decision layer that chooses the route, the model, the provider, the reroute. And a receipt layer that records each of those choices as a signed artifact. Deliver the receipts at the end and you get an audit. Stream them during the call to an independent dashboard and outside review can correct, reroute, or pause the trip while it is still moving.

Providers own roads. The agent owns the trip. Hive receipts the route.
— The two layers

Route is a decision. Proof is a receipt. Keep them separate.

Decision layer

Where the agent chooses

Objective, plan, model, provider, reroute. The control plane over inference. When one provider is cheaper, faster, or a better fit for a task class, the agent can reroute — the same way a driver changes roads without changing the destination.

Receipt layer

Where the choice is proven

Each decision is canonicalized, hashed, and signed with ML-DSA-65. Receipts chain by prior-hash into one record of the whole trip. Stream them live and an independent observer holds the same evidence the agent does, at the same moment.

— Live trip

Run a trip. Watch the route sign itself.

One button runs a short trip of seven route decisions. Each event streams in, then mints a receipt: a real ML-DSA-65 (NIST FIPS 204) signature over the canonical decision body, chained to the one before it, and verified in your browser against a keypair minted in memory for this run. Nothing is stored. Nothing is sent to a server.

Trip dashboard
Idle. Press Run a trip to begin.

Trip receipt chain

0
Receipts
0
Verified in browser
ML-DSA-65
Signature scheme
0
Total verify (ms)
trip_id —
public_key —
chain_root —
Signing primitive: the same audited @noble/post-quantum ML-DSA-65 build this site uses on /typed-signer/. Keypair, signatures, and verification all run in your browser.
— Honesty

What this proves. What it does not.

What this proves

  • Real ML-DSA-65 signatures over a sequence of route decisions, one receipt per decision.
  • Each receipt chains to the previous by prior-hash, so the order cannot be edited after the fact.
  • Every signature is verified in your browser against the public key minted for this run.
  • The decision layer and the receipt layer are separated, and a live external correction is folded into the trip mid-flight.

What it does not prove

  • That inference actually executed on Together or LFM. The reroute is a routing-control-plane demonstration; the cost and latency figures are modeled, not measured.
  • Production multi-provider execution, or per-token streaming from a live model.
  • HSM-backed keys, transparency-log anchoring, or on-chain settlement. That is the production layer, not this in-browser demo.
  • Any dual Ed25519 co-signature. Production Hive receipts add the classical half; this demo signs the post-quantum half only.

The control-plane idea is the point: an agent that reroutes inference between providers when one is cheaper, faster, or a better fit — and signs a receipt for the decision — is the control plane over inference. This page renders that route and proves the decisions. It does not claim the underlying provider calls ran here.

Typed Signer
The same ML-DSA-65 primitive, signing typed fragments. Verify in your browser.
The Hive Thesis
Agents route by inference, not configuration. Why the decision layer is the adoption layer.
Inference Bus
Route any model through Hive. Every call returns a SHOD-anchored receipt.
ML-DSA-65 is NIST FIPS 204. Signatures on this page are produced and verified entirely client-side using the audited pure-JavaScript @noble/post-quantum build; if that module cannot load, the page falls back to a SHA-256 hash chain and labels every receipt accordingly, so it never presents an unverified signature as verified. USPTO patent portfolio pending. Contact [email protected].