Setting the file. One moment.
Subchapter 68.1
references/receipt-contract.mdMarkdown2 KBView on GitHub
Use JSON only when the user, CI, or another tool needs a structured artifact. Keep the normal final answer human-readable.
version: integer 2 for new receipts. Version 1 remains accepted for compatibility.status: verified, partial, or blocked.evidenceSource: executed-now, supplied, or mixed (required in version 2).problem: concise defect and intended behavior.baseline: object with command, result, and evidence.rootCause: object with summary and at least one evidence item for verified.changes: array of { "file", "summary" } objects.verification: array of { "command", "result", "evidence" } objects.gaps: array of explicit missing proof statements.Baseline results are failed, observed, or not-run. Verification results are passed, failed, or not-run.
For verified:
failed or observed, never not-run.location and observation.passed.gaps to be empty.For partial:
gaps.passed.For blocked:
not-run; do not speculate about the result.Validate against receipt.schema.json, run node scripts/validate-receipt.mjs <file> from the skill directory, pipe JSON to node scripts/validate-receipt.mjs - --json, or use bug-receipt check <file> when the package CLI is installed.