White papers

Twenty six white papers on typed receipt instruments

These are the working papers for the Hive receipt canon. The first twenty one cover deployed receipt instruments. Five new papers explain the specialized receipt engines, their verifier gates, their adverse outcomes, and the point where each claim stops.

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 stateThe original twenty one papers describe deployed receipt instruments. The five specialized primitive papers describe the current reference implementation and do not claim public deployment.

Specialized primitives

family: specialized primitives, 5 papers

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.

Data handling. Client-side hashes and server-side text processing have different boundaries. Logging, storage and retention are endpoint-specific. See Privacy.