Evidence and Proof · Lesson 02 of 04
Runtime and lifecycle proof
Runtime proof evaluates selected runtime obligations; lifecycle proof additionally binds phase transitions, teardown authority, and exact cleanup.
Learning objectives
- Distinguish runtime proof from task exit-code proof
- Run
ota proof runtimeand read the result - Identify what lifecycle proof adds over runtime proof
Prerequisites
Runtime proof evaluates one declared workflow's runtime obligations. Lifecycle proof additionally binds startup, readiness, assertion, teardown authority, and terminal cleanup transitions for the selected service boundary.
Runtime proof
Runtime proof resolves the selected workflow, exercises its declared runtime surfaces and dependency obligations, and can include a contract-owned negative control. Its verdict remains bounded by not_proved records for obligations Ota could not establish.
ota proof runtime --workflow app --json --archiveLifecycle proof
Lifecycle proof is phase-accurate. Cleanup authority must be acquired before service start, and terminal evidence can claim only the exact boundary Ota removed. Failed or interrupted setup cannot be reported as completed simply because later cleanup succeeded.
ota proof lifecycle --workflow smoke --service database --json --archiveCanonical terminology
Commands and expected output
ota proof runtime --workflow app --json --archiveota proof lifecycle --workflow smoke --service database --json --archiveEvidence boundary for this lesson
Establishes
- The worked examples establish the lesson's canonical Ota distinctions for its stated scope.
Does not establish
- Reading the lesson does not validate a repository, execute its tasks, or establish organizational acceptance.
Knowledge check
What does lifecycle proof add beyond runtime readiness?
It binds phase-valid transitions, teardown authority, terminal outcome, and exact cleanup for the selected service boundary.