Hive research paper

A Refused Write Is Evidence

Tamper attempt receipts for append only agent records

Published
September 3, 2026
Scope
3 typed receipt profiles
Format
HTML, Markdown, JSON index
Quick answer. A tamper receipt should prove a narrow event: a mutation was requested, the protected root stayed unchanged, and the refusal was recorded after the request. It should not turn that event into an accusation.

The problem

Agent systems produce transcripts, tool calls, scorer outputs, policy decisions, and checkpoints. An ordinary audit log can show the final record. It often cannot show that someone tried to change that record and failed.

The missing object is a signed refusal record. It binds a target receipt, a requester commitment, the requested operation, the refusal reason, the prior root, the observed root, and the relevant times. The service derives the outcome from those fields.

Primitive map

ReceiptBound inputsDerived relationClaim boundary
tamper.attemptTarget receipt, attempt type, requester commitment, prior and observed roots, request and observation timesThe roots match and the observation follows the requestRequester identity, intent, or log completeness
transparency.checkpointLog identity, tree size, root, and checkpoint timeA specific append only state existed at a stated sizeThat every relevant event entered the log
sequence.attestationOrdered event commitments and sequence positionThe supplied sequence is internally orderedThe truth of each event payload

Verifier gates

The verifier rebuilds derived values. It does not trust a caller supplied outcome, count, root, total, or relation.

  • SCHEMA
  • ISSUER_KEY_MATCH
  • ENVELOPE_SIGNATURE
  • TARGET_RECEIPT
  • ROOT_UNCHANGED
  • OBSERVATION_ORDER
  • OUTCOME_DERIVATION
  • NON_ACCUSATORY

Failure cases

Delete

A requested deletion is committed before the protected root is read again.

Overwrite

The prior and observed roots show whether the protected state changed.

Reorder

Sequence commitments expose a changed order when the verifier recomputes them.

Backdate

Request and observation relations fail when the claimed order is impossible.

Suppress

A witnessed refusal remains independently verifiable even if the application omits it later.

Claim boundary

  • It does not identify the requester.
  • It does not infer malicious intent.
  • It does not prove that the log was complete before the first independent witness.
  • It does not prove the truth of facts inside the protected receipt.

Standards context

These sources describe related transparency, authorization, or evidence patterns. They do not endorse Hive or establish that a Hive receipt was present in any third party system.

Related research