Engineering roadmaps where every milestone is a proof.
Most roadmaps hand you a graph of keywords and leave "learned it" undefined. Here every node states its finishing condition in advance — You're done when … — and meeting it leaves an artifact outside your head: a merged eval, a confirmed break, a green test suite, a fabricated board. Finish a node and you have evidence, not a feeling.
→ proofstone.dev — every roadmap, rendered and cross-linked.
| Roadmap | For the engineer moving into … |
|---|---|
| AI Safety Engineer | evals, red-teaming, guardrails, agent security |
| Distributed Systems Engineer | consensus, replication, failure detection |
| Applied Cryptography | breaking it in Cryptopals and CryptoHack, then shipping it right |
Two more — Robotics Software Engineer and PCB Design — are with practitioner reviewers and stay private until that review passes.
Some milestones ship with runnable code, because "read about SWIM" and "implement SWIM and pass a deterministic suite" are different claims.
- swim-lab — the Distributed Systems §4.1 milestone made executable: you implement SWIM, a deterministic suite grades it.
The roadmap repositories are the source of truth; proofstone.dev is the render layer and rebuilds itself when a roadmap changes. Open a pull request on the roadmap your change belongs to.
A node earns its place by naming a finishing condition someone else can check. If it cannot be proven, it is not a milestone.
