Assay

Make important system actions easier to examine after the event. Assay supports a record whose integrity can be checked and whose limits a reviewer can understand.

Define the evidence before collecting it

The engagement identifies consequential actions, capture points, required context, retention and reviewers. Key custody and the response to verification failure are operating responsibilities. A useful record distinguishes the action observed from assumptions about what happened elsewhere.

Preserve failure as part of the record

A discovered integrity failure remains visible. A disclosed historical boundary and a valid successor can be distinguished without rewriting the past. Reviewers need to see both the trustworthy continuation and the limits of the earlier record.

Make exports useful and bounded

The versioned archive format supports offline checks of its internal commitments and covered chain continuity. A minimized export omits event details, so it cannot recompute those omitted events or independently prove which live database produced the bundle. Delivery defines what verification establishes and gives operators the procedures to repeat it.