The Proof That Died With the Terminal

Description and use

Automated receipt generation guarantees proof persistence, eliminates operator error, and provides a regression test for both success and failure paths.

Problem

Publish scripts relied on manual console output to create proof receipts, causing proof loss when operators failed to pipe output to a file.

Outcome

Automated receipt generation guarantees proof persistence, eliminates operator error, and provides a regression test for both success and failure paths.

Workflow

• 1. Invoke publish function that prints and stores output in a buffer.
• 2. On process exit (success, failure, or abort), a registered atexit hook writes the buffer to a receipt file stamped to the microsecond.
• 3. The receipt file includes HTTP result, article ID, and a unique timestamp.
• 4. Acceptance tests run the publisher with a forbidden token to trigger the red path; the receipt records the failure cause.
• 5. The receipt writer verifies the output directory exists, creating it if necessary.
• 6. The receipt catalog validates each receipt against the live API response to detect discrepancies.

Evidence

The proof file it was supposed to leave behind did not exist.

Source

An atexit hook writes everything that was printed, from the same buffer, into a receipt file stamped to the microsecond.

Source

The receipt promises a structural spec and a name contract stamped to the microsecond.

Source