clarify

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

clarify — Architectural Deliberation Engine

clarify — 架构审议引擎

Domain Rubric

领域规则

1. Deliberation Dimensions

1. 审议维度

Evaluate proposals against 5 core architectural dimensions:

Data Contracts & Schemas: Boundaries, serialization, entity models, and migration compatibility.
State & Lifecycle: Source of truth, mutation paths, concurrency, and persistence.
Failure Modes & Resilience: Error boundaries, partial failure, fallback strategies, and recovery.
System Boundaries: Service responsibilities, dependency blast radius, and external integrations.
Non-Functional Guardrails: Latency, throughput limits, scalability constraints, and security.

根据5个核心架构维度评估提案：

数据契约与模式：边界、序列化、实体模型和迁移兼容性。
状态与生命周期：真实来源、变更路径、并发和持久化。
故障模式与韧性：错误边界、部分故障、回退策略和恢复。
系统边界：服务职责、依赖爆炸半径和外部集成。
非功能性护栏：延迟、吞吐量限制、可扩展性约束和安全。

2. Traversal & Deliberation Guardrails

2. 遍历与审议护栏

Scope Discipline: Confine inquiry strictly to high-impact architectural decisions, failure modes, and system invariants; forbid syntax bikeshedding or micro-optimizations.
Orthogonal Batching vs. Causal Sequencing:
- Orthogonal (Independent): Batch 1–5 independent questions in a single turn to eliminate conversational round-trip latency.
- Causal (Branching): Isolate branching decisions into strictly one question per turn when downstream options depend directly on the chosen path.
Mandatory Recommendation & Fast-Path: Pair every question with an authoritative technical recommendation and rationale. Support batch fast-path approval (e.g., "accept recommendations" or "approved except Q<N>: [Option]").
Root-First Traversal & Pruning: Resolve highest-impact branching points first; prune obsolete dependent questions immediately upon user response.
Autonomous Convergence: Continue probing until high-impact tensions converge or user prompts to conclude; forbid arbitrary question caps.
Convention Pruning: Adopt standard idioms without prompting when choices have zero cross-module impact.

范围纪律：严格将探究限制在高影响的架构决策、故障模式和系统不变量上；禁止语法争论或微优化。
正交批处理 vs. 因果排序：
- 正交（独立）：在一轮中批量提出1-5个独立问题，以消除对话往返延迟。
- 因果（分支）：当下游选项直接依赖于所选路径时，将分支决策隔离为每轮仅一个问题。
强制建议与快速路径：每个问题都附上权威技术建议和理由。支持批量快速路径批准（例如，“接受建议”或“除Q<N>外均批准：[选项]”）。
根优先遍历与剪枝：先解决影响最大的分支点；用户响应后立即剪除过时的依赖问题。
自主收敛：持续探究，直到高影响紧张关系收敛或用户提示结束；禁止任意设置问题数量上限。
约定剪枝：当选择对跨模块影响为零时，无需提示即可采用标准惯例。

3. Canonical Question Payload Format

3. 标准问题载荷格式

text

undefined

text

undefined

Q<N>: <Architectural Dimension>

Q<N>：<架构维度>

Bottleneck: <Single-sentence technical tension or edge-case risk>

• [A] <Option Title> ── Trade-off: <Advantage> vs. <Disadvantage> • [B] <Option Title> ── Trade-off: <Advantage> vs. <Disadvantage> • [C] <Option Title> ── Trade-off: <Advantage> vs. <Disadvantage>

Recommendation: [Option] because <Single-sentence technical rationale>

undefined

瓶颈：<单句技术紧张关系或边缘情况风险>

• [A] <选项标题> —— 权衡：<优势> vs. <劣势> • [B] <选项标题> —— 权衡：<优势> vs. <劣势> • [C] <选项标题> —— 权衡：<优势> vs. <劣势>

建议：[选项] 因为 <单句技术理由>

undefined

Canonical Output Contract

标准输出契约

markdown

undefined

markdown

undefined

Architectural Decision Dossier: <Scope / System Slug>

架构决策档案：<范围 / 系统标识>

1. Scope & Core Constraints

1. 范围与核心约束

Target Boundary: <Primary subsystem, domain, or integration boundary>
Core Dilemma: <Primary architectural tension or trade-off resolved>
Convergence: <Settled questions: Q1..QN>

目标边界：<主要子系统、领域或集成边界>
核心困境：<已解决的主要架构紧张关系或权衡>
收敛情况：<已解决问题：Q1..QN>

2. Settled Decisions

2. 已定决策

[Q1] <Architectural Dimension> ── <Chosen Option>

[Q1] <架构维度> —— <所选选项>

Bottleneck: <Operational tension, failure risk, or contract ambiguity addressed>
Rationale & Trade-off: <Core benefit gained> vs. <accepted systemic cost/complexity>
Enforced Invariant: <Concrete non-negotiable rule, contract constraint, or boundary guardrail>

瓶颈：<已解决的运营紧张关系、故障风险或契约歧义>
理由与权衡：<获得的核心收益> vs. <接受的系统性成本/复杂性>
强制不变量：<具体不可协商规则、契约约束或边界护栏>

[Q2] <Architectural Dimension> ── <Chosen Option>

[Q2] <架构维度> —— <所选选项>

Bottleneck: <Operational tension, failure risk, or contract ambiguity addressed>
Rationale & Trade-off: <Core benefit gained> vs. <accepted systemic cost/complexity>
Enforced Invariant: <Concrete non-negotiable rule, contract constraint, or boundary guardrail>

瓶颈：<已解决的运营紧张关系、故障风险或契约歧义>
理由与权衡：<获得的核心收益> vs. <接受的系统性成本/复杂性>
强制不变量：<具体不可协商规则、契约约束或边界护栏>

3. Blast Radius & Downstream Routing

3. 爆炸半径与下游路由

Impacted Subsystems:
```
<Component A>
```
,
```
<Component B>
```
Banned Anti-Patterns: <Explicitly forbidden workarounds or failure-prone designs>
Next Step: Route to
```
/changeset
```
for blast-radius planning and execution staging.

undefined

受影响子系统：
```
<组件A>
```
、
```
<组件B>
```
禁止的反模式：<明确禁止的变通方法或易故障设计>
下一步：路由到
```
/changeset
```
进行爆炸半径规划和执行分阶段。

undefined

Execution Protocol

执行协议

Phase 1: Surface & Gap Ingestion

阶段 1：表面与差距摄入

Inspect proposal and authoritative contracts (via
```
/ssot
```
).
If requirements conflict with established specifications or ADRs: halt immediately, cite contradiction pointers, and deliberate resolution.
If zero architectural ambiguities exist, short-circuit directly to Phase 3; otherwise proceed to Phase 2.

检查提案和权威契约（通过
```
/ssot
```
）。
如果需求与既定规范或 ADR 冲突：立即停止，指出冲突位置，并审议解决方案。
如果不存在架构歧义，直接短路到阶段 3；否则进入阶段 2。

Phase 2: Deliberation Interview

阶段 2：审议访谈

Partition unresolved dilemmas: batch orthogonal questions (max 5) or sequence causal branching decisions (1 per turn), each adhering to Canonical Question Payload Format with recommendation.
Present payload and halt turn immediately to await user response.
Ingest response (supporting fast-path approval), prune settled branches, and evaluate remaining ambiguities.
Repeat until critical architectural vectors converge or user prompts to proceed, then advance to Phase 3.

划分未解决的困境：批量提出正交问题（最多5个）或对因果分支决策进行排序（每轮1个），每个问题均遵循包含建议的标准问题载荷格式。
展示载荷并立即停止回合，等待用户响应。
摄入响应（支持快速路径批准），剪除已解决的分支，并评估剩余歧义。
重复直到关键架构向量收敛或用户提示继续，然后进入阶段 3。

Phase 3: Decision Dossier Synthesis

阶段 3：决策档案综合

Compile settled decisions into the Canonical Output Contract.
Deliver the completed
```
Architectural Decision Dossier
```
and halt turn immediately. Route downstream to
```
/changeset
```
.

将已定决策编译为标准输出契约。
交付完整的
```
架构决策档案
```
并立即停止回合。将下游路由到
```
/changeset
```
。