Compiler
Platform spec domain
Compiler
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. Nested descendants exist deeper in this subtree.
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 | yes |
Full tree: run pnpm verify:platform-spec-layout (writes src/generated/platform-spec-layout-report.json).
Rationale
The compiler domain owns implementation-facing contracts: phases that must exist, ordering constraints, diagnostic classes, and how source maps tie back to user code. Language semantics that users rely on without caring about pipeline shape live primarily under Language meta.
Background
Build pipeline — Formal contracts for the reference compiler’s resolution, lowering, lockfile/workspace behaviour, diagnostics surfaces, and JIT versus AOT backends live under Build pipeline (area with feature leaves and an architecture graph).
Execution — Long-form runtime ABI, IR narrative, and host integration chapters remain under Execution; the build-pipeline area links to those chapters from backend features where relevant.
Normative language law — The Language meta domain is the canonical language specification surface; compiler pages do not fork normative prose.
Compiler Mods — Mod host orchestration, AOT artifact lifecycle, typed collector/generator/analyzer/rewriter execution, stable beskid_pipeline phase ids, and incremental determinism under Compiler Mods. Beskid contracts: Compiler Mod SDK. Rust composition: Pipeline composition. v0.3 dynamic mapping: Dynamic types and mapping.
Areas
- Build pipelineFormal platform contracts for project resolution, lowering, diagnostics parity, and JIT versus AOT backends in the reference compiler.
- Codegen and IRLowering contracts from analyzed source into backend-ready artifacts and IR-related invariants.
- Compiler ModsRust-side compiler mod host, AOT mod lifecycle, typed merge pipeline, and incremental orchestration for Mod projects.
- ConformanceCompiler conformance harnesses, fixture policies, and behavior-locking test contracts.
- Front-endGrammar, parser, syntax structures, and formatting contracts in the compiler front-end.
- Implementation mapCrate-level map of the compiler workspace with normative ownership boundaries and feature anchors.
- Pipeline compositionRust-native compiler composition, pass registration, and phase DAG (separate from Mod projects).
- Resolution and projectsName resolution, workspace/project discovery, and lockfile-related compiler contracts.
- Semantic pipelineSemantic analysis phases, rule execution, and diagnostic classification in the reference compiler.