12. The normative bible (and why we bothered)
Informative vs normative docs, spec-leads-code, Git versioning, and ADRs—without theology degrees.
The normative bible (and why we bothered)
Every language project eventually grows a Google Doc titled “FINAL spec v3 (real).” Beskid skipped that stage and went straight to Platform specification—one tree, Git as the version axis, and ADRs instead of hallway folklore.
This book is informative. When we argue, we argue against the spec—not against a README paragraph from 2019.
What you will find here
Section titled “What you will find here”| Section | Topic |
|---|---|
| Informative vs normative | Book vs platform-spec vs legacy bridges. |
| Spec leads code | Change order that saves retrospectives. |
| Language law vs implementation | language-meta vs compiler/execution/tooling. |
| Proposed vs Standard | Maturity and enforceability. |
| Git as version axis | No /platform-spec/v0.2/ URLs. |
| ADRs and decisions | Embedded decisions and adr/ files. |
| How to propose a change | Practical contributor path. |