Verification — bi-02-architecture-process-model

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

  • Process census for a trivial page vs a painting, cross-origin page
  • thread backtrace all run; main/compositor/raster/IO thread names written down
  • Cross-site iframe creates a second renderer; same-site does not — verified
  • Blocked main thread: explained what still works, in terms of threads
  • Found a browser-side Mojo validation test and named the invariant it encodes

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