If a firm is going to rely on machine-assisted research, the file should show more than the final prose. A verification audit trail answers: what citation was checked, which of the five checks ran, what public source was used, and whether the result was pass, fail, or needs review.

Minimum contents we treat as the trail on /verify:

• The raw pasted string and the normalized reporter cite, when one exists.
• Existence against a named public source (for the Carpenter example: Cornell LII, CourtListener, Oyez).
• Citation format: whether volume, reporter, page, and year resolve.
• Holding support: whether the surrounding proposition is consistent with the recorded holding, or still needs a person.
• Verification path: what was checked, against what, with a URL when one is available.
• Human review flag: always present, because OWL does not create an attorney-client relationship and does not file for you.
• Explicit error when the cite is not found, is ambiguous, or the source is unavailable.

A firm plan that includes an audit log is listed on /pricing. Do not confuse a chat transcript with a verification trail. One is conversation. The other is the record you can hand a reviewer.