ehoandClaude Opus 4.8
a828e604d1
New phase from the 5-item analysis: linked showcase snippets + animations, runnable scaffolding generators (pages/wizards/context/SSP), dependency graph + declarative boundaries, PII hardening (branded Bsn VO + masked-value atom + persisted no-PII audit) doubling as a privacy showcase, and Vitest coverage. Goal: both a teaching showcase and a production starter template. Sequenced with priorities + dependencies in the README. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2.0 KiB
2.0 KiB
WP-38 — Dependency graph + declarative boundaries
Status: todo Phase: 8 — platform/DX/showcase Priority: P1
Why
Bounded-context + atomic-layer boundaries are enforced only by hand-duplicated
no-restricted-imports blocks in eslint.config.mjs — pass/fail, no graph, and brittle: the
new-context skill literally says "grep the config and copy a block", and herregistratie is
missing its explicit ban block (asymmetry). We want to see the dependencies AND enforce
them from one declarative source.
Decisions
- Step 1 — tool fork: dependency-cruiser (recommended: graph + CI rules on plain Angular) vs Sheriff (tag-based, DDD/atomic-native, weaker graph). Decide before building.
- Encode context + layer rules once (contexts
shared/auth/registratie/herregistratie/brief/beheer/ showcase; layersdomain/application/infrastructure/contracts/ui); fix the herregistratie gap. - Keep ESLint for the intra-file rules it does better (
domain↛@angular, ApiClient value-import confinement,no-explicit-any); migrate only the cross-module direction rules to the new tool. - Emit a graph the showcase/teaching can reuse (feeds WP-39).
Files
- New:
.dependency-cruiser.js(orsheriff.config.ts);npm run graph+ validate script. scripts/ci-local.sh+.github/workflows/ci.yml— adddepcruise --validate(non-optional).eslint.config.mjs— remove the migrated direction rules (keep the rest).- New doc
docs/reference/architecture/dependencies.md; embed the graph in a Foundations page. .claude/skills/new-context/SKILL.md— point at the single declarative source.
Acceptance criteria
- One declarative config expresses all allowed context/layer edges; herregistratie included.
npm run graphproduces an architecture graph (SVG/HTML); validate runs innpm run ci.- A deliberately-illegal import fails the validate step (proven, then reverted).
- No loss of enforcement vs the old ESLint blocks;
npm run cigreen.