Verification — bi-09-paint

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

  • mini-browser M10–M11: display list, stacking contexts, transform tree, raster
  • Stage-5 experiment: re-record vs property-tree-only change, measured
  • Baked-transform variant proves the cheap path impossible
  • Reverse-paint-order hit testing disagrees with DOM order in a constructed case
  • Layer explosion measured (5,000 x will-change)

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