Julien Gautier
07cb466d51
CI / commits (pull_request) Successful in 2m49s
CI / check (pull_request) Successful in 3m25s
CI / scan (pull_request) Successful in 3m37s
CI / a11y (pull_request) Successful in 3m25s
Docs site / build (pull_request) Successful in 3m32s
CI / perf (pull_request) Successful in 5m33s
ADR-0026 was reviewed; status flips proposed -> accepted with the two open questions closed: 1. Person dedup at first sign-in. v1 looks up by entraOid only; no email-based merging. Two distinct people genuinely can share an email, and silent auto-merge would corrupt the golden record. ADR-0027 introduces operator-confirmed reconciliation; v1 takes the safe-by-default posture. 2. Org-hierarchy seed placement. Region / Delegation / Etablissement codes ship inline in the Prisma migration as reference data — slow-moving, environment-agnostic, single atomic deploy. ADR-0027's Pléiades sync supersedes the inline seed when it ships. user_scopes for the 19 test personas stay in prisma/seed.ts (implementation PR 2) since those are test-tenant-specific data. Consequences section reworked to reflect the new dedup choice: the email-fragility Bad-because is removed; a new Bad-because documents the v1 cost (a self-signed-in Person + a later Pléiades-imported Person look like duplicates until ADR-0027's operator merge flow resolves them — observable, not silent). CLAUDE.md updated: - Roll-up bumped 0001 -> 0025 -> 0001 -> 0026. - New Architecture bullet for the portal-side data model. - Roadmap entry on @RequireScope Prisma resolver updated to reflect ADR-0026 (accepted) and the two-PR implementation phasing. Index row flipped to accepted.
Documentation index
This is the entry point to all project documentation. It is maintained automatically: any addition, rename, or removal of a .md file under docs/ must be reflected here in the same change.
Conventions
- Documentation is written in English.
- One topic per file. Group related files into a folder when there are three or more.
- Cross-reference with relative links so they keep working in GitHub, IDEs, and exported sites.
- For architectural decisions, do not add them here — they belong in decisions/ as MADR 4.0.0 ADRs.
Sections
Daily development
- development.md — repo layout, prerequisites, initial setup, daily commands, observability dev-loop (Jaeger UI, log ↔ trace correlation), dependency updates (Renovate), conventional commit cycle. Day-to-day reference for working on the project.
Architecture
- architecture.md — cross-cutting Mermaid diagrams: C4 system context, C4 containers, Nx module boundaries, CI/CD pipeline. Single-decision diagrams (auth sequence, ERD, etc.) live inline in their ADR.
Onboarding & environment
Setup guides for new contributors:
- setup/01-wsl-terminal-setup.md — modern WSL terminal (Zsh + Powerlevel10k + CLI tools)
- setup/02-dev-web-stack.md — Node via nvm, pnpm via corepack, Docker
- setup/03-angular-nx-monorepo.md — Angular + Nx monorepo bootstrap
Operations & runbooks
Empty — to be populated when we deploy.
Security, performance, accessibility
Empty — placeholders to be filled with rationale docs alongside their corresponding ADRs.