Sibling articles under this feature previously restated requirements in inconsistent forms.
Conformance evidence policy
Platform spec feature
Conformance evidence policy
Spec standingStandard
-
This feature hub owns normative MUST/SHOULD contract text for Conformance evidence policy.
Context
Decision
This feature hub owns normative MUST/SHOULD contract text. Sibling articles must not redefine hub requirements and should link here for authority.
Consequences
Contract changes start on the hub or in linked ADRs, then propagate to articles and implementation anchors.
Verification anchors
site/website/src/content/docs/platform-spec/compiler/conformance/conformance-evidence-policy/index.mdxarticle bundle under the same feature directory.
-
Platform-spec text supersedes informal crate comments for Conformance evidence policy.
Context
Implementation crates accumulated informal notes that diverged from published contracts.
Decision
Normative platform-spec prose and ADRs under this feature supersede informal comments in implementation crates until explicitly migrated into spec text.
Consequences
Engineers file spec/ADR updates when behavior changes; crate comments are non-authoritative for conformance arguments.
Verification anchors
compiler/crates/beskid_tests/src/analysis/diagnostics.rscompiler/crates/beskid_tests/src/doc_tests.rscompiler/crates/beskid_e2e_tests/src/tests/runtime_cases.rs
-
Release arguments lacked traceable proof layers.
Context
Release arguments lacked traceable proof layers.
Decision
Standard conformance claims require analysis fixtures, doc tests, and e2e runtime evidence—mapped in hub verification articles.
Consequences
A single test kind cannot satisfy Standard maturity alone.
Verification anchors
compiler/crates/beskid_tests/compiler/crates/beskid_e2e_tests/.
- 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).
This feature hub defines the normative contract for conformance evidence policy and links newcomer-oriented reference articles.
Implementation anchors
Section titled “Implementation anchors”compiler/crates/beskid_tests/src/analysis/diagnostics.rsprovides semantic conformance evidence.compiler/crates/beskid_tests/src/doc_tests.rsvalidates docs-facing conformance examples.compiler/crates/beskid_e2e_tests/src/tests/runtime_cases.rsprovides executable behavior evidence.
Compiler mods evidence (required when feature ships)
Section titled “Compiler mods evidence (required when feature ships)”Conformance for Mod projects must include, at minimum:
- Manifest goldens — Valid and invalid
Project.proj/Workspace.projpairs with stable diagnostic codes fortype = Mod,modsettings, and capability violations. - Pipeline ordering — A test
PipelineObserverrecording parse,mod.load,mod.collect,mod.generate, semantic gate,mod.analyze,mod.rewrite, and lowering in documented order. - Incremental replay — Fixtures performing edits with identical keys that assert stable generator outputs.
- Analyzer coverage — Fixtures showing analyzers run over host and generated code.
- LSP parity — Snapshot tests ensuring mod diagnostics round-trip through
beskid_lspwith the same codes as CLI analysis.
Fixture layout for manifest/mod work must follow names documented in Project manifest contract / verification.
Decisions
Section titled “Decisions”No open decisions. Closed choices are normative ADRs under adr/ (D-COMP-CONF-0001 … D-COMP-CONF-0003); use the reader ADRs tab for expandable detail.