通行证 · 这个房间做了什么
Why does the same outage keep recurring?
每一行都来自记录。这个页面上没有任何计算出来的内容，也没有任何修饰：分歧清单很短，说明房间达成了一致，而不是房间把分歧收拾掉了。
| 梳理的是 | 障碍 |
| 开启于 | 08 Sep 2026 |
| 回答者 | 30 人，分 2 个小组 · 参与者: 30 |
| 盲写 | 未记录 |
| 主张 | 写下 30 条，结构化 20 条 |
| 已认证的关联 | 20 |
| 这个问题上的房间 | 1 · 不计入共享地图 |
| 决定门槛 | 所投票数的 75% |
| 已封存 | 是，成员已被忘记 |
它的依据- The service map in the wiki is two years old
- One engineer knows how the payment path actually works
- Feature flags are never cleaned up, so nobody knows which paths are live
- The on-call rota has the same two people on it most weeks
- Rollbacks take longer than the outage they are meant to end
- Alerts fire so often that on-call mutes them
预计随之而来的在地图定下之后撰写。没有人对其投票。
- No production deploy after 14:00 on Fridays unless the on-call engineer agrees — 预期：the same cause stops coming back once fixing it is in the sprint — 到期：23 Jan 2027
房间会怎么做每项行动都对照每个根本原因进行判断，以所投票数的四分之三为准。
- No production deploy after 14:00 on Fridays unless the on-call engineer agrees
意见分裂： One engineer knows how the payment path actually works - Give the shared schema one named owner and a migration tool with rollback
减轻： One engineer knows how the payment path actually works - Reserve one engineer-week per sprint for post-mortem actions, first in the sprint, not last
不减轻任何根本原因
← 返回对话