evalfirst

Method

Placeholder. TODO: this page is a stub. The structure below is real; the prose still has to be written.

Every teardown in evalfirst follows one fixed template. Its point is that verification comes before architecture: you read how a system is known to work before you read how it is built.

The template

Each teardown has the same seven sections, in the same order:

  1. What it does. TODO: explain what belongs here.
  2. How you know it works. TODO: explain what belongs here.
  3. Constraints. TODO: explain what belongs here.
  4. Decisions and trade-offs. TODO: explain what belongs here.
  5. How it fails. TODO: explain what belongs here.
  6. Running it alone. TODO: explain what belongs here.
  7. Interview answer. TODO: explain what belongs here.

Status labels

Every teardown says how much to trust it:

  • Public sources. Written from public material only. Nobody who built the system has reviewed it.
  • Builder reviewed. Written from public material and checked by someone who worked on the system.
  • First-hand. Written by someone who built or operated the system.

Sourcing

TODO: explain the sourcing bar. Every claim about a real system needs a public source or a builder's confirmation, and inference is labelled as inference.

Why verification first

TODO: make the argument.

Suggest a correction