Tree and resolution

Informative guide. This Book page explains Beskid but does not define the standard. For normative requirements, use the Beskid Standard.

Resolution is not magic—it is a DAG walk with a lockfile receipt.

Build lifecycle (deterministic sketch)

1. Discover manifest (App.bproj or workspace member).
2. Resolve dependency DAG.
3. Sync Project.lock.
4. Materialize dependencies under obj/beskid.
5. Build dependencies before dependents.

accTitle: Dependency build order
accDescr: Dependency A is required by dependency B, and dependency B is required by the application target.
flowchart TD
  D1[Dep A Lib] --> D2[Dep B Lib]
  D2 --> APP[App target]

Text equivalent: Build dependency A before dependency B. Build dependency B before the application target.

Inspecting structure

• beskid tree on a .bd file shows AST shape (parser-level).
• Project graphs: use reference resolution and CLI project introspection flags documented on tree command where applicable to manifests.

When resolution fails, read the diagnostic first—path dependencies love typos (../Wrong).

Workspace members

Multi-project repos resolve members via Workspace.bws (chapter 06). Single-project repos stay ignorant and happy.

Failure modes

Symptom	Likely cause
Unsupported provider in graph	Active git dependency; current materialization supports path and registry sources
Missing entry	target.entry not under project.root
Cycle	Circular path dependencies between projects
Stale lock	Changed manifest without lock/fetch

Deep dive

• Project Resolution
• Project manifest contract

Next chapter

04. Where does this file even go?