Workspace and lock contracts

Platform spec feature

Workspace and lock contracts

Back to Manifests and lockfiles ◎ Open in platform map

Spec standingStandard

Owner

Piotr Mikstacki pmikstacki@cybernomad.it

Submitter

Piotr Mikstacki pmikstacki@cybernomad.it

Current document

ADRs (2)

1. 0001-hub-authority Hub authority Accepted

   Hub authority

   Context

   Lock alignment.

   Decision

   Hub owns workspace and lock rules.

   Consequences

   CLI/IDE defer.

   Verification anchors

   resolution tests.

   Open full ADR page

2. 0002-lock-mutations-via-cli CLI lock mutations Accepted

   CLI lock mutations

   Context

   Resolver bypass risk.

   Decision

   fetch/lock must use CLI resolver.

   Consequences

   Matches VSC-0002.

   Verification anchors

   CLI integration.

   Open full ADR page

Articles

• Contracts and edge cases Workspace and lockfile guarantees for tooling operators. article Standard
• Design model Conceptual model for workspace manifests, lockfiles, and materialized dependency roots. article Standard
• Examples Workspace and lockfile examples for tooling workflows. article Standard
• FAQ and troubleshooting Workspace and lockfile troubleshooting for tooling users. article Standard
• Flow and algorithm Lock synchronization, fetch, and update flows for workspace tooling. article Standard
• Verification and traceability Tests and traceability for workspace and lock tooling contracts. 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 · 3 SpecSection(s) · 0 H2 heading(s)

Section id	Required	Found
what-this-feature-specifies	yes	yes
implementation-anchors	yes	yes

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

Related spec docs

• Area
  Manifests and lockfiles

  Parent area

• Feature
  Workspace and lock contracts (compiler)

  implements — lock materialization, layout invariants, resolution diagnostics

• Area
  Build pipeline

  Stage scheduling depends on stable dependency graph materialization

• Area
  Registry client

  Lock updates rely on registry metadata and fetch flows

What this feature specifies

Workspace and lock contracts defines one operational contract that a newcomer can follow end-to-end: first the model, then execution flow, then strict guarantees, concrete examples, and verification guidance.

Implementation anchors

• Lock/update commands in compiler/crates/beskid_cli/src/commands/
• Project and dependency resolution in compiler/crates/beskid_analysis/src/resolve/mod.rs
• Workspace tests in compiler/crates/beskid_tests/src/analysis/pipeline/core.rs
• Corelib package tests in compiler/crates/beskid_tests/src/projects/corelib/layout.rs

Decisions

No open decisions. D-TOOL-MAN-0001 (hub authority), 0002 (lock mutations via CLI)—see adr/ and the ADRs tab.

Articles

• Hub authorityHub authority
• Contracts and edge casesWorkspace and lockfile guarantees for tooling operators.
• Design modelConceptual model for workspace manifests, lockfiles, and materialized dependency roots.
• ExamplesWorkspace and lockfile examples for tooling workflows.
• FAQ and troubleshootingWorkspace and lockfile troubleshooting for tooling users.
• Flow and algorithmLock synchronization, fetch, and update flows for workspace tooling.
• Verification and traceabilityTests and traceability for workspace and lock tooling contracts.