Evidence package

Deliver an output together with the basis for checking it.

Result

The deliverable travels with enough evidence for an independent reader to trace its origin, inspect critical transformations, repeat key checks, and understand the acceptance decision without access to the chat.

evidence-package/
├── README.md
├── task-brief.md
├── sources/
├── transformations.md
├── checks.md
├── limitations.md
└── acceptance.md

Use links or stable identifiers instead of copying restricted source material into the package.

Actions

1. Preserve the accepted task brief and identify each input by path, source, date, version, or checksum as appropriate.
2. List material transformations in order, including the tool and version when it affects reproducibility.
3. Attach permitted sources or stable identifiers and exact locations supporting critical claims.
4. Record each acceptance criterion, the check performed, evidence location, result, and reviewer.
5. Separate known limitations, missing data, rejected output, unresolved questions, and manual expert decisions.
6. Remove secrets, raw private consultation notes, and unnecessary personal data; verify the intended recipient.
7. Give the package a date, version, owner, status, and link to the accepted output.

Check

Open the package in a clean session with no chat history. An independent reader can identify the task, input versions, final output, source support, transformations, failed and passed checks, limitations, reviewer, and acceptance decision. Every referenced file or link resolves for that reader.

If it fails

If a source, transformation, or decision cannot be reconstructed, keep the output in draft status. Re-run only the opaque step from the last trusted input and retain both the failed and corrected evidence. If access cannot be shared, record the limitation and the authorised reviewer who performed the check.

Next: Verify the result.