How to read these docs

Status: slice 34 · October 2026.

This site is the architecture source of trust for Locus. Its pages are deep references, not overviews: most of them state exact routes, permissions, status codes, env keys, entity names, and failure modes taken from the code and the original technical documentation. Expect to look things up rather than skim.

If a page conflicts with the running code or IMPLEMENTATION_TRACKER.md, the code and the tracker win. Where older technical documents (October 2026 technical presentation / documentation) disagree with newer slice 30–34 work, this site keeps the newer facts — for example the platform legal vault, Watchtower, the separate locus-ops app, FORCE RLS, and the ops cookie.

Pick a path

You want to…	Read
Understand the product in five minutes	What Locus is
See the system and its request paths	Architecture overview
Know who can do what	Trust boundaries (six-tier RBAC matrix, cookies)
Know where data lives	Data stores (entity inventory, RLS, object storage)
Change one tier	The service page: web, ops, backend, workers
Change a feature end to end	The matching flow: auth, dossier/OCR/analysis, market ingest, legal vault, copilot
Check a calculation	Engines
Explain a screen to someone	Workspace route map → zone pages → Full guide
Operate the platform	Ops overview → Regulatory admin, Access requests, Market ingest
Harden or audit	Security
Run or deploy	Deploy & environment, OCR override SOP
Look up a term	Glossary

Suggested reading order (full pass)

1. What Locus is — framing, two products, two document libraries.
2. Architecture overview — topology, ports, request paths.
3. Trust boundaries and Security — the rules everything else obeys.
4. Data stores — what the SoR holds.
5. The service page for the tier you are changing.
6. The flow that matches your feature.
7. Workspace UI or Ops pages when touching screens.
8. Deploy before shipping.

What lives where

Artifact	Role
This site (docs-site/)	How the platform works — services, flows, engines, security, ops, UI tours. Deep reference
IMPLEMENTATION_TRACKER.md (repo root)	Done / not-done checklist by slice; wins on status disputes
PRESENTATION.md / PITCH.md	French product / investor narrative
Each service .env.example	Authoritative env keys (summarized, not duplicated, here)
docs/, TECHNICAL_PRESENTATION.md, locus-web/TECHNICAL_DOCUMENTATION.md	Legacy entry points that now point here

Page types

Section	Style
Architecture, Security, Deploy, Ops	Reference: tables of routes, permissions, errors, env keys
Flows	Step-by-step data paths with diagrams
Engines	Formulas, thresholds, and where they run
Workspace UI	Page-by-page tours: purpose, behavior, terms, business value; full-guide is the long single-page version
Data	What is on disk and why (fixtures vs production vault)

Conventions

• Status line at the top of a page gives the slice and month it was verified against.
• Current vs Deferred callouts mark pilot leftovers (R1 staging smoke, attaching official foundational PDFs, live Watchtower polling).
• Code paths are relative to the monorepo root (locus-backend/…).
• Env keys use their runtime spelling; ASP.NET nested keys use __ in env (ConnectionStrings__DefaultConnection).
• SEEG / PAPN / Eneo / SNPC figures in UI tours and engine examples are test-reference walkthroughs. Fresh registered tenants start empty.
• The seeded ops account and demo data exist only when Seed:RunOnStartup=true and never belong in production.
• French UI strings (Brief du matin, Provisionner le tenant) are quoted as they appear on screen.