Workspace and lock contracts - FAQ and troubleshooting

Platform spec article

Workspace and lock contracts - FAQ and troubleshooting

Back to Workspace and lock contracts ◎ Open feature in platform map

Spec standingStandard

Owner

Piotr Mikstacki pmikstacki@cybernomad.it

Submitter

Piotr Mikstacki pmikstacki@cybernomad.it

Current document

ADRs (3)

1. 0001-feature-hub-authority Feature hub authority Accepted

   This feature hub owns normative MUST/SHOULD contract text for Workspace and lock contracts.

   Context

   Sibling articles under this feature previously restated requirements in inconsistent forms.

   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.mdx
   • article bundle under the same feature directory.

   Open full ADR page

2. 0002-spec-over-implementation-notes Specification over implementation notes Accepted

   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.rs
   • compiler/crates/beskid_cli/src/commands/
   • compiler/crates/beskid_tests/src/projects/corelib/compile.rs

   Open full ADR page

3. 0003-lockfile-pins-resolution Lockfile pins drive resolution Accepted

   Floating registry versions broke reproducible compiles.

   Context

   Floating registry versions broke reproducible compiles.

   Decision

   Workspace resolution must honor lockfile pins from beskid_analysis::resolve before 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.rs
   • compiler/crates/beskid_cli/src/commands/.

   Open full ADR page

Articles

• Workspace and lock contracts - Contracts and edge cases Compiler guarantees for lock-backed graphs and workspace layout invariants. article Standard
• Workspace and lock contracts - Design model Compiler entities for workspace roots and lock materialization (workspace key prose defers to tooling). article Standard
• Workspace and lock contracts - Examples Gives concrete newcomer-friendly scenarios mapped to real compiler paths. article Standard
• Workspace and lock contracts - FAQ and troubleshooting Answers common operator and contributor questions with practical next checks. article Standard
• Workspace and lock contracts - Flow and algorithm Compiler order of operations for workspace discovery, lock apply, and graph materialization. article Standard
• Workspace and lock contracts - Verification and traceability Shows how the team proves this feature works and where evidence lives. article Standard

History

0 revisions (git unavailable at build; counts may be empty)

Open full history on GitHub

No commits recorded for this path.

Completeness

OKfeature · 2 SpecSection(s) · 2 H2 heading(s)

Full tree: run pnpm verify:platform-spec-layout (writes src/generated/platform-spec-layout-report.json).

Related spec docs

• Feature
  Workspace and lock contracts

  Parent feature hub

This article documents faq and troubleshooting for workspace and lock contracts in the reference compiler.

What this covers

For newcomers, this page explains where the contract shows up in day-to-day compiler work and which code paths are most useful first reads.

Anchored code paths

• compiler/crates/beskid_tests/src/projects/corelib/compile.rs covers lock-sensitive workspace builds.
• compiler/crates/beskid_tests/src/projects/corelib/layout.rs validates workspace folder invariants.
• compiler/crates/beskid_cli/src/commands/ is the public entrypoint for lock policy flags.

Practical notes

• Prefer tracing from CLI/test entry points into analysis/codegen crates before changing internals.
• Treat diagnostics and tests as part of the contract, not optional implementation details.
• If behavior changes, update this article and add/adjust tests in compiler/crates/beskid_tests or compiler/crates/beskid_e2e_tests.