Feature hub authority
Platform spec ADR
Feature hub authority
Spec standingStandard
- Backends (JIT and AOT) - Contracts and edge cases Required backend guarantees for output kinds, entrypoints, and shared lowering semantics.
- Backends (JIT and AOT) - Design model Backend responsibility split and shared artifact model for run and build commands.
- Backends (JIT and AOT) - Examples Example command outcomes for JIT execution and AOT output kinds.
- Backends (JIT and AOT) - FAQ and troubleshooting Troubleshooting for backend-specific build or run failures.
- Backends (JIT and AOT) - Flow and algorithm Ordered backend execution for run and build after lowering completes.
- Backends (JIT and AOT) - Verification and traceability Crate-level anchors and tests that verify backend divergence and shared lowering contract.
0 revisions (git unavailable at build; counts may be empty)
No commits recorded for this path.
Full tree: run pnpm verify:platform-spec-layout (writes src/generated/platform-spec-layout-report.json).
Context
Section titled “Context”Sibling articles under this feature previously restated requirements in inconsistent forms.
Decision
Section titled “Decision”This feature hub owns normative MUST/SHOULD contract text. Sibling articles must not redefine hub requirements and should link here for authority.
Consequences
Section titled “Consequences”Contract changes start on the hub or in linked ADRs, then propagate to articles and implementation anchors.
Verification anchors
Section titled “Verification anchors”site/website/src/content/docs/platform-spec/compiler/build-pipeline/backends-jit-aot/index.mdxarticle bundle under the same feature directory.