Sibling articles under this feature previously restated requirements in inconsistent forms.
Lowering contract
Platform spec feature
Lowering contract
Spec standingStandard
-
This feature hub owns normative MUST/SHOULD contract text for Lowering contract.
Context
Decision
This feature hub owns normative MUST/SHOULD contract text. Sibling articles must not redefine hub requirements and should link here for authority.
Consequences
Contract changes start on the hub or in linked ADRs, then propagate to articles and implementation anchors.
Verification anchors
site/website/src/content/docs/platform-spec/compiler/codegen-and-ir/lowering-contract/index.mdxarticle bundle under the same feature directory.
-
Platform-spec text supersedes informal crate comments for Lowering contract.
Context
Implementation crates accumulated informal notes that diverged from published contracts.
Decision
Normative platform-spec prose and ADRs under this feature supersede informal comments in implementation crates until explicitly migrated into spec text.
Consequences
Engineers file spec/ADR updates when behavior changes; crate comments are non-authoritative for conformance arguments.
Verification anchors
compiler/crates/beskid_codegencompiler/crates/beskid_codegencompiler/crates/beskid_engine/src/jit_module.rs
-
Lowering was split across experimental paths.
Context
Lowering was split across experimental paths.
Decision
beskid_codegen::lower_sourceis the single lowering entry producingCodegenArtifactconsumed byJitModule.Consequences
Experimental IR dumps must not bypass this entry in release builds.
Verification anchors
compiler/crates/beskid_codegencompiler/crates/beskid_engine/src/jit_module.rs.
- Contracts and edge cases Normative guarantees and known edge cases for `Lowering contract`.
- Design model Conceptual model for `Lowering contract` and its subsystem boundaries.
- Examples Practical examples that demonstrate `Lowering contract` behavior.
- FAQ and troubleshooting Common questions and debugging guidance for `Lowering contract`.
- Flow and algorithm End-to-end control flow and major algorithmic steps for `Lowering contract`.
- Verification and traceability How `Lowering contract` requirements map to tests and implementation anchors.
0 revisions (git unavailable at build; counts may be empty)
No commits recorded for this path.
| Section id | Required | Found |
|---|---|---|
what-this-feature-specifies | yes | yes |
implementation-anchors | yes | yes |
Full tree: run pnpm verify:platform-spec-layout (writes src/generated/platform-spec-layout-report.json).
What this feature specifies
This feature explains how source text becomes a backend-ready artifact without changing language semantics late in the pipeline. It is organized into newcomer-friendly articles that move from model, to flow, to contracts, then practical verification and debugging guidance.
Implementation anchors
beskid_codegen::lower_sourceincompiler/crates/beskid_codegenCodegenArtifactconstruction incompiler/crates/beskid_codegenJitModuleconsumption incompiler/crates/beskid_engine/src/jit_module.rs- Runtime execution coverage in
compiler/crates/beskid_tests/src/runtime/jit.rs
Decisions
Section titled “Decisions”No open decisions. Closed choices are normative ADRs under adr/ (D-COMP-IR-0007 … D-COMP-IR-0009); use the reader ADRs tab for expandable detail.
Articles
- Feature hub authorityThis feature hub owns normative MUST/SHOULD contract text for Lowering contract.
- Contracts and edge casesNormative guarantees and known edge cases for `Lowering contract`.
- Design modelConceptual model for `Lowering contract` and its subsystem boundaries.
- ExamplesPractical examples that demonstrate `Lowering contract` behavior.
- FAQ and troubleshootingCommon questions and debugging guidance for `Lowering contract`.
- Flow and algorithmEnd-to-end control flow and major algorithmic steps for `Lowering contract`.
- Verification and traceabilityHow `Lowering contract` requirements map to tests and implementation anchors.