L1
规划闭环
Planning Closure
触发：rewrite · migration · plan-before-coding
大型改造、迁移、项目级重构先做轻量分析 / 计划 / 进度包，再进入实现，不让高风险任务一上来就动手。
关键产物
- Planning Pack
- Phase Plan
- Progress Anchor
- pre-development playbook
Seven Closure Layers
从规划到交付的七层闭环协调
不只是"选谁来回答"，而是把复杂软件工作的七层闭环打通。每层都有明确的触发条件、核心机制和结构化产物，避免高风险任务直接动手、避免单轮建议无执行路径。
L2
路由闭环
Routing Closure
触发：multi-domain · fuzzy ideas · cross-stack
基于任务形态、风险、技术栈、Git/process 信号，在 lead / assistant / governance / process 四条轨道间路由，而不是角色堆砌。
关键产物
- Lead Agent Selection
- Workflow Bundle
- Intent Confirmation
- Resume Anchor
L3
交付闭环
Delivery Closure
触发：quick implementation · bugfix · narrow slice
窄功能和 bugfix 切片用 quick slice brief、持久项目上下文、delivery status、目标验证和自审，保证窄范围不漂移。
关键产物
- Quick Slice Brief
- Project Context
- Delivery Status
- Targeted Verification
L4
迭代闭环
Iteration Closure
触发：optimization · benchmark · repeated retry
优化循环保留 baseline、round memory、self-feedback，明确 keep / retry / rollback / stop / pivot / resume，不做无限自转。
关键产物
- Baseline Snapshot
- Round Memory
- Self-Feedback
- Decision Ledger
L5
发布闭环
Release Closure
触发：ship/hold decision · formal acceptance
发布不是一句"能不能发"，而是有 ship / hold 门禁、blocker 清单、修复入口；ship 必须由结构化 completion evidence 支撑。
关键产物
- Release Gate Result
- Completion Evidence
- Remediation Brief
- Next Iteration Entry
L6
演练闭环
Drill Closure
触发：offline verification · rollback drill
离线演练验证回滚、resume、release-gate bootstrap 路径确实跑得通，不依赖线上事故才暴露问题。
关键产物
- Loop Drill Report
- Rollback Verification
- Resume Path Audit
L7
Team Engine Lite 闭环
Team Engine Lite Closure
触发：code-facing · release-facing · Git remediation
Worker 负责产出，Verifier 负责验收，Lead 只能根据 DeliveryCycleReport 接受，不让同一个角色既当选手又当裁判。
关键产物
- Work Order
- Verification Report
- Remediation Patch
- Delivery Cycle Report