Primary contract for Rules and diagnostics catalog
Platform spec ADR
Primary contract for Rules and diagnostics catalog
Spec standingStandard
- Contracts and edge cases Rule-level guarantees and high-risk semantic edge cases.
- Design model Mental model for staged semantic rules and diagnostic production.
- Examples Practical examples of semantic rule outcomes and diagnostic generation.
- FAQ and troubleshooting Common semantic-pipeline debugging questions and practical checks.
- Flow and algorithm End-to-end semantic rule flow from resolved items to user-facing diagnostics.
- Verification and traceability How semantic rule behavior is validated and traced to source modules.
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”This feature defines how semantic rules are scheduled and how their findings map to stable diagnostic kinds. The primary implementation roots are beskid_analysis/src/analysis, staged rule modules under analysis/rules/staged, and services that expose diagnostics to CLI/LSP consumers.
Decision
Section titled “Decision”The reference compiler must implement Rules and diagnostics catalog as documented in this feature hub and its article bundle.
Consequences
Section titled “Consequences”Changes require hub/ADR updates and verification anchor extensions.
Verification anchors
Section titled “Verification anchors”compiler/crates/beskid_analysis/src/analysiscompiler/crates/beskid_analysis/src/analysis/rules/stagedcompiler/crates/beskid_analysis/src/analysis/diagnostic_kinds.rs