White papers

Twenty one white papers, one per typed receipt instrument

These are the working papers for twenty one receipt instruments. Each one was written from the running implementation rather than from a design document. The gate lists come from the verification code, the field tables come from the JSON Schema that the service actually validates against, the adversarial cases come from the test files, and where a benchmark row exists the latency and artifact size figures come from that measured file.

Every paper follows the same shape: what the instrument binds, what is deliberately left out of the signed body, the gates in the order they run, the boundary text that sits inside the signed bytes, the adversarial cases, the measured cost, how to run it, and where it sits in the canon. Each one ends with a link to its canon entry, its JSON Schema and its verify route, so you can check the paper against the artifact.

Verification is open on the deployed types and needs no credentials. Patent pending.

An honest note on stateAll 21 of them, including the six in the network authority family, are production_deployed. Their papers say so plainly and each carries measured mint and verify latency plus artifact size, because the benchmark file now holds a row for every one of them.

Authority

family: authority, 3 papers

Bonded performance

family: bpa, 2 papers

Compliance evidence

family: compliance-evidence, 1 paper

Evaluation

family: evaluation, 1 paper

Incident evidence

family: incident-evidence, 1 paper

Network authority

family: network-authority, 7 papers

Provenance

family: provenance, 1 paper

Risk evidence

family: risk-evidence, 3 papers

Settlement evidence

family: settlement-evidence, 2 papers

Each instrument also has a canon entry with its schema, its verify route and its implementation state. Start at the Hive canon for the full registry, or go to verify a receipt to check one you already hold.

Private by design. Hive does not store your prompts. Every request is already receipted by a one-way SHA-256 fingerprint, not the words. Proof, not surveillance.