Verification — bi-15-vertical-traces

A module is complete when these pass against measured or observed output, not when the prose has been read.

  • Each trace: every layer resolved with evidence, or explicitly recorded unresolved
  • Process and thread named at every resolved step
  • Deferred vs immediate stated at every step
  • At least one variant constructed per trace that changes which layers are involved
  • Evidence type (source/trace/debugger) recorded per layer
  • PROGRESS.md ledger updated with deepest genuinely resolved layer

Gate (§44) — for every source-reading exercise in this module

  • Why does this code exist?
  • What invariant does it maintain?
  • Who calls it?
  • What does it call?
  • Which process and thread executes it?
  • What happens if it is removed?
  • How is it tested?
  • What simpler design would fail, and why?

Record