Verification — bi-10-compositor-gpu

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

  • Frame budget decomposed from a trace into script/style/layout/paint/raster/GPU
  • Passive vs non-passive scroll latency measured; mechanism and number explained
  • Compositor vs main-thread animation compared under a 500 ms blocking task
  • Checkerboarding captured and explained via tiles and raster priority
  • Frame budget recomputed against 8.3 ms; the term that breaks first identified

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