Agent Receipt vs. Audit Log | Reelier
Evidence state: explained against released reelier@0.32.0 on 2026-08-12.
A Reelier 0.32.0 receipt is an execution-specific outcome record: it identifies the skill, retains ordered step results, totals, and failure text when present, and can bind those outcomes to separately retained skill bytes through optional skillContentSha256. The comparison is about that receipt structure, not a claim that all audit logs share one shape.
Evidence note
The released runner contract defines the receipt fields. This page makes no universal claim about the many products and formats called audit logs.
The receipt boundary
The record describes one Reelier execution. A supplied skillContentSha256 identifies separately retained bytes; when the field is absent, the receipt establishes no content binding.
What the record retains
The receipt retains ordered step number, title, outcome, totals, and failure text when present. It does not reproduce the full skill source, action tool or arguments, explicit intent, or every successful assertion expression.
Why the distinction is bounded
An audit log may contain more, less, or different data depending on the system. The useful comparison is therefore field-by-field against a particular log contract, not a categorical claim that a receipt replaces audit logging.
Non-claims
This does not prove that an action was safe or semantically correct.
This does not prove that every write was observed or receipted.
Falsifier
If the released receipt exposes neither execution outcomes nor the optional content binding described here, this structural distinction collapses.
Citation-friendly definition
A Reelier 0.32.0 receipt records outcomes for one execution and can optionally bind them to separately retained skill bytes; that field structure is the bounded distinction made here.