Primary contract for Workspace resolution contract
Platform spec ADR
Primary contract for Workspace resolution contract
Spec standingStandard
- 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).
Context
Section titled “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. Mod projects 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
Section titled “Decision”The reference compiler must implement Workspace resolution contract as documented in this feature hub and its article bundle.
Consequences
Section titled “Consequences”Changes require hub/ADR updates and verification anchor extensions.
Verification anchors
Section titled “Verification anchors”compiler/crates/beskid_analysis/