Three-tier conformance evidence
Platform spec ADR
Three-tier conformance evidence
Spec standingStandard
- Conformance evidence policy - Contracts and edge cases States the normative guarantees and what happens at boundaries or failure edges.
- Conformance evidence policy - Design model Explains the persistent concepts, entities, and boundaries this feature relies on.
- Conformance evidence policy - Examples Gives concrete newcomer-friendly scenarios mapped to real compiler paths.
- Conformance evidence policy - FAQ and troubleshooting Answers common operator and contributor questions with practical next checks.
- Conformance evidence policy - Flow and algorithm Walks through runtime/order-of-operations behavior in the implementation.
- Conformance evidence policy - 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).
Context
Section titled “Context”Release arguments lacked traceable proof layers.
Decision
Section titled “Decision”Standard conformance claims require analysis fixtures, doc tests, and e2e runtime evidence—mapped in hub verification articles.
Consequences
Section titled “Consequences”A single test kind cannot satisfy Standard maturity alone.
Verification anchors
Section titled “Verification anchors”compiler/crates/beskid_tests/compiler/crates/beskid_e2e_tests/.