Verification receipts

Verification is only useful when it proves the right thing in the right place.

Orcho records receipts so readiness is not based only on a sentence like “tests passed”. A receipt should make the verification environment inspectable:

• command;
• working directory;
• interpreter or runtime;
• source path;
• result;
• relevant provenance assertions.

Why receipts matter

Without receipts, a run can look green while testing the wrong checkout, missing a sibling change, or relying on a stale command.

Receipts let final acceptance distinguish:

• no check was run;
• a check ran but failed;
• a check ran in the wrong place;
• a check ran in the expected environment and passed.

That distinction is central to Orcho’s trust model.