diff --git a/CODING_STANDARDS.md b/CODING_STANDARDS.md
index 97562f0..936c4dc 100644
--- a/CODING_STANDARDS.md
+++ b/CODING_STANDARDS.md
@@ -20,6 +20,31 @@ Paths are relative to `packages/api/`.
 - Change the schema with a numbered migration, following the recipe in `src/db/README.md`, and refresh `initial_schema.sql` to match. Keep DDL out of the connection code (`src/db/open.ts`, `src/db/client.ts`), routes, and `src/lib/`. The schema-evolution modules in `src/db/` (`migration-runner.ts`, `migration-preflight.ts`, `legacy-baseline.ts`, `apply-initial-schema.ts`) run DDL as part of evolution, and tests may create tables inline to build a legacy or partial database, as `src/db/__tests__/client.test.ts` and `src/lib/subjects/__tests__/subject-read.test.ts` do.
 - Open a database through `openOperationalDatabase`, which runs schema evolution. Open the file directly only when the code must not migrate it, and say why in a comment. For example, `src/scripts/check-integrity.ts` opens a backup with `new Database(path, { readonly: true })` so that checking it leaves it unchanged, and `src/db/__tests__/initial-schema-snapshot.test.ts` applies `initial_schema.sql` alone so that pending migrations can't hide a stale snapshot.
 
+### Domain modules
+
+- In a new write path, create Specimens and Containers with `registerSpecimens` from `src/lib/specimen-registration/` (ADR 0010). Bulk combined import, `/subjects/with-specimens` and `/specimens/bulk` have migrated. The paths in ADR 0010's later slices still create the Specimen themselves and add each Container through `createContainerForSpecimen` from `src/lib/container-creation.ts`, a wrapper over `registerSpecimens` that reports only the first error: `POST /specimens` and `POST /specimens/:id/containers` (`src/routes/specimens.ts`), derivations and the derivation CSV (`src/lib/derivations.ts`, `src/lib/derivations-csv.ts`), and control batches (`src/lib/controls/batch-with-specimens.ts`). Call `createContainerForSpecimen` only from those paths.
+- In a new write path, validate a registration with `checkSpecimenRegistration`, or wrap the whole write in `withRolledBackTransaction` when the caller writes its own records first (ADR 0010).
+- Validate an inbound container with a `@sampledb/contract` schema (`containerWriteInputSchema`, `bulkCombinedContainerSchema` or `optionalContainerInputSchema`), not an endpoint-specific container Zod schema (ADR 0006).
+- Map a CSV row to `ContainerWriteInput` with `csvRowToContainerWriteInput` from `@sampledb/contract` (ADR 0006). The web bulk import and control-batch CSVs still map through `flatBulkContainerToWriteInput` and `flatControlBatchContainerToWriteInput` in `packages/web/src/lib/`.
+- In a `ContainerWriteInput`, place a paper container on a `collection` of type `sheet`, not on a box or bag `collection` with a sibling `sheetName` (ADR 0006).
+- Accept an inbound container field only under its `ContainerWriteInput` name; map no alias for a name ADR 0006 removed (`type`, `containerBarcode`, flat `collectionName`, `collectionType`, `collectionLocationId`, `sheetName`, `sheetParentType`, `sheetParentName`). A schema may reject a removed name with a message naming its replacement, as `src/lib/controls/batch-schemas.ts`, `src/lib/derivation-schemas.ts` and `packages/contract/src/bulk-combined.ts` do.
+- Resolve a Specimen's Source with `resolveSpecimenSource` or `resolveSpecimenSources` from `src/lib/specimens/provenance.ts` (ADR 0007).
+- Return the full `SpecimenSource` shape to every caller, not a per-endpoint subset (ADR 0007).
+- Load a Container's read view (placement, identity, Tags, unit, location, Specimen, Source) with `loadContainerReadViews` or `loadContainerReadViewsByIds` from `src/lib/container-read-view.ts`, not with per-endpoint queries (ADR 0009).
+- Map the read view to its read path's type: `EnrichedContainerApi` for list, derivations and PATCH, `EnrichedStorageContainer` for collection detail, and CSV row fields for Container export (ADR 0009).
+
+### Routes
+
+- In new or changed route code, report an error by throwing a typed error from `src/lib/error-handler.ts` or returning `handleRouteError(error, c)`, not with `return c.json({ error }, 4xx)` (ADR 0004).
+- Throw `RouteError` from `src/lib/error-handler.ts` when the client-visible error body must stay the same, as export's `"Failed to export …"` responses do (ADR 0004).
+- Throw `ExpectedNotFoundError` for a 404 caused by user input, such as an export preflight miss or a user-supplied lookup, and `NotFoundError` for a missing resource on a direct GET or a stale link (ADR 0004).
+- Write no route-level `catch` block that calls `console.error`; return `handleRouteError(error, c)` from it instead (ADR 0004).
+- Write structured stdout (request lines, diagnostics) with `logDebug`, `logInfo`, `logWarn` or `logError` from `src/lib/observability.ts`, and persist a failure to the `error_logs` table with `src/lib/error-logger.ts`; use each module only for its own sink (ADR 0004). Both export `logError`, so import the observability one as `logObservabilityError`, as `src/lib/error-handler.ts` does.
+- Use plain `console.*` only for human-readable bootstrap, migration and script output: the startup lines in `src/index.ts`, the open and schema-evolution modules in `src/db/`, `src/scripts/`, and the CLI entry of `src/lib/demo-seed.ts` (ADR 0004). In new or changed request-time code, use `observability.ts`. Two request-time uses predate this rule: the `console.warn` in `logTemplateError` in `src/routes/qpcr-experiments.ts`, and the seeding progress lines in `POST /setup/initialize` in `src/routes/setup.ts`.
+- In a new or changed route handler, do not spread a Drizzle row into a `c.json` payload (ADR 0005). `...newSpecimen` in `src/routes/specimens.ts`, `...locationRecord` in `src/routes/locations.ts` and `...subject` in `GET /studies/:id/subjects` (`src/routes/studies.ts`) predate this rule.
+- Map a response that has a schema in `@sampledb/contract/wire` (containers today) to that wire DTO before `c.json` (ADR 0005).
+- Leave null omission to `omitOnWireMiddleware`: do not call `toWireJson()` in a route handler (ADR 0005).
+
 ### API tests
 
 - Give each test its own database from `setupTestDatabase()`, and close it with `cleanupTestDatabase()` in `afterEach`.
@@ -33,6 +58,15 @@ Paths are relative to `packages/api/`.
 Paths are relative to `packages/web/`.
 
 - Call the API through its domain module, `src/lib/api/<domain>`. Its methods resolve to the response body, so read `res.study`. Reference-data `list()` helpers are the exception: their body is `{ data, meta? }` (ADR 0002).
+- Read a setting with `settingsApi.getValue(key)` or `settingsApi.get(key).value`, never `api.get` on `/settings/:key` (ADR 0002).
+- Write a setting with `settingsApi.putValue`, `settingsApi.update`, or the bulk wrappers `exportConfigurationsApi.update`, `scannerConfigurationsApi.update` and `tableViewConfigurationsApi.update`, never `api.put` on `/settings/:key` (ADR 0002).
+- Parse a container response with the wire schemas from `@sampledb/contract/wire`, as `src/lib/api/parse-response.ts` does (ADR 0005). In a field you add to those schemas, mark an unset value `.optional()`, not `.nullish()` or `.nullable().optional()`. The existing `.nullable().optional()` fields in `packages/contract/src/wire/container-wire.ts` predate this rule, and parsers of other responses, such as `parseSettingsEnvelope`, are out of its scope.
+- On a screen ADR 0001 lists as migrated, show a query's read error inline with `PageError` or `SectionMessage` from `src/ui/`, not a toast (ADR 0001). Show a mutation's error with a toast, or with the inline mutation banner where the screen already has one. Workflow local state (CSV parse, server validate, export and import submits, wizard review and submit) keeps its inline or toast errors.
+- In new code, send a mutation that changes queried data through a domain hook, such as `useCreateStudy`, that invalidates the queries it changes, including `dashboardKeys` when it changes dashboard data (ADR 0001 says "should"). Two kinds of call stay direct: workflow submit and resolve calls, which keep local state (ADR 0001's workflow write paths, ADR 0008), and settings writes through `settingsApi` and the `*ConfigurationsApi` wrappers in the settings forms and managers under `src/components/`. Direct `*Api` mutations on CRUD screens predate this rule, among them `Locations.tsx`, `QpcrExperimentDetail.tsx`, `StudyDetail.tsx`, `ControlBatchDetail.tsx`, `AdminUsers.tsx`, `SubjectForm.tsx` and `ControlDefinitionForm.tsx`.
+- Put new Scan move behaviour in the `src/lib/scan-move/` core with plain-data unit tests, not in `ContainerMoveMicronix.tsx` or `ContainerMoveCryovial.tsx` (ADR 0008). `ContainerMovePapers.tsx` (interactive paper move) and `CollectionMove.tsx` (moving a Collection to a new Location) are not Scan moves, and this rule and the two below do not cover them.
+- Pass a Scan move effect a `ScanMoveGateway` instead of importing `collectionsApi` into it (ADR 0008). Only the production adapter, `src/lib/scan-move/gateway.ts`, imports `collectionsApi`.
+- Test Scan move effects with plain stub gateway functions, not `vi.mock` (ADR 0008).
+- Open a modal with `Modal` from `src/ui/`, not `ModalPortal` (ADR 0001). `CommandPalette` and `SearchModal` still use `ModalPortal` directly.
 
 ### Web tests