Blameless postmortems — what broke, why, and the guard that prevents recurrence.
Real bugs that hit prod, with root cause + structural fix + recurrence guard. Numbered FM-XXX. Blameless. The point is institutional memory — if a class of bug repeats, the entry says so.
Migrated
Section titled “Migrated”| FM | Title | Severity | Category | Status |
|---|---|---|---|---|
| 001 | Cross-Organization Cache Pollution | SEV-1 | Multi-tenancy data leaks | 🟢 Archived |
Pending migration
Section titled “Pending migration”FM-002 through FM-047 + FM-UI-001 still live in Confluence Engineering → Incidents. Migration in progress.
Bug classes that repeat (from Confluence audit)
Section titled “Bug classes that repeat (from Confluence audit)”| Class | Examples |
|---|---|
| Multi-tenancy data leaks | FM-001, FM-002, FM-012, FM-047 |
| Drizzle / migration silent failures | FM-004, FM-005, FM-020, FM-021, FM-024, FM-026, FM-030, FM-042 |
| Org / auth scope confusion | FM-014, FM-015, FM-022, FM-037, FM-045 |
| Silent context dropping | FM-010, FM-013, FM-036 |
| Brain document handling | FM-027, FM-028, FM-029, FM-031, FM-033 |
When opening a new FM, check whether the symptom matches one of these classes — the guard may already exist.