Status. Proposed design only. Nothing in this vault is DG client approval. No application, service or test has been executed; every scenario is Not executed. Fees and dates are open.

Code change checklist

Use for every implementation task. It extends SECURITY.md section 13; it does not replace it.

Before coding

• One task ID. Scenario IDs and gates it serves are named (Scenario-Inventory).
• Module identified; its note in Modules/ and the cited vault notes read.
• Each Qnn the behaviour depends on is resolved, or the dependent scenario is marked Blocked by Qnn (Decision-Gates).
• Existing code searched for the hook, service, model, endpoint or route you were about to add.
• Tests-first subset from the step note identified; at least one failing test written for the expected reason.

Before opening the PR

• Focused tests, then broader checks run; results reported as run or not run.
• Every read, mutation, search, count, export and job checks authorisation on the server.
• A cross-company denial test exists where access is involved.
• No private message body in logs, email or errors; no real data; no secrets.
• Idempotency key and outbox event handled where the command is repeatable or notifying.
• Accessibility considered for UI changes.
• Brain updated per Documentation-Synchronisation, or “no durable knowledge change” stated.
• PR lists scenarios and gates touched with their status; none is called Passed without a named integrated build and fixture.
• Vault evidence folders untouched.

Change history

Date	Change
2026-10-20	Created (bootstrap Phase 2)