Dependency workspace and lockfile - Flow and algorithm

Platform spec article

Dependency workspace and lockfile - Flow and algorithm

Back to Dependency workspace and lockfile ◎ 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 Dependency workspace and lockfile.

   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/build-pipeline/dependency-workspace/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 Dependency workspace and lockfile.

   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/

   Open full ADR page

3. 0003-primary-contract-choice Primary contract for Dependency workspace and lockfile Accepted

   This feature hub specifies how manifests become prepared dependency workspaces and how `Project.lock` is synchronized un

   Context

   This feature hub specifies how manifests become prepared dependency workspaces and how Project.lock is synchronized under --locked and --frozen.

   Decision

   The reference compiler must implement Dependency workspace and lockfile as documented in this feature hub and its article bundle.

   Consequences

   Changes require hub/ADR updates and verification anchor extensions.

   Verification anchors

   • compiler/crates/beskid_analysis/

   Open full ADR page

Articles

• Dependency workspace and lockfile - Contracts and edge cases Normative behavior for lock mismatch, missing registry artifacts, and policy flags. article Standard
• Dependency workspace and lockfile - Design model Data model for compile plans, prepared workspaces, lock records, and dependency source roots. article Standard
• Dependency workspace and lockfile - Examples Concrete examples for frozen and locked workflows with project dependencies. article Standard
• Dependency workspace and lockfile - FAQ and troubleshooting Operational troubleshooting for lockfile synchronization and dependency workspace preparation. article Standard
• Dependency workspace and lockfile - Flow and algorithm Workflow from compile-plan construction to workspace materialization and lockfile synchronization. article Standard
• Dependency workspace and lockfile - Verification and traceability Source anchors and test evidence for compile-plan and lockfile behavior. 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 · 0 SpecSection(s) · 1 H2 heading(s)

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

Related spec docs

• Feature
  Dependency workspace and lockfile

  Parent feature hub

• Feature
  Stage ordering and lowering

  Uses prepared source roots

1. Build compile plan from manifest graph.
2. Materialize dependency sources into workspace object directory.
3. Read and reconcile Project.lock against resolved dependencies.
4. Enforce locked/frozen policy.
5. Expose final materialized source root to compile commands.

This flow is implemented in project workflow services and reused by fetch/lock/tree command surfaces.