Specification over implementation notes
Platform spec ADR
Specification over implementation notes
Spec standingStandard
- Contracts and edge cases Non-negotiable parser contracts and common edge-case handling rules.
- Design model Mental model for how the front-end parser and syntax model are organized.
- Examples Concrete examples that show parser contracts in daily compiler work.
- FAQ and troubleshooting Common parser and syntax questions with practical debugging guidance.
- Flow and algorithm Step-by-step parse flow from source text to syntax structures.
- Verification and traceability How to verify parser behavior and trace docs back to source.
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/beskid.pestcompiler/crates/beskid_analysis/src/parsingcompiler/crates/beskid_analysis/src/syntax/items