extreme-lifecycle

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Extreme Lifecycle

极端生命周期

When to Use

适用场景

Govern end-to-end system lifecycle from concept through disposal for high-assurance workloads
Define lifecycle phases, entry/exit criteria, and gate reviews with required evidence
Maintain bidirectional traceability—requirements, design, build, test, deploy, ops, and retire
Control configuration baselines, approved changes, and tech refresh / obsolescence plans
Plan sustainment—spares, vendor support, patch posture, and end-of-life transitions
Interface with assurance, DevSecOps, and authorization without owning those roles
Author decommissioning and data disposition plans with verification and audit trail
Operate in regulated or classified contexts using generic, NDA-safe framing (no customer dumps)
Produce lifecycle registers, gate packets, baseline manifests, and retirement checklists

为高保障工作负载治理从概念到处置的端到端系统生命周期
定义生命周期阶段、进入/退出标准，以及附带所需证据的关卡评审
维护双向可追溯性——覆盖需求、设计、构建、测试、部署、运维和退役环节
管控配置基线、已批准变更，以及技术更新/过时管理计划
规划运维保障——备件、供应商支持、补丁状态和生命周期末期过渡
在不承担相关角色的前提下，与**保障、DevSecOps和授权（ATO）**团队对接
编写带有验证和审计轨迹的退役与数据处置计划
使用通用、符合NDA要求的框架在受监管或涉密环境中运作（不涉及客户敏感信息）
生成生命周期登记册、关卡资料包、基线清单和退役检查表

When NOT to Use

不适用场景

Run multi-team milestone RAID and steering status only →
```
technical-program-manager
```
Establish HRO mindset, stop-the-line, and defect-escape prevention culture →
```
zero-tolerance-for-failure
```
Classify criticality tiers, RTO/RPO, and blast-radius architecture without full lifecycle →
```
mission-critical
```
Own cleared DevSecOps pipeline, build standards, and release trains only →
```
classified-software-devsecops-engineer
```
Prove correctness with formal methods, models, or certification evidence →
```
software-assurance-formal-methods-specialist
```
Automate SOC/ISO audit controls and continuous compliance monitoring →
```
compliance-engineer
```
Pre-flight architecture or go/no-go on a single change without lifecycle baseline →
```
build-validator
```
Own enterprise infrastructure portfolio, capex, and DC strategy →
```
vp-of-infrastructure
```

仅负责跨团队里程碑RAID和指导委员会状态汇报 →
```
technical-program-manager
```
仅建立HRO思维模式、停线机制和缺陷逃逸预防文化 →
```
zero-tolerance-for-failure
```
仅划分关键等级、RTO/RPO和影响范围架构而不覆盖全生命周期 →
```
mission-critical
```
仅负责涉密DevSecOps流水线、构建标准和发布列车 →
```
classified-software-devsecops-engineer
```
仅使用形式化方法、模型或认证证据证明正确性 →
```
software-assurance-formal-methods-specialist
```
仅自动化SOC/ISO审计控制和持续合规监控 →
```
compliance-engineer
```
仅在无生命周期基线的前提下对单一变更进行预飞架构检查或放行/否决决策 →
```
build-validator
```
仅负责企业基础设施组合、资本支出和数据中心战略 →
```
vp-of-infrastructure
```

Related skills

Need	Skill
Criticality tiering, objectives, release governance by tier	`mission-critical`
Failure-prevention culture, verification gates, FMEA	`zero-tolerance-for-failure`
Program milestones, dependencies, launch readiness	`technical-program-manager`
Cleared build/release and DevSecOps pipeline	`classified-software-devsecops-engineer`
Formal assurance, proofs, and certification packages	`software-assurance-formal-methods-specialist`
Audit evidence pipelines and control automation	`compliance-engineer`
Plan/design validation before execution	`build-validator`
Infrastructure portfolio and capex	`vp-of-infrastructure`
Secure SDLC, CI gates, SBOM	`devsecops`
Recovery architecture and restore evidence	`cyber-resilience-engineer`
BCM program and enterprise DR	`bcm-disaster-recovery-specialist`

需求	技能
关键等级划分、目标、按等级进行发布治理	`mission-critical`
故障预防文化、验证关卡、FMEA	`zero-tolerance-for-failure`
项目里程碑、依赖关系、上线就绪状态	`technical-program-manager`
涉密构建/发布和DevSecOps流水线	`classified-software-devsecops-engineer`
形式化保障、证明和认证包	`software-assurance-formal-methods-specialist`
审计证据流水线和控制自动化	`compliance-engineer`
执行前的规划/设计验证	`build-validator`
基础设施组合和资本支出	`vp-of-infrastructure`
安全SDLC、CI关卡、SBOM	`devsecops`
恢复架构和恢复证据	`cyber-resilience-engineer`
BCM项目和企业灾难恢复	`bcm-disaster-recovery-specialist`

Core Workflows

核心工作流

1. Scope and lifecycle charter

1. 范围与生命周期章程

Define system boundary, assurance level, regulatory/classified interfaces, and lifecycle authority.

See
references/extreme_lifecycle_scope.md
.

定义系统边界、保障等级、监管/涉密接口和生命周期权限。

详见
references/extreme_lifecycle_scope.md
。

2. Phases and gates

2. 阶段与关卡

Map concept → design → build → verify → deploy → operate → sustain → dispose with gate criteria.

See
references/lifecycle_phases_and_gates.md
.

映射从概念→设计→构建→验证→部署→运维→保障→处置的流程，并设定关卡标准。

详见
references/lifecycle_phases_and_gates.md
。

3. Traceability and evidence

3. 可追溯性与证据

Link artifacts across phases; define evidence types, retention, and independence requirements.

See
references/traceability_and_evidence.md
.

关联各阶段的工件；定义证据类型、保留要求和独立性要求。

详见
references/traceability_and_evidence.md
。

4. Operate, sustain, and obsolescence

4. 运维、保障与过时管理

Run sustainment reviews, tech refresh, vendor EOL, and operational baseline drift control.

See
references/operate_sustain_and_obsolescence.md
.

开展运维保障评审、技术更新、供应商生命周期末期管理，以及运营基线漂移控制。

详见
references/operate_sustain_and_obsolescence.md
。

5. Change, baseline, and retirement

5. 变更、基线与退役

Manage baselines, approved deltas, decommissioning, and data disposition with verification.

See
references/change_baseline_and_retirement.md
.

管理基线、已批准变更、退役流程，以及带有验证机制的数据处置。

详见
references/change_baseline_and_retirement.md
。

6. Stakeholders and assurance interfaces

6. 利益相关方与保障接口

Coordinate owners, ISSO/ATO consumers, assurance, and DevSecOps without owning their deliverables.

See
references/stakeholders_and_assurance_interfaces.md
.

协调所有者、ISSO/ATO需求方、保障团队和DevSecOps团队，无需负责他们的交付物。

详见
references/stakeholders_and_assurance_interfaces.md
。

Outputs

输出成果

Lifecycle charter — scope, phases, RACI, assurance tier, review cadence
Gate catalog — phase × gate → criteria, evidence, approvers, waiver rules
Traceability matrix — requirement/design/test/deploy/ops links with gap flags
Configuration baseline manifest — versions, hashes, environments, approval record
Obsolescence and tech-refresh plan — EOL dates, mitigations, funding hooks
Sustainment review record — support posture, patch debt, spares, drill outcomes
Decommissioning package — shutdown sequence, data disposition, evidence of destruction/archival

生命周期章程 —— 范围、阶段、RACI矩阵、保障等级、评审节奏
关卡目录 —— 阶段×关卡→标准、证据、审批人、豁免规则
可追溯性矩阵 —— 需求/设计/测试/部署/运维的关联关系及缺口标记
配置基线清单 —— 版本、哈希值、环境、审批记录
过时管理与技术更新计划 —— 生命周期末期日期、缓解措施、资金挂钩方案
运维保障评审记录 —— 支持状态、补丁债务、备件、演练结果
退役包 —— 停机序列、数据处置、销毁/归档证据

Principles

原则

Lifecycle before backlog — phase gates and baselines drive priority; do not substitute sprint velocity
Evidence is the product of governance — undocumented approval is not control
Trace forward and backward — every production artifact links to intent and verification
Baselines are contracts — change without baseline update is unauthorized state
Retire deliberately — disposal and data disposition are phases, not tickets
Stay in lane — interface with assurance, ATO, and DevSecOps; do not impersonate ISSO or auditor
NDA-safe by default — generic regulated/classified patterns; no counterparty-specific dumps

先生命周期，后待办事项 —— 阶段关卡和基线驱动优先级；不可用冲刺速度替代
证据是治理的产物 —— 未记录的审批不构成管控
双向追溯 —— 每个生产工件都关联到意图和验证环节
基线即合同 —— 未更新基线的变更属于未授权状态
审慎退役 —— 处置和数据处置是正式阶段，而非简单工单
各司其职 —— 与保障、ATO和DevSecOps团队对接；不要冒充ISSO或审计人员
默认符合NDA要求 —— 使用通用的受监管/涉密模式；不泄露特定合作方的敏感信息