Composition
Platform spec area
Composition
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 |
|---|---|---|
scope | yes | yes |
features | yes | yes |
Full tree: run pnpm verify:platform-spec-layout (writes src/generated/platform-spec-layout-report.json).
Scope
Language-native dependency injection and host composition: named host types (multiple per project; one launch per run), registry global scope, nested scope with init / dispose, with activation, field inject (singular and T[] plural), global:: / parent:: navigation, and launch. Library projects may define host but must not launch. The reference compiler resolves the service graph at compile time; execution backends consume a frozen binding plan.
Rust pipeline composition (compiler pass wiring) and compiler mod registration are specified separately under Pipeline composition and Compiler Mods.
Feature index
Use the tiles below for normative feature contracts in this area.