design-studio

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Design Studio

Design Studio is a portable design-engineering kernel. Lifecycle, source boundaries, routing, evidence and acceptance stay small here; specialist methods load only when signals match.

Design Studio 是一个可移植的设计工程内核。这里的生命周期、源边界、路由、证据及验收环节都保持轻量化；仅当信号匹配时才加载专业方法。

Role boundaries

角色边界

Role	Source	Prior scores	Owns
Planner	yes	no	scope and success criteria
Visual Director	no	no	visual directions and selected visual contract
Builder	yes	no	implementation fidelity
Evaluator	no	no	rendered observations and scores
Orchestrator	as needed	yes	SELECT / REFINE / PIVOT / SHIP / HALT

Visual Director never receives HTML, CSS, JSX, selectors, implementation diffs or the unattended assignment index.
Evaluator never receives source, implementation effort, full design description or prior scores. Document evaluation also excludes renderer identity/build metadata.
Builder implements the selected direction; it may not quietly replace it with a safer one.
Orchestrator is the sole decision owner. Evaluators/reviewers provide evidence, not workflow decisions.

角色	是否接触源文件	是否查看历史评分	负责内容
Planner（规划师）	是	否	范围与成功标准
Visual Director（视觉总监）	否	否	视觉方向与选定的视觉契约
Builder（构建师）	是	否	实现保真度
Evaluator（评估师）	否	否	渲染观测结果与评分
Orchestrator（编排师）	按需	是	选择/优化/转向/交付/终止

Visual Director 永远不会收到 HTML、CSS、JSX、选择器、实现差异或无人干预的任务分配索引。
Evaluator 永远不会收到源文件、实现工作量、完整设计描述或历史评分。文档评估还会排除渲染器标识/构建元数据。
Builder 负责实现选定的方向；不得擅自将其替换为更保守的方案。
Orchestrator 是唯一的决策所有者。评估者/审核者仅提供证据，不参与工作流决策。

Load and route

加载与路由

Load
```
invocation.md
```
for host input mapping and isolated-role rules.
Load
```
workflow.yaml
```
for the interactive Studio lifecycle and shared schemas/budgets/decisions.

Load

runtime-contract.md

references/context.md

and

references/runtime-integrity.md

for deterministic operations and run truth.

Read
```
method-router.json
```
. Every populated signal dimension on a route is required; load the union of matching
```
leaves
```
. If the route declares
```
procedure
```
, run that progressively disclosed procedure after its leaves.
Never load the full specialist catalog by default.

method-router.json

is routing data, not method authority. Repository ADR/authority-map paths are provenance metadata only; installed runs do not depend on repository docs.

加载
```
invocation.md
```
以进行宿主输入映射和角色隔离规则配置。
加载
```
workflow.yaml
```
以获取交互式 Studio 生命周期及共享模式/预算/决策信息。

加载

runtime-contract.md

、

references/context.md

和

references/runtime-integrity.md

以确保操作的确定性和运行真实性。

读取
```
method-router.json
```
。路由上每个已填充的信号维度都是必需的；加载匹配的
```
leaves
```
的并集。如果路由声明了
```
procedure
```
，则在加载其 leaves 后逐步执行该流程。
默认情况下绝不加载完整的专业方法目录。

method-router.json

是路由数据，而非方法权威来源。仓库的ADR/权限映射路径仅作为溯源元数据；已安装的运行实例不依赖仓库文档。

Required references

必需参考文件

```
invocation.md
```
```
workflow.yaml
```
```
runtime-contract.md
```
```
method-router.json
```
```
references/context.md
```
```
references/runtime-integrity.md
```
Conditional Document procedure:
```
references/document/document.md
```

The first six entries are the installed kernel. Document and specialist methods are conditional.

```
invocation.md
```
```
workflow.yaml
```
```
runtime-contract.md
```
```
method-router.json
```
```
references/context.md
```
```
references/runtime-integrity.md
```
条件文档流程：
```
references/document/document.md
```

前六项是已安装的内核文件。文档和专业方法是可选加载的。

Lanes

工作流通道

Lane	Trigger	Authority
Studio	new interactive surface or material redesign	`workflow.yaml`
Review	audit/polish while preserving an interactive visual world	routed `references/review/polish.md`
Document	quote, invoice, SOW, proposal, report, brief, print/PDF or other paginated artifact	routed `references/document/document.md`
Design system	codify an accepted system	Studio codify or accepted Document contract
Meta	improve Design Studio	routed `references/meta.md`

An interactive report remains Studio/Review even if it can export PDF. Page/print intent and pagination route to Document. A narrow component/CSS correction does not require Studio.

通道	触发条件	权威来源
Studio	新交互式界面或物料重设计	`workflow.yaml`
Review（审核）	在保留交互式视觉场景的前提下进行审计/优化	路由至 `references/review/polish.md`
Document（文档）	报价单、发票、工作说明书、提案、报告、简报、印刷/PDF 或其他分页制品	路由至 `references/document/document.md`
Design system（设计系统）	对已验收的系统进行编码	Studio 编码流程或已验收的 Document 契约
Meta（元优化）	改进 Design Studio	路由至 `references/meta.md`

即使交互式报告可以导出PDF，它仍属于 Studio/Review 通道。页面/印刷意图及分页需求会路由至 Document 通道。单一组件/CSS修正无需使用 Studio。

Studio

Studio 流程

Execute

workflow.yaml

end to end.

Prove repository/app/context roots and actual capabilities before planning.
Separate product truth, copy authority and proven visual authority.
Commit unattended candidate assignment before direction generation and hide it from Visual Director.
Generate materially different viable directions; user choice or precommitted assignment selects.
Builder implements the source-free direction. Local mechanical evidence runs before blind browser evaluation.
Evaluator uses required live viewports without source/prior scores. Orchestrator alone decides.
Preserve evaluated builds/evidence. Acceptance names the final tree before codification.

The brief wins. Redesign replaces the visual world while preserving confirmed truth/behaviour; refinement preserves the established world.

完整执行

workflow.yaml

。

在规划前确认仓库/应用/上下文根目录及实际能力。
区分产品事实、文案权威来源及已验证的视觉权威来源。
在生成方向前提交无人干预的候选任务分配，并对 Visual Director 隐藏该信息。
生成显著不同的可行方向；由用户选择或预提交的分配方案选定最终方向。
Builder 基于无源码的方向进行实现。在盲态浏览器评估前先运行本地机械验证。
Evaluator 使用必需的实时视口进行评估，不接触源码/历史评分。仅由 Orchestrator 做出决策。
保留已评估的构建版本/证据。在编码前为最终版本命名。

需求简报优先。重设计会替换视觉场景，但保留已确认的事实/行为；优化则保留现有场景。

Document

Document 流程

Execute

references/document/document.md

; do not force pages through the browser viewport graph. Reuse the same root, capability, assignment, mechanical-snapshot, evidence, decision and acceptance primitives over complete ordered rendered pages.

A4 is default; Letter and explicit physical sizes are supported without binding the visual model to a renderer.
Visual Director/Evaluator may receive rendered page images, never document source, renderer identity or implementation rationale.
Reuse hierarchy and generated-specificity methods, then the Document pagination, table, furniture and print lenses. Interaction/motion review does not apply.
Rendering/export is optional host capability. Without complete page evidence, creation preserves one build and halts unselected; review returns visual status unverified.
Accepted Document work may emit
```
harness-output/design-system/document-visual-contract.json
```
for downstream document-generation skills.

Design Studio owns visual page-system intent and rendered-page judgement. It does not own transcript interpretation, business voice, accounting truth, binding commercial/legal terms or the renderer/generator.

执行

references/document/document.md

；无需强制通过浏览器视口图处理页面。在完整的有序渲染页面上复用相同的根目录、能力、任务分配、机械快照、证据、决策及验收原语。

默认尺寸为A4；支持Letter及明确的物理尺寸，且无需将视觉模型绑定到特定渲染器。
Visual Director/Evaluator 可接收渲染后的页面图像，但永远不会收到文档源码、渲染器标识或实现理由。
复用层级结构和生成特异性方法，然后应用 Document 的分页、表格、装饰元素及印刷适配规则。交互/动效审核不适用。
渲染/导出是可选的宿主能力。若无完整页面证据，创建流程会保留一个构建版本并终止未选定的方案；审核流程会返回“视觉状态未验证”。
已验收的 Document 工作可输出
```
harness-output/design-system/document-visual-contract.json
```
，供下游文档生成技能使用。

Design Studio 负责视觉页面系统的意图及渲染页面的判断。它不负责文稿解读、商务话术、财务事实、具有约束力的商业/法律条款或渲染器/生成器。

Review

Review 流程

Review does not run the Studio create loop. Route through

references/review/polish.md

, then add only matching lenses. Reviewers report evidence first; implementation receives one bounded fix plan. Missing rendered evidence is

unverified

, not a clean verdict.

Review 流程不运行 Studio 的创建循环。通过

references/review/polish.md

进行路由，然后仅添加匹配的适配规则。审核者首先提交证据；实现环节仅接收一个有限范围的修复计划。缺失的渲染证据标记为“未验证”，而非合格结论。

Evidence and degradation

证据与降级处理

```
roots.json
```
/
```
capabilities.json
```
are operational truth;
```
events.jsonl
```
is append-only recovery truth.
```
PRODUCT.md
```
stores confirmed product truth;
```
COPY.md
```
durable language rules;
```
DESIGN.md
```
only proven accepted visual authority.
Mechanical snapshots are complete current-state evidence. Missing evidence is explicit, never a pass.
Acceptance, not directory existence or a high score, proves authority.

All create lanes need file I/O, shell and isolated roles. Interactive visual decisions additionally need a runnable target/browser; Document decisions need complete rendered page evidence from an existing artifact or host-supplied renderer.

Missing browser in Studio: one build + mechanical evidence, then halt without winner.
Missing interactive viewport in Review: partial evidence, visual status unverified.
Missing complete pages in Document: never infer quality from source; follow the Document failure contract.
No user-answer mechanism: use precommitted deterministic assignment.
No image generation: use equally specified text directions.
Any failed/missing operation is recorded with exact reason.

```
roots.json
```
/
```
capabilities.json
```
是操作事实；
```
events.jsonl
```
是仅可追加的恢复事实。
```
PRODUCT.md
```
存储已确认的产品事实；
```
COPY.md
```
存储持久化语言规则；
```
DESIGN.md
```
仅存储已验证的已验收视觉权威内容。
机械快照是完整的当前状态证据。缺失证据需明确标记，绝不默认通过。
验收结果而非目录存在或高分证明权威。

所有创建通道都需要文件I/O、shell及角色隔离。交互式视觉决策还需要可运行的目标/浏览器；Document决策需要来自现有制品或宿主提供的渲染器的完整渲染页面证据。

Studio 中缺少浏览器：生成一个构建版本 + 机械证据，然后终止流程且不选定胜出方案。
Review 中缺少交互式视口：仅提供部分证据，视觉状态标记为未验证。
Document 中缺少完整页面：绝不从源码推断质量；遵循 Document 失败契约。
无用户应答机制：使用预提交的确定性任务分配方案。
无图像生成能力：使用同等规格的文本描述方向。
任何失败/缺失的操作都需记录确切原因。

Method ownership

方法所有权

Design Studio has no upstream design-method runtime dependency. Adopted external ideas live as routed local methods with provenance; observation/rejection records are research evidence only. Do not import another command taxonomy, prompt library or fallback runtime.

Growth Arsenal remains outside this method kernel and may provide approved role-scoped offer/copy artifacts through the composition boundary. A new method must name a reusable gap, fit or justify authority, pin external source/licence when relevant, adapt the smallest coherent slice and prove benefit with an eval/contract/dogfood result.

Design Studio 无上游设计方法运行时依赖。采用的外部理念作为路由本地方法存在，并附带溯源信息；观察/拒绝记录仅作为研究证据。不得导入其他命令分类体系、提示库或 fallback 运行时。

Growth Arsenal 不属于此方法内核，可通过组合边界提供经批准的角色限定型报价/文案制品。新方法必须明确可复用的缺口、适配性或权威理由，必要时固定外部来源/许可证，适配最小的连贯切片，并通过评估/契约/内部试用结果证明收益。