7a4ebe75ea399b8be1a40a0b30e9cdccef10f263
CI / commits (pull_request) Successful in 2m36s
CI / check (pull_request) Successful in 2m46s
CI / scan (pull_request) Successful in 2m56s
CI / a11y (pull_request) Successful in 3m23s
Docs site / build (pull_request) Successful in 3m27s
CI / perf (pull_request) Successful in 6m17s
ADR-0025 left several anchors as proposed-follow-up: - Principal.user.id / personId carry the Entra oid as a placeholder. - StubScopeResolver returns unrestricted for everyone. - @RequireScope's ScopableResource shape references an Etablissement / Delegation / Region chain that has no table. ADR-0026 specifies the portal-side data model that closes those stubs without dragging the upstream Pléiades / Acteurs+ syncs into scope: - Person golden record (stable identity; lazy-created on first sign-in in v1, source-stamped 'self-signin' for traceability). - User overlay (one-to-zero-or-one with Person; portal-only state like lastSignInAt rides here, not on the shared Person row). - UserScope migration confirming the ADR-0025 §"Sources of truth" shape. - Region / Delegation / Etablissement hierarchy with externally-meaningful codes (INSEE / dept / FINESS) as primary keys, matching scope literals' on-the-wire shape. Facet schemas (Salarié / Élu / Adhérent / Bénéficiaire) are deferred to ADR-0027 alongside the Pléiades and Acteurs+ sync that populates them - keeping the v1 migration small enough to land + roll back cleanly. Status: proposed. Implementation lands in two PRs once accepted: the schema + lazy provisioner, then the PrismaScopeResolver + admin-UI scope-seeding screen + test-tenant seed for the 19 personas. Index updated.
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.
Description
Languages
TypeScript
85.3%
JavaScript
5.4%
SCSS
4.3%
HTML
3.9%
Shell
0.8%
Other
0.3%