Decision records
Significant decisions are recorded as short architecture decision records (ADRs) in
docs/adr. Each one states the context, the decision and
its consequences. A new decision that changes an old one gets a new record, and the old one is marked as superseded.
| ADR | Decision |
|---|---|
| 0001 | Pseudonymise user IDs in-process with rotating, destroyed salts |
| 0002 | Audit mode is a two-sided, encrypted, time-limited opt-in |
| 0003 | PostgreSQL by default, partitioned, no extensions |
| 0004 | Wire-format versioning: additive within a major |
| 0005 | Pin TypeScript to 6.0.x |
| 0006 | Gateway intents re-verified against Discord’s docs |
| 0007 | Changes to the spec’s reference code during M0 |
| 0008 | npm releases stay switched off until trusted publishing is proven |
| 0009 | Never read or cancel shared REST response bodies |
| 0010 | Collector and dashboard choices made during M1 |
| 0011 | Privacy, audit and admin choices made during M2 |
| 0012 | Run embedded mode on PGlite, not SQLite |
| 0013 | Choices made during M3 and M4 |
| 0014 | Pre-release quality and hardening pass |
| 0015 | Reports in Discord, and what identified mode may collect |
| 0016 | Corrections from simulated installs |
| 0017 | Version 1.0 and what it promises |
| 0018 | Record message (prefix) commands the bot reports |
| 0019 | Copy events into the owner’s own database through sinks |
To propose a decision, copy
0000-template.md to the next number and
open a pull request.