13. Reading the law without going blind
Navigate platform-spec domains, maps, graphs, and feature hubs without tab bankruptcy.
Reading the law without going blind
The Platform specification is large on purpose: languages are not one PDF. This chapter is a map reader’s guide, covering where home tiles live, how domains split, and when to open an architecture graph instead of guessing crate names.
What you will find here
Section titled “What you will find here”| Section | Topic |
|---|---|
| Platform spec home | Entry, domains, maturity badges. |
| Language meta map | Syntax, types, evaluation, interop. |
| Compiler domain map | Pipeline, front-end, mods, conformance. |
| Execution and corelib | Runtime vs standard library law. |
| Tooling domain map | CLI, LSP, manifests, registry. |
| Implementation map | Crate-to-spec anchors. |
| Architecture graphs | Dagre pipeline graphs in the reader. |
A repeatable route through the standard
Section titled “A repeatable route through the standard”Start with a domain, narrow to an area and feature hub, then read the relevant requirement. Only after that should you follow architecture graphs or implementation anchors. This makes it easier to distinguish a language guarantee from a compiler, runtime, or tooling concern.