Specification over implementation notes
Platform spec ADR
Specification over implementation notes
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”Implementation crates accumulated informal notes that diverged from published contracts.
Decision
Section titled “Decision”Normative platform-spec prose and ADRs under this feature supersede informal comments in implementation crates until explicitly migrated into spec text.
Consequences
Section titled “Consequences”Engineers file spec/ADR updates when behavior changes; crate comments are non-authoritative for conformance arguments.
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