Labs · Lesson 03 of 05
Lab: Interpret a bounded receipt
Read a real receipt from a not_proved boundary and explain what it does and does not certify.
Learning objectives
- Identify the
not_provedentries in a receipt - Explain why the bounded scope is honest
- State what additional proof would be needed to close the gap
Prerequisites
This lab practices claim discipline. You will inspect one execution-produced receipt and state exactly what it proves, what it only records, and which adjacent behavior remains unproved.
Produce inspectable evidence
Choose a finite, agent-safe verifier with no external credentials. Capture JSON so identities, selected closure, outcome, and boundaries can be inspected without scraping terminal prose.
ota run --agent --receipt --json testWrite a bounded verdict
Name the contract identity, selected task, execution mode, completed outcome, and material not_proved boundaries. Do not claim repo-global correctness, production readiness, container isolation, or CI parity unless those exact claims have evidence.
Canonical terminology
Evidence boundary for this lesson
Establishes
- You can interpret a receipt correctly
Does not establish
- Any specific execution was valid
Knowledge check
Which fields anchor a bounded execution claim?
Use the producer, contract identity, selected closure, execution mode, outcome, evidence classes, and explicit not_proved boundaries together.