zero-tolerance-for-failure

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Zero-Tolerance for Failure

零故障容忍

When to Use

适用场景

Establish failure-prevention culture and operating norms for mission-critical systems
Apply HRO principles (preoccupation with failure, reluctance to simplify, sensitivity to operations, commitment to resilience, deference to expertise)
Design defense-in-depth, fail-safe, and fail-closed controls for software, infra, and OT
Define verification gates, independent checks, and release hold criteria
Architect redundancy, isolation, and graceful degradation with explicit failure modes
Facilitate pre-mortems, FMEA, and risk registers before high-stakes change
Author stop-the-line policy and escalation when quality or safety signals are ambiguous
Select and track prevention metrics (defect escape, near-miss, repeat incidents, gate bypass)
Coach leadership behaviors that counter normalization of deviance and blame theater
Brief engineering and ops on zero-defect aspiration vs error budgets for the right domain

为关键任务系统建立故障预防文化与运营规范
应用HRO原则（对故障保持警觉、拒绝简化操作、对运营状态敏感、致力于韧性、尊重专业能力）
为软件、基础设施及OT系统设计纵深防御、故障安全与故障关闭控制机制
定义验证门、独立检查环节及发布冻结标准
设计具备明确故障模式的冗余、隔离及优雅降级架构
在高风险变更前开展事前分析（pre-mortem）、FMEA并维护风险登记册
制定停线政策，在质量或安全信号不明确时启动升级流程
选择并跟踪预防类指标（缺陷逃逸、未遂事件、重复事件、验证门绕过情况）
指导领导层采取抵制违规常态化与追责表演的行为模式
向工程与运营团队讲解特定领域中零缺陷目标与错误预算的平衡

When NOT to Use

不适用场景

Own SLI/SLO definitions, error-budget policy, and burn-rate alerting →
```
site-reliability-engineer
```
Run live incident war room, SEV classification, and status communications →
```
incident-management-engineer
```
Design backup/immutability, RTO/RPO recovery, and ransomware restore architecture →
```
cyber-resilience-engineer
```
Enforce CI compile/lint/test gates without broader prevention program →
```
build-validator
```
Facilitate sprint ceremonies, backlog grooming, or team agile transformation → agile coaching skills
Issue HR warnings, performance plans, or legal disciplinary guidance → escalate to HR/legal
Own classified ATO/accreditation packages without operational excellence deliverables →
```
classified-cyber-security-senior-manager
```
(pair for cleared context)
Produce ADRs and integration patterns without failure-prevention lens →
```
senior-system-architecture
```
(pair for architecture)

负责SLI/SLO定义、错误预算政策及消耗率告警 →
```
site-reliability-engineer
```
负责实时事件作战室运行、SEV分级及状态沟通 →
```
incident-management-engineer
```
负责备份/不可变性设计、RTO/RPO恢复及勒索软件恢复架构 →
```
cyber-resilience-engineer
```
仅执行CI编译/代码检查/测试门控，未推行更广泛的预防项目 →
```
build-validator
```
负责冲刺仪式、待办事项梳理或团队敏捷转型 → 敏捷教练技能范畴
下达HR警告、绩效计划或法律纪律指导 → 升级至HR/法务部门处理
负责涉密ATO/认证包，但未结合卓越运营交付物 →
```
classified-cyber-security-senior-manager
```
（需结合涉密背景协作）
制定ADR及集成模式，但未融入故障预防视角 →
```
senior-system-architecture
```
（需与架构师协作）

Related skills

Need	Skill
SLOs, error budgets, reliability toil, capacity	`site-reliability-engineer`
Incident program, SEV, on-call, postmortems	`incident-management-engineer`
Recovery tiers, backup/immutability, resilience tests	`cyber-resilience-engineer`
Build/CI quality gates and merge validation	`build-validator`
Cleared program governance, inspection, escalation	`classified-cyber-security-senior-manager`
NFRs, architecture review, ADRs	`senior-system-architecture`
Enterprise BCM/DR program and tabletops	`bcm-disaster-recovery-specialist`
Active CSIRT containment and forensics	`incident-responder`

需求	技能
SLO、错误预算、可靠性运维工作、容量管理	`site-reliability-engineer`
事件管理项目、SEV分级、值班制度、事后分析	`incident-management-engineer`
恢复层级、备份/不可变性、韧性测试	`cyber-resilience-engineer`
构建/CI质量门控与合并验证	`build-validator`
涉密项目治理、检查、升级流程	`classified-cyber-security-senior-manager`
非功能需求、架构评审、ADR	`senior-system-architecture`
企业BCM/DR项目与桌面演练	`bcm-disaster-recovery-specialist`
主动CSIRT遏制与取证	`incident-responder`

Core Workflows

核心工作流

1. Scope, limits, and charter

1. 范围、限制与章程

Clarify what “zero tolerance” means in context—aspiration, gates, and metrics—without perfectionism traps.

See
references/zero_tolerance_scope_and_limits.md
.

明确特定场景下“零容忍”的含义——包括目标、门控及指标——避免陷入完美主义陷阱。

参考
references/zero_tolerance_scope_and_limits.md
。

2. HRO principles and operating mindset

2. HRO原则与运营思维模式

Embed high-reliability organization behaviors in teams that face rare, catastrophic failure.

See
references/high_reliability_organization_principles.md
.

将高可靠性组织（HRO）的行为模式融入面临罕见灾难性故障的团队中。

参考
references/high_reliability_organization_principles.md
。

3. Prevention, verification, and gates

3. 预防、验证与门控

Layer independent checks, hold points, and evidence before irreversible change.

See
references/prevention_verification_and_gates.md
.

在不可逆转的变更前设置多层独立检查、冻结点及验证证据要求。

参考
references/prevention_verification_and_gates.md
。

4. Redundancy, degradation, and fail-safe design

4. 冗余、降级与故障安全设计

Specify failure modes, safe defaults, and degraded operation—not only happy path.

See
references/redundancy_degradation_and_fail_safe.md
.

明确故障模式、安全默认值及降级运行机制——而非仅考虑正常路径。

参考
references/redundancy_degradation_and_fail_safe.md
。

5. Pre-mortem, FMEA, and risk registers

5. 事前分析、FMEA与风险登记册

Surface latent failures before launch; maintain living risk and mitigation traceability.

See
references/pre_mortem_fmea_and_risk_registers.md
.

在上线前发现潜在故障；维护动态更新的风险及缓解措施可追溯记录。

参考
references/pre_mortem_fmea_and_risk_registers.md
。

6. Leadership, culture, and metrics

6. 领导力、文化与指标

Measure prevention; reinforce stop-the-line; reduce normalization of deviance.

See
references/leadership_culture_and_metrics.md
.

衡量预防效果；强化停线机制；减少违规常态化现象。

参考
references/leadership_culture_and_metrics.md
。

Outputs

交付物

Failure-prevention charter — scope, principles, RACI, interfaces with SRE/IR/QA
Gate catalog — hold points, owners, evidence required, bypass rules and audit trail
Design review pack — fail-safe/fail-closed decisions, degradation modes, verification plan
FMEA / pre-mortem record — failure modes, causes, controls, residual risk, owners
Stop-the-line policy — triggers, authority, duration, comms, and restart criteria
Metrics dashboard brief — defect escape, near-miss, repeat incidents, gate effectiveness
Leadership playbook — behaviors, rituals, and anti-patterns (learning vs blame)

故障预防章程 —— 范围、原则、RACI职责、与SRE/IR/QA的接口
门控目录 —— 冻结点、负责人、所需证据、绕过规则及审计追踪
设计评审包 —— 故障安全/故障关闭决策、降级模式、验证计划
FMEA/事前分析记录 —— 故障模式、原因、控制措施、剩余风险、负责人
停线政策 —— 触发条件、权限、持续时间、沟通机制及重启标准
指标仪表盘简报 —— 缺陷逃逸、未遂事件、重复事件、门控有效性
领导层手册 —— 行为规范、仪式及反模式（学习导向vs追责导向）

Principles

核心原则

Prevent over punish — optimize systems and norms; avoid blame theater and hidden workarounds
Fail closed by default — ambiguous safety or auth states deny; document explicit fail-open exceptions
Independent verification — separation between build, check, and approve for high-criticality change
Deference to expertise — elevate domain experts at the boundary; leaders ask, not override silently
Measure escapes and near-misses — lagging severity alone rewards luck; track what almost failed
Stop-the-line is a gift — halting bad change is success; normalize escalation without career penalty
Pair with peers — reliability math (SRE), incidents (IR program), recovery (resilience), builds (CI)

预防优先，而非惩罚 —— 优化系统与规范；避免追责表演及隐藏的变通操作
默认故障关闭 —— 安全或权限状态不明确时拒绝操作；明确记录故障开放的例外情况
独立验证 —— 高关键度变更需实现构建、检查与审批环节的分离
尊重专业能力 —— 在边界场景中提升领域专家的话语权；领导者应询问而非默默否决
追踪逃逸与未遂事件 —— 仅依赖滞后的严重程度指标会滋生侥幸心理；需追踪险些发生的故障
停线是一种赋能 —— 阻止不良变更就是成功；让升级流程常态化且无职业风险
与同行协作 —— 需与可靠性计算（SRE）、事件管理（IR项目）、恢复（韧性）、构建（CI）等领域的人员协作