[P1] Enforce crate dependency boundaries in workspace #3

New Issue

joe · 2026-03-31T19:58:36-05:00

joe commented

2026-03-31 19:58:36 -05:00

Council finding: with the multi-crate workspace now established, explicit dependency rules should be enforced to prevent future cycles.

Desired boundary rules:

notcore is a leaf crate — depends on nothing in this workspace
notsecrets, nothooks, notfiles depend on notcore but NOT on each other
notstrap is the top-level orchestrator — may depend on all others

How to enforce:

Add cargo-deny rules or workspace [patch] guards
Document the dependency graph in CLAUDE.md or architecture docs
Consider a CI check that fails on unexpected cross-crate deps

Source: devloop council analysis 2026-03-31

Council finding: with the multi-crate workspace now established, explicit dependency rules should be enforced to prevent future cycles. **Desired boundary rules:** - `notcore` is a leaf crate — depends on nothing in this workspace - `notsecrets`, `nothooks`, `notfiles` depend on `notcore` but NOT on each other - `notstrap` is the top-level orchestrator — may depend on all others **How to enforce:** - Add `cargo-deny` rules or workspace `[patch]` guards - Document the dependency graph in CLAUDE.md or architecture docs - Consider a CI check that fails on unexpected cross-crate deps Source: devloop council analysis 2026-03-31

joe referenced this issue from a commit

2026-04-04 00:14:33 -05:00

fix: address security findings from devkit-review (#1–#7)

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: joe/notfiles#3