Sibling articles under this feature previously restated requirements in inconsistent forms.
Rules pipeline contract
Platform spec feature
Rules pipeline contract
Spec standingStandard
-
This feature hub owns normative MUST/SHOULD contract text for Rules pipeline 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/semantic-pipeline/rules-pipeline-contract/index.mdxarticle bundle under the same feature directory.
-
Platform-spec text supersedes informal crate comments for Rules pipeline 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_analysis/src/analysis/rules/compiler/crates/beskid_analysis/src/analysis/diagnostic_kinds.rscompiler/crates/beskid_analysis/src/services.rs
-
Monolithic semantic passes blocked incremental invalidation.
Context
Monolithic semantic passes blocked incremental invalidation.
Decision
Semantic rules are grouped in
analysis/rules/staged/with explicit stage boundaries wired throughservices.rsfor CLI and LSP.Consequences
New rules declare their stage; cross-stage dependencies are documented in the hub articles.
Verification anchors
compiler/crates/beskid_analysis/src/analysis/rules/.
- Rules pipeline contract - Contracts and edge cases States the normative guarantees and what happens at boundaries or failure edges.
- Rules pipeline contract - Design model Explains the persistent concepts, entities, and boundaries this feature relies on.
- Rules pipeline contract - Examples Gives concrete newcomer-friendly scenarios mapped to real compiler paths.
- Rules pipeline contract - FAQ and troubleshooting Answers common operator and contributor questions with practical next checks.
- Rules pipeline contract - Flow and algorithm Walks through runtime/order-of-operations behavior in the implementation.
- Rules pipeline contract - Verification and traceability Shows how the team proves this feature works and where evidence lives.
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).
This feature hub defines the normative contract for rules pipeline contract and links newcomer-oriented reference articles.
Implementation anchors
Section titled “Implementation anchors”compiler/crates/beskid_analysis/src/analysis/rules/defines staged rule groups.compiler/crates/beskid_analysis/src/analysis/diagnostic_kinds.rsclassifies emitted diagnostics.compiler/crates/beskid_analysis/src/services.rswires semantic services used by CLI/LSP.
Decisions
Section titled “Decisions”No open decisions. Closed choices are normative ADRs under adr/ (D-COMP-SEM-0010 … D-COMP-SEM-0012); use the reader ADRs tab for expandable detail.