Verification — bi-08-layout

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

  • mini-browser M7–M9: layout tree, block layout, inline text, basic flex
  • Margin collapsing implemented; the three rules written down
  • Intrinsic sizing implemented; the second pass observed
  • Result caching implemented; hit rate measured for resize vs deep text change
  • Incomplete cache key produces a wrong render — demonstrated
  • Forced sync layout measured at n=100/1000/5000 and plotted

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