Canonical parse-to-lowering phase DAG
Platform spec ADR
Canonical parse-to-lowering phase DAG
Spec standingStandard
- Stage ordering and lowering - Contracts and edge cases Required ordering guarantees and behavior under parse or semantic failures.
- Stage ordering and lowering - Design model Pipeline stage model and artifact boundaries for the reference compiler.
- Stage ordering and lowering - Examples Newcomer-oriented examples of pipeline execution order and failure points.
- Stage ordering and lowering - FAQ and troubleshooting Troubleshooting guide for stage ordering assumptions in build and run commands.
- Stage ordering and lowering - Flow and algorithm Ordered lowering algorithm used by build and run command paths.
- Stage ordering and lowering - Verification and traceability Source and test anchors that verify lowering order and backend artifact handoff.
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”Reference compiler must emit stable beskid_pipeline phase events from parse through lower.ready without reordering semantic gates relative to mod boundaries.
Decision
Section titled “Decision”Phase literals are defined in compiler/crates/beskid_pipeline/src/phases.rs and asserted by conformance tests; CLI/LSP observers rely on the same ids.
Consequences
Section titled “Consequences”Reordering phases requires an ADR and registry updates.
Verification anchors
Section titled “Verification anchors”compiler/crates/beskid_pipeline/compiler/crates/beskid_analysis/src/services.rs.