Specification over implementation notes
Platform spec ADR
Specification over implementation notes
Spec standingStandard
- Build and run orchestration - Contracts and edge cases States the normative guarantees and what happens at boundaries or failure edges.
- Build and run orchestration - Design model Explains the persistent concepts, entities, and boundaries this feature relies on.
- Build and run orchestration - Examples Gives concrete newcomer-friendly scenarios mapped to real compiler paths.
- Build and run orchestration - FAQ and troubleshooting Answers common operator and contributor questions with practical next checks.
- Build and run orchestration - Flow and algorithm Walks through runtime/order-of-operations behavior in the implementation.
- Build and run orchestration - 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”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_cli/src/commands/compiler/crates/beskid_engine/src/jit_module.rscompiler/crates/beskid_tests/src/runtime/jit.rs