How We Developed This

The method behind Part I — and how to find out where your own program stands.

Part I shows you the architecture. This appendix shows you the workshop it was built in: how the study was actually conducted, the instrument it produced, and how you use that instrument to assess a team — yours or anyone’s — against what the corpus shows.

It reads in two movements. The first is method: how we read 55 season repositories, the index that lets us count a pattern across all of them, and the one rule that makes the findings trustworthy — score what’s used, not what’s present. The second is assessment: the eight-dimension rubric that turns “is this code good” into eight separately observable questions, the maturity ladder that tells you which rung a program is actually on and what pain moves it to the next, and an honest accounting of how much any of it predicts winning.

If Part I answers what the architecture is, this appendix answers how we know, and how you measure where you are in it.

1. How we read the corpus — the study end to end, and the rule that makes it trustworthy.
2. Eight dimensions of sophistication — the rubric: what it measures and how to read a profile.
3. The novice-to-elite maturity ladder — the five-season climb, sequenced by pain.
4. What the architecture predicts — the validation against competition results, honestly.
5. Foundation-first — the build order, the deferred dividends, and the one rule that carries it all.

• 1. How we read the corpus
• 2. Eight dimensions of sophistication
• 3. The novice-to-elite maturity ladder
• 4. What the architecture predicts
• 5. Foundation-first