Verification — fw-04-mini-react-scheduling

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

  • bi-11 completed first
  • Explicit work loop replacing recursion
  • Yielding with a justified primitive choice
  • Render and commit phases separated; commit atomic
  • Double buffering; two priority levels with abandonment
  • Automatic batching
  • All six failure-lab bugs reproduced, incl. tearing
  • Complexity notebook: Fiber — the flagship entry
  • Measured: p75 input delay under load, recursive vs interruptible

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