another step

server/CLAUDE.md

@@ -63,14 +63,21 @@ Server is required to start.
 
 ## Quality gates — run before declaring work done
 
-1. `dotnet build Baya.sln` — zero new warnings introduced.
+1. `dotnet build Baya.sln` — zero new warnings introduced. Unused `using`s, locals, parameters,
+   private fields, or members count as failures — delete them, don't suppress them
+   ([CONVENTIONS.md](CONVENTIONS.md) §2 "No unused code").
 2. `dotnet test Baya.sln` — all tests pass.
 3. Read your own diff as if reviewing a PR: would a senior engineer approve it without comment?
+4. If the change alters the architecture, update the **Project map** below in the same change
+   (see "Keeping the Project map current").
 
 ---
 
 ## Project map
 
+This tree is the **canonical description of the server's architecture** — the authoritative list of
+projects/assemblies, Clean-Architecture layers, and cross-layer dependencies.
+
 ```
 src/
 ├── Core/
@@ -95,6 +102,12 @@ src/
 Domain. Infrastructure and API implement/consume Application contracts. Never make Domain or
 Application reference Infrastructure or the API — this is a hard rule.
 
+**Keeping the Project map current.** When a change touches the architecture — adds, removes, or
+renames a project/assembly, a Clean-Architecture layer, or a major folder, or changes a cross-layer
+dependency — you **must** update this Project map (and the dependency rule above, if affected) in the
+**same** change. This is the server-specific form of the root "Keep docs honest" rule: the map is
+only canonical if it stays accurate.
+
 ---
 
 ## Startup wiring
@@ -179,6 +192,8 @@ Full rules in [CONVENTIONS.md](CONVENTIONS.md). The essentials:
 - `async`/`await` all the way; pass `CancellationToken` through every async call; never `.Result`/`.Wait()`/`async void`.
 - Mapster for mapping; FluentValidation for validation (validate at the boundary).
 - Package versions live **only** in `Directory.Packages.props` — never `Version=` in a `.csproj`.
+- No unused code (usings, locals, parameters, private fields/members) and no *what*-comments — explain *why*, prefer self-documenting names (§2).
+- Architecture changes (a project/layer/major folder or a cross-layer dependency) must update the **Project map** in the same change.
 - The `Baya.*` namespace is project naming — do not rename without explicit instruction.
 
 ---