---
title: "Euthyne glossary"
description: "Plain definitions of the terms behind verifiable records of AI agent actions: signed receipts, mandates, transparency logs, checkpoints and more."
canonical: "https://euthyne.com/glossary"
updated: "2026-10-18"
---

# Glossary

Plain definitions of the terms behind verifiable records of AI agent actions: signed receipts, mandates, transparency logs, checkpoints and more.

## Signed receipt

A signed receipt is a tamper-evident record of one action an AI agent took, signed with a key on the machine where the action happened, so anyone can later check that it was not changed. In Euthyne, each Claude Code hook event produces one receipt that names the organization, the person, the device, the harness, the model, the tool and the outcome. Prompts, tool inputs and outputs appear only as salted hashes. A receipt shows which key signed which record and when it was logged, not that the action was correct or that every action was captured.

## Mandate

A mandate is a signed record of what an agent was allowed to do at a given moment. In Euthyne, the session mandate is captured from Claude Code's own permission settings at the first hook of a session: the permission mode, the allow, ask and deny rules, the MCP servers, the working directories and the sandbox settings. It is a W3C Verifiable Credential 2.0, versioned on every change and logged before the receipts that cite it. Each receipt records whether its action was in the mandate, outside it, or not determined, and nothing is ever blocked.

## Transparency log

A transparency log is an append-only, publicly readable list of entries built on a Merkle tree, where anyone who has seen an earlier state can detect an entry being removed or changed. Its state is published as signed checkpoints, and inclusion proofs show that a given entry is in it. Euthyne appends the digest of each receipt and mandate to its log, which holds no content and no organization ID and is served in the C2SP tlog-tiles format.

## Checkpoint

A checkpoint is a signed statement of a transparency log's state: the log's origin, its tree size and the Merkle root hash at that size. Holding a checkpoint lets you check that an entry is in the log at that size, and comparing checkpoints reveals a log that was rewritten or forked. Euthyne's checkpoints follow the C2SP tlog-checkpoint format, are signed by a log key built into the CLI, and are periodically anchored on chain.

## Inclusion proof

An inclusion proof is the short list of Merkle tree hashes needed to recompute a log's root hash from one entry. If the recomputed root matches a signed checkpoint, the entry was in the log when that checkpoint was signed. Euthyne saves the inclusion proof of each receipt in a bundle on your machine, so euthyne verify can check it without the network.

## Anchoring on chain

Anchoring on chain means committing the hash of some data to a public blockchain, so anyone can later show that the data existed before a given block, without trusting whoever holds it. Euthyne anchors checkpoints of its transparency log on chain, which gives every receipt under an anchored checkpoint a time bound that does not depend on Euthyne. Until the anchor lands, the receipt reads as timestamp pending. The anchor bounds when a receipt existed, not when the action happened.

## Agent identity

Agent identity is the set of verifiable facts that say which agent acted and on whose behalf. In Euthyne today, an agent is a harness running on one enrolled device for one person: each receipt names the harness, the model, the session and any subagent, and is signed by a session key that the device key certified. Euthyne binds the device key to a person and an organization at enrolment, so the identity in a receipt rests on Euthyne while the integrity of the log does not.

## Hook

A hook is a command that a program runs automatically at a defined point in its lifecycle, with details of the event passed to it. Claude Code runs hooks on events such as SessionStart, PostToolUse and SessionEnd, and passes each event as JSON on standard input. Euthyne registers euthyne hook claude-code on these events to sign one receipt per event. Recording never blocks. On PreToolUse, the hook can deny a tool call only when the org enforces a signed policy.
