Module 04

Evidence and Proof

Learn how Ota captures and interprets execution evidence: receipts, archives, runtime and lifecycle proof, negative controls, freshness, replay, promotion, and semantic identity.

Module curriculum

Lessons in Evidence and Proof

Follow the sequence to build the model, then use the exercises to test the boundary.

Lesson 019 min read

Receipts and archives

Receipts are typed, producer-bounded evidence; archives preserve identity-bound history without expanding what the evidence proves.

Describe the structure of a receipt
Explain what archive identity can detect and what mutable local storage cannot authenticate

Lesson 028 min read

Runtime and lifecycle proof

Runtime proof evaluates selected runtime obligations; lifecycle proof additionally binds phase transitions, teardown authority, and exact cleanup.

Distinguish runtime proof from task exit-code proof
Run ota proof runtime and read the result

Lesson 037 min read

Negative controls

Runtime negative controls challenge a proof obligation; refusal canaries separately verify agent admission remains closed.

Explain how a runtime negative control challenges one proof obligation
Reconcile the control identity, obligation, failure mode, and attestation digest

Lesson 048 min read

Freshness, replay, promotion, and identity

How Ota derives prerequisite materialization freshness, promotes replay authority explicitly, and binds inputs and outputs through semantic identity.

Explain per-prerequisite materialization freshness
Describe the record, promotion, and replay-consumption authority chain