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.
Documentation synchronisation
A code change is incomplete until the Brain is synchronised. This table says which note a change forces.
| Change | Update |
|---|---|
| New or changed endpoint, guard or error shape | Request-Pipeline and the owning Modules/ note |
| New table, column, constraint or index | Data-Architecture and the owning module note |
| New outbox event, retry or delivery behaviour | Outbox-and-Worker |
| Authentication, role, membership or session change | Authentication-and-Authorization, SECURITY.md |
| Isolation or denial behaviour | Company-Isolation, Company-Isolation-Scenarios |
| New port or adapter | Integration-Ports |
| New environment variable (name only) | Environment-Configuration |
| Build, CI or deploy change | Build-Test-and-Deployment, Local-Setup |
| Scenario evidence produced | Scenario-Inventory status, per Scenario-Evidence-Rules |
| Engineering choice with trade-offs | New ADR; update ADR-Index |
| A DG decision recorded by the owner | The evidence Qnn note (owner only), then Decision-Gates and TODOS.md |
| Any change to these notes | log |
If a change spans several modules, check Cross-Module-Impact-Matrix for the scenarios to re-run.
Change history
| Date | Change |
|---|---|
| 2026-10-20 | Created (bootstrap Phase 2) |