Roadmap search

Versions, deliverables, workstreams, tasks, and pages

Beskid

Jump to a Beskid service

Dependency workspace and lockfile - Flow and algorithm

articleStandard

src/content/docs/platform-spec/compiler/build-pipeline/dependency-workspace/flow-and-algorithm.mdx

import SpecArticleChrome from '@beskid/beskid-ui/platform-spec/SpecArticleChrome.astro';

<SpecArticleChrome />
  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.