Specification over implementation notes
Platform spec ADR
Specification over implementation notes
Spec standingStandard
- Contracts and edge cases Normative guarantees and known edge cases for `Crate-to-spec anchors`.
- Design model Conceptual model for `Crate-to-spec anchors` and its subsystem boundaries.
- Examples Practical examples that demonstrate `Crate-to-spec anchors` behavior.
- FAQ and troubleshooting Common questions and debugging guidance for `Crate-to-spec anchors`.
- Flow and algorithm End-to-end control flow and major algorithmic steps for `Crate-to-spec anchors`.
- Verification and traceability How `Crate-to-spec anchors` requirements map to tests and implementation anchors.
0 revisions (git unavailable at build; counts may be empty)
No commits recorded for this path.
| Section id | Required | Found |
|---|---|---|
what-this-feature-specifies | yes | yes |
implementation-anchors | yes | yes |
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/