Sibling articles under this feature previously restated requirements in inconsistent forms.
Workspace resolution contract - FAQ and troubleshooting
Platform spec article
Workspace resolution contract - FAQ and troubleshooting
Spec standingStandard
-
This feature hub owns normative MUST/SHOULD contract text for Workspace resolution contract.
Context
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-resolution-contract/index.mdxarticle bundle under the same feature directory.
-
Platform-spec text supersedes informal crate comments for Workspace resolution contract.
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/
-
This feature hub explains how the compiler discovers `Project.proj`, builds a project graph, and hands resolved workspac
Context
This feature hub explains how the compiler discovers
Project.proj, builds a project graph, and hands resolved workspace inputs to compile and dependency commands.Modprojects are included in the graph like other project kinds; after resolution, the mod host registers them for event-driven orchestration per Project manifest contract and Compiler Mods.Decision
The reference compiler must implement Workspace resolution contract 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/
- Workspace resolution contract - Contracts and edge cases Normative guarantees and failure behavior for manifests, graph resolution, and root selection.
- Workspace resolution contract - Design model Actors, data model, and boundaries for project/workspace discovery in compiler services.
- Workspace resolution contract - Examples Practical examples of manifest graph resolution and target path selection.
- Workspace resolution contract - FAQ and troubleshooting Common newcomer questions for project graph resolution, manifests, and lock behavior.
- Workspace resolution contract - Flow and algorithm End-to-end algorithm from manifest discovery to resolved compile input.
- Workspace resolution contract - Verification and traceability Tests and source anchors used to validate project graph and workspace resolution behavior.
0 revisions (git unavailable at build; counts may be empty)
No commits recorded for this path.
Full tree: run pnpm verify:platform-spec-layout (writes src/generated/platform-spec-layout-report.json).
Why does the compiler ignore my workspace target?
Section titled “Why does the compiler ignore my workspace target?”Explicit file input overrides target inference; remove the explicit path to use manifest target resolution.
Why did a dependency warning not fail the command?
Section titled “Why did a dependency warning not fail the command?”The command may be using a warning-oriented unresolved dependency policy. Use a strict mode command or policy where available.
Why does lockfile behavior differ between commands?
Section titled “Why does lockfile behavior differ between commands?”--frozen and --locked are command-level options propagated into workspace preparation options.