Evidence ladder — a check is not runtime
The checks prove clean HEAD, syntax, tier contracts, dispatcher smoke, and CLI help. They do not prove installation, healthy containers, chat, UI, security, backup, or uninstall.
Complete Simple + Technical
The checks prove clean HEAD, syntax, tier contracts, dispatcher smoke, and CLI help. They do not prove installation, healthy containers, chat, UI, security, backup, or uninstall.
Bounded analogy: Plans and materials may be coherent; only an instrumented crossing proves the bridge in use. Software also changes state during execution.
Under the hood
The runner checked the exact commit and used pipefail. The receipt marks installation, runtime, and Docker/Compose as not executed. That non-claim is part of the proof.
Boundary: installation, runtime, and Docker/Compose were not executed.
14 semantic microdiagrams
Each figure teaches one relationship; the sequence is a decision map, not a health dashboard.
Command and proof boundary
bash work/run-nonmutating-checks.sh rg -n 'Exit code|Fronteira de prova|Resultado geral' outputs/ods-check-receipt.md
Allows claiming
| check | reading |
|---|---|
| local | exercised contract |
| upstream | declared capability |
Remains open
| runtime | gate |
|---|---|
| health/chat/UI | live pilot |
| lifecycle | backup/restore/uninstall |
Local sources
outputs/ods-adoption-dossier.md:89-109outputs/ods-check-receipt.md:8-33work/ods-latest/ods/docs/RELEASE_VALIDATION.md:98-115outputs/ods-check-receipt.md:120-135,222-232
Includes dossier, receipt, and official source by path:line.
Practice with feedback
1 · Prediction
2 · Stepper
1. classify the need
2. locate the proof
3. decide without overclaiming
3 · Scenarios
4 · Checklist
6 · Quiz
What does macOS smoke prove?