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:
- What it does. TODO: explain what belongs here.
- How you know it works. TODO: explain what belongs here.
- Constraints. TODO: explain what belongs here.
- Decisions and trade-offs. TODO: explain what belongs here.
- How it fails. TODO: explain what belongs here.
- Running it alone. TODO: explain what belongs here.
- 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.