Legacy spec mapping
Platform spec domain
Legacy spec mapping
No architecture decision records under adr/ for this feature yet. Standard features must
publish at least one ADR or keep a ## Decisions summary on the hub.
- No directly attached article pages for this node.
0 revisions (git unavailable at build; counts may be empty)
No commits recorded for this path.
| Section id | Required | Found |
|---|---|---|
rationale | yes | yes |
background | no | no |
notice | yes | yes |
canonical | yes | yes |
scope | yes | yes |
execution-mapping | yes | yes |
corelib-mapping | yes | yes |
maintenance | yes | yes |
Full tree: run pnpm verify:platform-spec-layout (writes src/generated/platform-spec-layout-report.json).
Rationale
Readers still follow links to legacy /execution/ and /corelib/ trees. This domain records non-normative path crosswalks to canonical platform-spec destinations without forking language law.
Non-normative notice
This domain is non-normative. It exists only to bridge URLs from the legacy Starlight trees at /execution/ and /corelib/. Do not cite these mappings as language law; use the linked canonical pages.
Canonical destinations
| Domain | Role | Hub |
|---|---|---|
| Language meta | User-visible semantics | /platform-spec/language-meta/ |
| Compiler | Pipeline and resolution | /platform-spec/compiler/ |
| Execution | Runtime, ABI, fibers, GC | /platform-spec/execution/ |
| Core library | Standard library contracts | /platform-spec/core-library/ |
| Tooling | Manifests, CLI, LSP | /platform-spec/tooling/ |
Mapping scope
Included: Stable path correspondences for legacy /execution/* and /corelib/* pages still linked from books, issues, or READMEs.
Excluded: Per-symbol API listings (remain in compiler corelib package docs); v0.1 stubs with no platform-spec feature yet (mapped to nearest area hub).
Legacy execution (`/execution/`)
Legacy corelib (`/corelib/`)
Maintenance
Retire this domain when Standard platform-spec pages no longer link to /execution/ or /corelib/ without a non-normative relation and legacy traffic is negligible for two release cycles.