Sibling articles under this feature previously restated requirements in inconsistent forms.
Workspace and lock contracts - Flow and algorithm
Platform spec article
Workspace and lock contracts - Flow and algorithm
Spec standingStandard
-
This feature hub owns normative MUST/SHOULD contract text for Workspace and lock contracts.
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/resolution-and-projects/workspace-and-lock-contracts/index.mdxarticle bundle under the same feature directory.
-
Platform-spec text supersedes informal crate comments for Workspace and lock contracts.
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_analysis/src/resolve/mod.rscompiler/crates/beskid_cli/src/commands/compiler/crates/beskid_tests/src/projects/corelib/compile.rs
-
Floating registry versions broke reproducible compiles.
Context
Floating registry versions broke reproducible compiles.
Decision
Workspace resolution must honor lockfile pins from
beskid_analysis::resolvebefore applying CLI overrides.Consequences
Lock update commands are explicit; silent refresh is forbidden in CI modes.
Verification anchors
compiler/crates/beskid_analysis/src/resolve/mod.rscompiler/crates/beskid_cli/src/commands/.
- Workspace and lock contracts - Contracts and edge cases Compiler guarantees for lock-backed graphs and workspace layout invariants.
- Workspace and lock contracts - Design model Compiler entities for workspace roots and lock materialization (workspace key prose defers to tooling).
- Workspace and lock contracts - Examples Gives concrete newcomer-friendly scenarios mapped to real compiler paths.
- Workspace and lock contracts - FAQ and troubleshooting Answers common operator and contributor questions with practical next checks.
- Workspace and lock contracts - Flow and algorithm Compiler order of operations for workspace discovery, lock apply, and graph materialization.
- Workspace and lock contracts - 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).
Resolution flow
Section titled “Resolution flow”- Locate workspace root and member projects.
- Load lock snapshot (or fail if policy requires a lock and none is present).
- Materialize dependency roots from lock pins into the resolver cache layout.
- Build the combined workspace/project graph (see project manifest contract / flow).
- Proceed to analysis only when graph and layout invariants pass.
CLI lock update and author workflows are described under tooling / flow and algorithm.
Code anchors
Section titled “Code anchors”compiler/crates/beskid_analysis/src/resolve/mod.rscompiler/crates/beskid_cli/src/commands/compiler/crates/beskid_tests/src/analysis/pipeline/core.rs