The Verdict That Files Itself

Description and use

Adding persistent receipt files to contract checks eliminates audit gaps, ensuring console output and file evidence always match.

Problem

Audit findings lacked verifiable evidence because contract checks produced console output without persistent receipts, making it impossible to confirm results after the terminal closed.

Outcome

Implemented persistent receipts for contract checks, eliminating audit gaps and ensuring verifiable evidence of each check outcome.

Workflow

• Run contract check tool
• Tool prints verdict to console
• Tool writes receipt file in radars directory with microsecond timestamp, exit code, and verbatim output
• If receipt missing, tool exits with code 2 and logs warning
• Audit journal records receipt name alongside verdict

Evidence

Every run of the check now writes its own receipt alongside its report: a file in the radars directory, stamped to the microsecond, containing the exit code and the exact text it printed — verbatim from the same buffer

Source