Hive Civilization Knowledge Base
Receipts · Proof-state · ProvenanceReference library
← back to thehiveryiq.com
Reference library · Explainers · Field notes

The Hive Knowledge Base

A reference library for provable AI: cryptographic receipts, proof-state, and independent provenance for AI agents, machines, and payments — with the public record of our regulatory filings alongside it.

These pages explain the primitives Hive builds on and how they fit together. The foundations cover why an independent receipt is different from an internal log, what proof-state means, and how a receipt layer can witness a workflow without slowing it down. From there, the library follows the receipt across the places it applies — AI agents, machines and robots, and payments — and into the regulated settings where an independently verifiable record is the point.

Everything here is written to stand on its own and to be useful to anyone reading it, including competitors and partners. If you would like to cite, fork, or republish, please do — attribution is appreciated but not required.

Foundations
Hub Start here
AI Receipts: the proof layer for agents, model calls, and x402 payments
One page that maps every thread — AI receipts, agent receipts, signed model calls, x402 AI payments, MCP and API agent receipts, and the AI audit trail — to the live route that proves it.
AI receipts Agent provenance AI audit trail
Open the hub →
Canonical Foundations
Logs Are Claims. Receipts Are Proof.
Internal logs tell a story from inside the system. Cryptographic receipts create independently verifiable proof of what happened, what was observed, and where the proof boundary ends — the difference that matters for agents, machines, payments, and regulated workflows.
Logs vs receipts Independent verification Proof boundary
Read post →
Canonical Foundations
Proof-State: The Missing Primitive for AI Systems
AI systems need a machine-readable state for what has been proven, what was only claimed, and what actions remain permitted. Proof-state defines the evidence tiers — self-attested, relay-observed, chain-verified — and why honesty about the weakest boundary is the feature.
Proof-state Evidence tiers R3Pv
Read post →
Explainer Inference · Proof
What Cryptographic AI Receipts Are — and Why Inference Needs Proof
A plain explanation of the primitive: signed, independently verifiable proof that an AI inference happened the way it is claimed. Why a database row is not proof, and how anyone can verify a receipt offline with ML-DSA-65.
Cryptographic AI receipts AI inference receipts Signed inference
Read post →
Architecture How it works
AFiR Runs Beside the Control Loop, Not Inside It
Won't signing everything slow the system down? AFiR runs as a sidecar witness beside agents, robots, and payment rails — signing event boundaries asynchronously and measuring receipt latency separately from control-loop or rail latency.
AFiR sidecar Asynchronous receipts Receipt latency
Read post →
Agent receipts
Explainer Agents · Actions
AI Agent Receipts: Verifiable Proof of What an Agent Actually Did
Route decisions, tool calls, model choices, and memory turned into a signed receipt chain — verifiable proof of what an autonomous agent did, not a reconstructed story from logs the operator controls.
AI agent receipts Verifiable agent actions Receipt chain
Read post →
Machine receipts
Field note Physical AI · Robot data
Robot Data Factories Need Speed. They Also Need Receipts.
Physical AI data factories cannot choose between high-throughput teleoperation and long-term auditability. AFiR runs as a sidecar witness to the collection loop — receipting the moments that matter asynchronously so robot training data moves fast while staying independently provable.
Robot training data provenance Teleoperation data Physical AI auditability
Read post →
Payment receipts
Explainer Stablecoins · Payment proof
Stablecoin Transactions Need Receipts, Not Just Logs
A stablecoin transfer settles in seconds, but the context around it — intent, actor, policy, evidence, settlement state — lives in a log the payer controls. Receipt Relay signs that context into an independently verifiable record, with honest evidence tiers and offline verification.
Stablecoin payment receipts Agentic payments Receipt Relay
Read post →
Explainer x402 · Agentic commerce
x402 Agent Payments: Receipts for Agentic Commerce
When agents pay for AI actions on their own, the payment has to settle and the economic event has to be provable. x402 handles settlement on Base; Hive receipts make the action verifiable.
x402 agent payments Agentic commerce USDC on Base
Read post →
Data & regulation
Explainer Human data · Provenance
Human-Origin Attestation: Third-Party Proof of Expert-Data Provenance
Buyer-verifiable proof that data was human-conditioned — expert-data provenance you can check without trusting the platform's own claim. Why AI data provenance needs independent third-party proof.
Human-origin attestation Expert-data provenance AI data provenance
Read post →
Explainer Finance · Health · Legal · Gov
AI Assurance for Regulated Workflows: Finance, Healthcare, Legal, and Government
In regulated settings, "the model did the right thing" is not a defense — a verifiable record is. How signed inference and agent receipts map to record-keeping, oversight, and audit obligations across domains.
AI assurance Regulated workflows Third-party proof
Read post →
Comment Letter FinCEN · Filed May 19, 2026
Re: AML & Sanctions Compliance Framework for PPSIs under the GENIUS Act
Hive Civilization's public comment on the Treasury / FinCEN / OFAC Notice of Proposed Rulemaking implementing the AML and sanctions provisions of the GENIUS Act for permitted payment stablecoin issuers. Comments close June 9, 2026.
FinCEN OFAC GENIUS Act PPSI Travel Rule
Read letter →
Position Paper EU AI Office · Filed May 19, 2026
Re: Practical Implementation of Articles 12, 13, and 14 of the EU AI Act for Agentic Commerce
A position letter to the European AI Office, the EU AI Board, and the National Competent Authorities proposing the signed transaction receipt as a candidate reference implementation for the record-keeping, transparency, and human-oversight obligations applicable to high-risk agentic-commerce systems.
EU AI Act Article 12 Article 13 Article 14 Receipt Engine
Read letter →

Every post here connects back to a live primitive you can inspect: Receipt Relay for signing events at explicit evidence tiers, the Hive Ledger for searchable, offline-verifiable records, and the AI Receipts hub as the map that ties every thread to the route that proves it.