Documentation

Trust · Guide 05

Receipts, ledger and verification

Three trust artifacts answer different questions: what was decided, who accessed what, and whether the proof is intact.

8 min read

Pre-release documentation. This guide describes the current product design and evaluation build. Packaging, availability and commercial terms may change before release.

01

Decision receipts

A receipt is a signed portable record of one decision. It binds the rulebook version, artifact hash, supplied facts, as-of time, answer tier, outcome, applied rules, reasoning chain and evidence.

  • An authorization signature is created before a gated action executes
  • A result signature covers the completed receipt
  • Facts are bound by salted hashes rather than embedded in clear text
  • Receipts can be chain-linked so removal is detectable
02

The access ledger

The ledger records every access, including searches and reads that did not produce a decision. It answers who asked what and what knowledge left the system.

  • Decision, retrieval, document read, MCP, gateway, export, verification and administrative events
  • Sensitive fact values are hashed
  • Disclosure records identify the exact evidence returned
  • Enforcement-grade writes become durable before the response
03

Independent verification

The verifier checks the receipt schema, signatures, chain links and commitments without asking a model and without needing to trust the service that made the decision.

avy verify ./decision-receipt.json

Executive briefing

Apply the architecture to one consequential workflow.

Bring one consequential agent workflow. We will map the governing policies and regulations, runtime gate, human authority and auditable evidence path with your team.

Request a briefing