Ultra Orchestration · Handbook / 白皮书

这是 Ultra Orchestration 的开源使用手册与白皮书页面，默认展示中文。

This is the open-source handbook and whitepaper page for Ultra Orchestration (English mode).

GitHub README

规范平面（OpenSpec）

Program → Milestone → Change → Slice

OpenSpec 负责长期规格真相、边界定义和状态核算。

规格权威

编排平面（Ultra）

Intake → Plan → Dispatch → Execute → Review → QA → Deliver → Retro

Ultra 负责执行状态机、质量门禁、审查回环和交付证据。

执行权威

Agent-Skills 协作逻辑

阶段	主要技能	职责
Intake	`clarify-and-intake`	将模糊需求归一化成结构化 intake。
Plan	`decision-complete-planner` + `spec-review`	形成可执行任务图和规格前置审查。
Dispatch	`dispatch-and-track`	派发工作包、控制 owned paths、更新执行状态。
Execute	`ultra-orchestrator`	按 slice 受限执行，实现最小变更闭环。
Review	`code-review` + `spec-review`	工程质量与规格一致性双审。
QA	`qa-verify`	行为验证、回归验证、验收证据。
Deliver/Retro	`deliver-and-retro`	交付摘要、风险说明、复盘沉淀。
跨阶段护栏	`risk-vetter` + `safety-guard` + `autoplan`	风险分级、安全约束、加速规划。
Bridge 层	`openspec-ultra-bridge`	同步 OpenSpec 与 Ultra 账本，推进 change/slice 状态一致。

Backstory / 引文

“在复杂 coding-agent 任务中，真正的瓶颈不是模型能力，而是工程纪律能否被稳定执行。”

最初方法以编排优先（orchestration-first）为核心。随着 spec-coding 趋势出现，我们观察到：仅靠对话上下文推进任务，会频繁出现状态漂移、隐性回归、写冲突与不可审计交付。

因此采用迭代演进：把 OpenSpec 植入到编排体系中，形成“规格平面 + 编排平面”双轨模型，确保每个变更都能在 Program/Milestone/Change/Slice 与执行阶段之间形成闭环证据。

历史背景保留，执行权威以 skills 为准

Specification Plane (OpenSpec)

Program → Milestone → Change → Slice

OpenSpec owns long-lived specification truth, scope boundaries, and progress accounting.

Spec authority

Execution Plane (Ultra)

Intake → Plan → Dispatch → Execute → Review → QA → Deliver → Retro

Ultra owns execution state, quality gates, review loops, and delivery evidence.

Execution authority

Agent-Skills Logic

Phase	Primary skills	Responsibility
Intake	`clarify-and-intake`	Normalize ambiguous requests into structured intake artifacts.
Plan	`decision-complete-planner` + `spec-review`	Create dependency-aware plans and pre-implementation spec checks.
Dispatch	`dispatch-and-track`	Assign work packages, enforce owned paths, and track execution state.
Execute	`ultra-orchestrator`	Implement bounded slices with explicit constraints.
Review	`code-review` + `spec-review`	Run engineering and specification consistency gates.
QA	`qa-verify`	Run behavior/regression validation and acceptance evidence checks.
Deliver/Retro	`deliver-and-retro`	Assemble delivery output and process retrospectives.
Cross-cutting safety	`risk-vetter` + `safety-guard` + `autoplan`	Risk classification, guardrails, and accelerated planning mode.
Bridge layer	`openspec-ultra-bridge`	Synchronize OpenSpec artifacts with Ultra execution artifacts.

Backstory / Quote

"In complex coding-agent delivery, the bottleneck is not only model capability, but whether engineering discipline can be executed consistently."

The framework started orchestration-first. As spec-coding matured, we observed recurring failures in chat-only workflows: state drift, hidden regressions, write conflicts, and poor auditability.

This drove an iterative upgrade: integrate OpenSpec into the orchestration stack and enforce a dual-plane model so every change is verifiable across both specification and execution ledgers.

Historical context retained; runtime authority remains in core skills

Ultra Orchestration · docs.html (default: 中文, switchable EN)