Verification — bi-16-capstone

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

  • Application runs on your own compiler, runtime, store, router and query cache
  • Every observable layer instrumented
  • setCount(count+1) explained end to end, incl. skipped stages and why
  • Complexity notebook: all 12 entries, each classified and defended
  • Comparison matrix: 7 rows x 10 axes, incl. the Blink style-invalidation row
  • All 7 design challenges answered with constraints, invariants, failure modes
  • Mastery criteria checklist complete

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