Specification over implementation notes
Platform spec ADR
Specification over implementation notes
Spec standingStandard
- Dependency workspace and lockfile - Contracts and edge cases Normative behavior for lock mismatch, missing registry artifacts, and policy flags.
- Dependency workspace and lockfile - Design model Data model for compile plans, prepared workspaces, lock records, and dependency source roots.
- Dependency workspace and lockfile - Examples Concrete examples for frozen and locked workflows with project dependencies.
- Dependency workspace and lockfile - FAQ and troubleshooting Operational troubleshooting for lockfile synchronization and dependency workspace preparation.
- Dependency workspace and lockfile - Flow and algorithm Workflow from compile-plan construction to workspace materialization and lockfile synchronization.
- Dependency workspace and lockfile - Verification and traceability Source anchors and test evidence for compile-plan and lockfile behavior.
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/