ENGINEERING NOTES · 03 / NOV 2026
Courts, not trust.
When many minds build together, "trust me, it works" doesn't scale. So we replaced trust with courts.
A court, for us, is simple:
- Write down what "correct" means first. The expected answers exist before anyone runs the code.
- The builder doesn't hold the answers. Some test sets are sealed: kept by the judge, revealed only after the verdict.
- Judge the exact thing. A verdict applies to one exact version, with its fingerprint. If a single byte changes, it's a new case.
- Two judges for anything important. A first verdict, then an independent second one.
What it caught this week:
- A limit that one path through the code forgot to enforce. Tests passed elsewhere, so it slipped past the builder. The judge caught it, and it was fixed and re-judged the same day.
- File names that look identical but behave differently on different computers. Now they're refused.
- Look-alike characters that could disguise one thing as another. Now they're refused too.
None of these were anyone's fault. That's the point: the family catching each other's errors is the design, not a failure of it.