Dependency cycles reported at graph build
Platform spec ADR
Dependency cycles reported at graph build
Spec standingStandard
- Dependency graph and cycle policy - Contracts and edge cases States the normative guarantees and what happens at boundaries or failure edges.
- Dependency graph and cycle policy - Design model Explains the persistent concepts, entities, and boundaries this feature relies on.
- Dependency graph and cycle policy - Examples Gives concrete newcomer-friendly scenarios mapped to real compiler paths.
- Dependency graph and cycle policy - FAQ and troubleshooting Answers common operator and contributor questions with practical next checks.
- Dependency graph and cycle policy - Flow and algorithm Walks through runtime/order-of-operations behavior in the implementation.
- Dependency graph and cycle policy - Verification and traceability Shows how the team proves this feature works and where evidence lives.
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”Silent cycle handling broke workspace diagnostics parity.
Decision
Section titled “Decision”Directed cycles must be reported during graph build; Mod cycles must include mod id in the diagnostic path.
Consequences
Section titled “Consequences”Policy knobs (error, warn, permissive) select abort vs continue; default remains fail-closed for release builds.
Verification anchors
Section titled “Verification anchors”beskid_analysis::projects::graphcompiler/crates/beskid_tests/src/projects/corelib/layout.rs.