Skip to content

AI turns documents or topics into real, native PowerPoint decks—with native shapes, transitions and animations, data-backed charts and tables on demand, audio narration from speaker notes, and support for your own .pptx templates. · by Hugo He

docs: template facts may inform canvas and page range, never the goal

Kevin667b032bbb3f
diff --git a/docs/getting-started.md b/docs/getting-started.md
index b9c28464..e2ec69d4 100644
--- a/docs/getting-started.md
+++ b/docs/getting-started.md
@@ -73,7 +73,7 @@ A created template lives in one of two places:
| **Registered in the skill library** | `skills/ppt-master/templates/<kind>/<id>/` | Portable workspace plus global registration, so it appears when you ask "what templates are available?" |
| **Under projects** | `projects/<name>/` | A shared qualified-spec root without global registration; all four kinds may coexist, with Layout taking structural precedence over Deck |
-Default Generate shows the template choice inside Stage 1, beside the communication contract. The initial communication recommendation is written without reading any template. Ordinary requests start with free design; explicit template intent or any exact root starts in template mode, and the user can always switch. To offer another result, supply its exact **workspace-root path** in chat: an unregistered root appears in the specified-root dropdown, while an exact registered match resolves back to its kind dropdown. Exactly one supplied root may be preselected; multiple supplied roots remain unselected candidates. Each kind may appear once; Layout and Deck may coexist, with Layout supplying structure. A multi-kind project root is selected atomically. One confirmation closes communication and template choice together. Only then are selected roots validated and installed; template-aware planning begins in final Stage 2. A bare template name never resolves to a workspace. A project root can be reused directly by another project; moving one contribution into the library changes its spec filename placement and adds registration.
+Default Generate shows the template choice inside Stage 1, beside the communication contract. A template never rewrites the communication goal; template facts already in context, such as an exact root's kind and canvas, may inform only the recommended canvas and page range. Ordinary requests start with free design; explicit template intent or any exact root starts in template mode, and the user can always switch. To offer another result, supply its exact **workspace-root path** in chat: an unregistered root appears in the specified-root dropdown, while an exact registered match resolves back to its kind dropdown. Exactly one supplied root may be preselected; multiple supplied roots remain unselected candidates. Each kind may appear once; Layout and Deck may coexist, with Layout supplying structure. A multi-kind project root is selected atomically. One confirmation closes communication and template choice together. Only then are selected roots validated and installed; template-aware planning begins in final Stage 2. A bare template name never resolves to a workspace. A project root can be reused directly by another project; moving one contribution into the library changes its spec filename placement and adds registration.
```
You: Make a deck from sources/report.pdf with template skills/ppt-master/templates/layouts/presentation_core/
diff --git a/docs/technical-design.md b/docs/technical-design.md
index fd7ebb6c..01953273 100644
--- a/docs/technical-design.md
+++ b/docs/technical-design.md
@@ -448,11 +448,11 @@ input.
`<template_workspace>` is either `skills/ppt-master/templates/<kind>/<id>/` or
another exact workspace root such as `projects/<name>/`. Step 3 records it as
-candidate input without reading template content. Once Stage 1 selects it, the
-apply stage validates and installs it into the current project's
-`templates/`, `images/`, and `icons/`; it never copies `exports/`. Strategist
-and later roles read only that project-local copy when template-aware planning
-begins after Stage 1. A project root remains directly reusable by another
+candidate input, reading only the frontmatter its kind and canvas need. Once
+Stage 1 selects it, the apply stage validates and installs it into the current
+project's `templates/`, `images/`, and `icons/`; it never copies `exports/`.
+Strategist and later roles read only that project-local copy when template-aware
+planning begins after Stage 1. A project root remains directly reusable by another
project. Moving one contribution into the library preserves its spec schema and
assets but changes its qualified filename to the bare single-kind library path;
global index registration then controls whether it appears as a library choice.
@@ -496,9 +496,12 @@ PPT Master keeps deck-state roles—Strategist, Image_Generator, and Executor—
**Template choice and communication share Stage 1.** Step 3 prepares candidates
without interaction, while the Stage-1 communication recommendation is authored
-without reading those candidates or any template content. The UI confirms that
-communication contract and the switchable free-design/template choice together;
-only afterward does the agent install every selected spec separately into the
+without opening candidate specs or prototypes. A template never rewrites the
+communication goal; an exact or handed-off root's kind and canvas may inform the
+recommended canvas and page range, and a differing canvas is a visible Stage-1
+decision. The UI confirms that communication contract and the switchable
+free-design/template choice together; only afterward does the agent install
+every selected spec separately into the
project. Strategist uses one dependency-ordered two-stage gate. Its `delivery_context` recommendation distinguishes presenter-led, reader-led, hybrid, and recorded/self-running use in one prose field, names the primary context, and records any secondary use; hybrid never stands alone without its lead mode. The prose boxes remain editable and none requires a non-empty answer: confirmation persists the current text exactly, and a cleared value stays empty instead of falling back to the recommendation. Final Stage 2 is authored once from that contract. Strategist first creates exactly three complete, viable, project-fit solutions, then projects each into a custom mode, custom visual style, color, typography, icon, and custom generated-image rendering; the fixed catalogs remain conservative lower-level single-select alternatives. Each direction is one complete design authored top-down within the confirmed contract rather than assembled from catalog picks, and three exist so a single recommendation cannot lock the user in; the fixed catalogs stay the manual lower layer. `custom` has no required relationship to the catalogs, and one selected preset may be carried unchanged. The three bundles are plainly different designs at the whole-deck level, decided before any field is written and only then projected onto mode, visual style, rendering, color, typography, and icons; that difference lives in the solutions rather than in one designated field, so whichever components a direction requires carry it and any component may coincide. A different name, note, or reference count alone is not a difference, and bundles identical on every component are not three solutions. Where authoritative user/template truth fixes some components, the remaining open ones carry the difference; identical projections are valid only when nothing is open, and the plan states that boundary instead of inventing variation. It does not assemble the three solutions afterward from independent component picks or force them into safe / shifted / bold archetypes. After all three bundles are complete, free design records the strongest overall fit as zero-based `design_directions.selected`. With installed template state, every bundle remains compliant with the same resolved context; `selected` identifies the viable bundle that most fully expresses it, while the other two vary only open dimensions rather than weakening template use or splitting its segments. Array order has no preference meaning. Before reference selection it reads only the three catalog indexes; after each solution's bases are frozen, it reads only the deduplicated selected detail files and completes the custom behaviors. Image source remains an independent judgment, so every solution already has a rendering candidate even when AI imagery is initially not recommended. The preferred top card is marked and applied initially. An inactive top card applies its immutable bundle, each projected custom card becomes editable in place after selection, and all lower controls may diverge; the adjusted active card exposes an explicit restore action, while final state stores only the edited current components. The same stage confirms reading mode, page count, conditional AI acquisition, generation mode, the Design Spec review toggle, and whether the agent should proactively generate speaker notes, custom animations, or narration audio. Formula handling is not a user-selectable production policy: structural mathematics becomes a native formula marker during authoring. Only after Stage 1 is confirmed, when a template is installed, does Strategist read the project-local workspace and current content, derive **how to apply it**, and expose that plan as editable `template_application` prose; Stage 2 never reselects a template, and the internal reuse/adherence modes stay hidden. Reading mode decides how meaning is carried by page, visuals, presenter, and notes; its cards do not present px values. The browser may apply the deterministic `reading mode → body baseline → unpinned role sizes` dependency locally, while manual size edits pin visible values. It never regenerates Stage 2. The three proactive values are fallback policies, not capability bans: the latest explicit user instruction wins, then final Stage 2, then the fixed defaults `true / false / false`. Strategist still records non-binding Motion suggestions when useful; a suggestion alone does not activate custom-animation execution. Generated images inherit the selected deck color anchors directly; there is no independent image-palette choice. Final state has two equivalent carriers: the default UI path reads `confirm_ui/result.json` exactly once after the final wait, while an explicit chat-only or delegated path retains an equivalent final confirmation summary and may produce no `result.json`. Both paths first resolve and persist every effective production outcome into one `design_spec.md` and complete Gate 1 fidelity. With refinement off, lock authoring proceeds immediately. With `refine_spec: true`, the pipeline stops before `spec_lock.md`; the user may revise any part of that same Design Spec through normal chat for any number of rounds, and explicit approval then releases Gate 2 lock authoring. No second Design Spec or parallel lock is maintained. Normal lock authoring and downstream execution do not reread either confirmation channel. Required manual assets may still introduce their own conditional blocking points, so this is not an exclusive claim over every runtime gate. Project validation requires the compact `audience` / `objective` / `core_message` anchor set under `spec_lock.md ## communication` plus an `Audience move` in every §IX Slide block.
The three proactive values confirmed in final Stage 2 remain independent raw
diff --git a/docs/templates-architecture.md b/docs/templates-architecture.md
index 53ce3f49..0f4785fa 100644
--- a/docs/templates-architecture.md
+++ b/docs/templates-architecture.md
@@ -101,7 +101,8 @@ Both roots have the same core shape:
Empty optional directories are omitted; do not add placeholder files. A preview
PPTX is derived review evidence, not a source template asset. It is generated
on request and is mandatory for a multi-Master package gate. Step 3 records the
-workspace root as candidate input without reading its content. After Stage 1
+workspace root as candidate input, reading only the frontmatter an exact root
+needs for kind and canvas. After Stage 1
selects it, the apply stage consumes `templates/` plus any existing `images/`
and `icons/`; it ignores `exports/`. Library `exports/` directories are
Git-ignored.
@@ -504,7 +505,7 @@ Bitmaps share the workspace `images/` pool and template SVGs reference them thro
### Strategist confirmation stage behavior per kind
-Installing a template does not narrow away the communication question. Stage 1 confirms the same open communication contract together with, but independently from, the template choice. The communication recommendation uses only the current request, source facts, conversation constraints, and project initialization; even template canvas is excluded. Only after Stage 1 closes and any selection is installed does final Stage 2 inspect that state and confirm the complete solution and production plan. Brand supplies identity constraints while structure stays free; Style supplies method and visual-default seeds while remaining flat; Layout exposes structural capability; Deck contributes descriptive reusable application context for comparison, not the current project's contract. For Style-only use, Strategist does not look for prototypes and deterministically records `template_reuse_scope: style` with flat structure. It otherwise inspects every effective prototype—Layout when present, otherwise Deck—and current content, then authors one page/prototype plan and records `mirror`, `layout`, or `style` only as internal exporter values. A mirror-authored workspace therefore enables literal reuse but never forces it.
+Installing a template does not narrow away the communication question. Stage 1 confirms the same open communication contract together with, but independently from, the template choice. The communication goal (audience, intent, outcome, core message, delivery context, and afterlife) comes only from the current request, source facts, conversation constraints, and project initialization; template facts already in context may inform only the recommended canvas and page range, and a canvas that differs from project initialization is a visible Stage-1 decision. Only after Stage 1 closes and any selection is installed does final Stage 2 inspect that state and confirm the complete solution and production plan. Brand supplies identity constraints while structure stays free; Style supplies method and visual-default seeds while remaining flat; Layout exposes structural capability; Deck contributes descriptive reusable application context for comparison, not the current project's contract. For Style-only use, Strategist does not look for prototypes and deterministically records `template_reuse_scope: style` with flat structure. It otherwise inspects every effective prototype—Layout when present, otherwise Deck—and current content, then authors one page/prototype plan and records `mirror`, `layout`, or `style` only as internal exporter values. A mirror-authored workspace therefore enables literal reuse but never forces it.
Default still presents three template-compliant design directions. The Recommended direction is the viable one that most fully expresses the resolved template context; the other two vary only dimensions left open by that context and the user. Quick materializes no candidate set and directly executes that same recommended-direction rule.
diff --git a/docs/templates-guide.md b/docs/templates-guide.md
index 819bce37..e3c35719 100644
--- a/docs/templates-guide.md
+++ b/docs/templates-guide.md
@@ -92,10 +92,14 @@ sentence is fine; the path just has to be unambiguous:
For every current template kind, an explicit path is the **template workspace root**. An exact root matching a registered index entry may be displayed as `library`; an unregistered root remains separately labelled `explicit`. The server parses the latter's actual qualified specs; `explicit` is provenance, not a fifth kind or a priority tier. Stage 1 validates each selected root atomically. After confirmation, installation maps every selected spec and asset root exactly once, installs only the effective structural roster (Layout when present, otherwise Deck), and never copies `exports/`. Deck/Layout roots additionally validate their structured SVG contracts before precedence is applied; Brand/Style validate their roster-free specs. The path may point to a built-in library workspace under `skills/ppt-master/templates/<kind>/<id>/`, a project workspace under `projects/<name>/`, or another workspace with the same routing. A Create Template run may hand its exact validated workspace root directly to the next Stage-1 selector in the same conversation.
Template selection shares the Stage-1 screen and submit action but remains a
-separate sidecar decision. The communication recommendation is authored only
-from the current request, source facts, conversation constraints, and project
-initialization; candidate metadata, selected roots, installed content, and
-template canvas cannot influence it. After the combined confirmation, a
+separate sidecar decision. The communication goal (audience, intent, outcome,
+core message, delivery context, and afterlife) is authored only from the
+current request, source facts, conversation constraints, and project
+initialization; a candidate's existence, summary, or prototypes never bend it.
+Template facts already in context—a root handed off by Create Template in this
+conversation, or an exact root's kind and canvas—may inform only the
+recommended canvas and page range, and a canvas that differs from project
+initialization is a visible Stage-1 decision. After the combined confirmation, a
non-free choice runs the common apply stage and installs the selected
workspaces into the project's `templates/`, `images/`, and `icons/`. Final
Stage 2 then compares the confirmed communication contract with that installed
diff --git a/docs/zh/getting-started.md b/docs/zh/getting-started.md
index 586ade1f..ae6c135b 100644
--- a/docs/zh/getting-started.md
+++ b/docs/zh/getting-started.md
@@ -73,7 +73,7 @@ Create Template 会分析参考材料,确认结果属于 Brand、Style、Layou
| **注册进 skill 库** | `skills/ppt-master/templates/<kind>/<id>/` | 可移植工作区并执行全局注册;问“有哪些模板”时会被列出来 |
| **放在 projects 下** | `projects/<name>/` | 不执行全局注册的共享限定名 spec root;四种 kind 均可共存,结构由 Layout 优先于 Deck |
-Default Generate 把模板选择放在 Stage 1,与沟通契约同屏确认;沟通推荐在此之前不会读取任何模板。普通请求默认自由设计;用户明确要求模板或提供任意精确 root 时,默认进入模板模式,但界面始终允许切换。未注册 root 会进入指定地址下拉框;与注册 canonical root 完全相同的路径会归回对应 kind 下拉框。只提供一个 root 时可预选它;提供多个 root 时都只作为候选、不预选。完整选择中每个 kind 最多一份;Layout 与 Deck 可以共存,结构由 Layout 提供。多 kind project root 必须原子选择。一次确认同时闭合沟通与模板选择,随后才校验、安装所选 root;最终 Stage 2 才读取安装结果。裸模板名不会被解析为工作区。Project root 可直接被其他项目复用;把其中一项迁入 library 时,需要改变 spec 文件名落点并完成注册。
+Default Generate 把模板选择放在 Stage 1,与沟通契约同屏确认;模板不会改写沟通目标,上下文中已有的模板事实(如精确 root 的 kind 与画布)只可影响推荐画布与页数范围。普通请求默认自由设计;用户明确要求模板或提供任意精确 root 时,默认进入模板模式,但界面始终允许切换。未注册 root 会进入指定地址下拉框;与注册 canonical root 完全相同的路径会归回对应 kind 下拉框。只提供一个 root 时可预选它;提供多个 root 时都只作为候选、不预选。完整选择中每个 kind 最多一份;Layout 与 Deck 可以共存,结构由 Layout 提供。多 kind project root 必须原子选择。一次确认同时闭合沟通与模板选择,随后才校验、安装所选 root;最终 Stage 2 才读取安装结果。裸模板名不会被解析为工作区。Project root 可直接被其他项目复用;把其中一项迁入 library 时,需要改变 spec 文件名落点并完成注册。
```
你:用 sources/report.pdf 做 deck,模板用 skills/ppt-master/templates/layouts/presentation_core/
diff --git a/docs/zh/technical-design.md b/docs/zh/technical-design.md
index e5bfdfa0..fd5943fa 100644
--- a/docs/zh/technical-design.md
+++ b/docs/zh/technical-design.md
@@ -381,7 +381,7 @@ Style 只贡献自己的 Design Spec,不携带素材或审阅 payload;项目
`<template_workspace>` 可以是 `skills/ppt-master/templates/<kind>/<id>/`,也
可以是 `projects/<name>/` 等其他精确 root。Step 3 只把它记录为候选输入,
-不读取模板内容;Stage 1 选中后,apply 阶段才逐个校验 root,把每份选中 `spec`
+且只读取判断其 kind 与画布所需的 frontmatter;Stage 1 选中后,apply 阶段才逐个校验 root,把每份选中 `spec`
作为独立的项目本地贡献安装到当前项目的 `templates/`,并把对应的真实素材
安装到 `images/`、`icons/`,且不复制 `exports/`、不合并 `spec` 正文。Stage 1 之后开始模板感知规划时,
Strategist 及后续角色只读该项目本地副本。Project root 可直接被其他项目
@@ -420,7 +420,7 @@ PPT Master 把拥有 deck 状态的 Strategist、Image_Generator 和 Executor
**为什么是角色专属 reference 而不是一个超大 prompt。** Strategist 跑的是「跟用户协商」模式(开放式、对话式、可以回退),Executor 跑的是「产出严格 XML」模式:不得重选上游方案或漏掉必需属性,但在 Design Spec 留出的范围内仍拥有几何、构图、层级和视觉处理的实现权。把两者塞进同一个 prompt,强迫模型在同一个 turn 里持守相互矛盾的纪律——所有混合模式的 prompt 工程病灶都会出现。按角色拆开,每个角色只加载它需要的、扔掉其他。
**模板选择与沟通契约在 Stage 1 同时确认。** Step 3 只在内部准备候选;
-Stage-1 沟通推荐的编写不得读取这些候选或任何模板内容。UI 在同一次提交中
+Stage-1 沟通推荐的编写不得打开候选 spec 或原型。模板不会改写沟通目标;精确 root 或交接 root 的 kind 与画布可以影响推荐的画布与页数范围,画布与项目初始化不一致时则是可见的 Stage-1 决定。UI 在同一次提交中
确认沟通契约与可切换的自由设计/使用模板选择;只有确认后,Agent 才把非自由设计选择安装成彼此独立的项目本地 `spec`。Strategist 采用一个按依赖排序的两阶段 gate。`delivery_context` 在同一个开放文本字段中区分演讲者主导、读者主导、混合、录制/自动播放,明确主要场景并记录可选的次要用途;混合场景不能只写“混合”而不说明由哪一种主导。其中的文本框仍承载可编辑推荐,且没有任何一项要求非空:确认时按当前文本原样保存,清空后的值保持为空,不会回退到推荐内容。最终 Stage 2 只从该契约计算一次,同时确认完整 PPT 方案与生产机制:阅读模式、叙事 mode、页数、成套视觉系统、图片来源、生成图渲染、条件式 AI 图片获取路径、生成模式、Design Spec 审核开关,以及 Agent 是否主动生成讲稿、自定义动画和旁白音频。公式处理不是用户选择的生产策略:结构性数学内容在创作时直接成为原生公式 marker。仅在 Stage 1 确认后,存在已安装模板时,Strategist 才读取项目本地工作区和当前内容,推导**如何应用**并以可编辑的 `template_application` 自然语言展示;Stage 2 不会重新选模板,内部复用/遵循模式保持隐藏。阅读模式决定信息由页面、视觉、讲者和备注如何共同承担,其选项卡不展示 px 数值。浏览器可以在本地执行确定性的「阅读模式 → 正文基准 → 未锁定角色字号」联动;手动编辑字号即锁定可见值,不会重新计算 Stage 2。三个主动执行值是用户未明确要求时的兜底策略,不是能力禁用开关;优先级固定为「用户最新明确指令 → 最终 Stage 2 → `true / false / false` 默认值」。Strategist 仍可按内容给出非绑定的 Motion suggestion,建议本身不会启动自定义动画执行。生成图直接继承已选 PPT 色彩锚点,不再单设图片调色选择。最终状态有两个等价载体:默认 UI 路径在最终等待返回后只读取一次 `confirm_ui/result.json`;显式 chat-only 或委托路径保留等价的最终确认摘要,并可不产生 `result.json`。两条路径都会先解析并把生产流程的最终有效结果固化到同一份 `design_spec.md`,再完成 Gate 1 fidelity。未开启 refine 时立即进入 lock 编写;`refine_spec: true` 时,流程会在 `spec_lock.md` 之前暂停,用户可以通过正常聊天任意修改这同一份 Design Spec、迭代任意轮次,明确批准后才释放 Gate 2 并编写 lock。流程不会维护第二份 Design Spec 或并行 lock。正常的 lock 编写与下游执行不再回读确认通道。必需人工素材未就绪仍可能引入条件式阻塞点,因此这里不是对所有 runtime gate 的排他声明。项目校验要求 `spec_lock.md ## communication` 下存在紧凑的 `audience` / `objective` / `core_message` 锚点,并要求 §IX 每个 Slide block 都有 `Audience move`。
Strategist 先创建恰好三套完整、可行、贴合项目的方案,再把每套方案投影为自定义 mode、自定义 visual style、色彩、字体、图标和自定义生成图 rendering;固定目录仍是保守的下层单选备选。每套方向都是在已确认契约内自顶向下完成的一套完整设计,而不是自下而上从目录里拼选出来的;给三套是为了不让单一推荐把用户锁死,固定 preset 目录始终是供用户手动选择的下层。`custom` 与 preset 目录没有固定关系,一个最合适的 preset 也可以原样成为完整基础。三套方案在整份 deck 的层面本身就显著不同:先定下三个大方案,再补全各自细节,最后才映射到 mode、visual style、rendering、色彩、字体和图标等具体选项。差异存在于方案本身,而不是由某个指定字段来证明——由该方案设计真正需要的组件承担,任何组件都可以承担,也任何组件都允许一致。仅换名称、note 或参考数量不构成差异;所有组件都完全相同的三项也不成其为三套方案。当用户或模板的真值锁定了部分组件时,由其余开放组件承担差异;只有在没有任何开放组件时投影才可以完全相同,并须如实说明边界而不是强行制造差异。它不会事后从相互独立的组件选择中拼装这三套方案,也不会把它们硬套进 safe / shifted / bold 原型。三套成套方案全部完成后,自由设计按已确认契约与来源比较整体适配度,把最优者的零基索引写入 `design_directions.selected`。已安装模板时,三套方案都遵守同一套解析后的模板上下文;`selected` 指向其中最充分表达该模板的可行方案,另外两套只在开放维度上变化,不得通过弱化模板使用或拆分其片段来制造差异。数组顺序不表示偏好。选择参考前只读取 mode、visual style 与 rendering 的三个目录索引;各方向的基础冻结后,只读取去重后的已选细节文件并完成 `custom` 行为。图片来源是独立判断,所以即使最初不推荐 AI 图片,每套方向也已包含 `rendering` 候选。首选方向卡片会被标记并在初始时应用;点击未激活的方向卡片会应用其不可变的整套方案,选中的 `custom` 投影卡片随后可原位编辑,下层控件也可彼此分离。已调整的活动卡片提供显式恢复操作,最终状态只保存编辑后的当前组件值。
diff --git a/docs/zh/templates-architecture.md b/docs/zh/templates-architecture.md
index 06a33332..e03455fb 100644
--- a/docs/zh/templates-architecture.md
+++ b/docs/zh/templates-architecture.md
@@ -91,7 +91,7 @@ native_structure_mode: structured
空的可选目录直接省略,不添加占位文件。预览 PPTX 是派生审阅证据,不是模板
源资产;单 Master 按需生成,多 Master 必须通过该 package gate。Step 3 只把
-工作区 root 记录为候选输入,不读取其内容;Stage 1 选中后,apply 阶段才消费
+工作区 root 记录为候选输入,只读取精确 root 确定 kind 与画布所需的 frontmatter;Stage 1 选中后,apply 阶段才消费
`templates/` 及实际存在的 `images/`、`icons/`,不会复制或使用 `exports/`;
全局库下的 `exports/` 统一由 Git 忽略。
@@ -432,7 +432,7 @@ apply 阶段解析一份 library 裸 spec 或全部 project 限定名 spec;根
### Strategist 确认阶段在不同类型下的行为
-安装模板不会让沟通问题消失。Stage 1 把同一份开放式沟通契约与模板选择同时确认,但两者相互独立:沟通推荐只使用当前请求、源材料事实、对话约束和项目初始化状态,连模板画布也不能参与。Stage 1 完成且所选模板安装后,最终 Stage 2 才读取该状态,并确认完整方案与制作计划。Brand 提供身份约束、结构仍然自由;Style 提供方法和视觉默认值候选并保持 flat;Layout 提供结构能力;Deck 提供描述性的可复用应用语境供对照,但不充当当前项目契约。Style-only 时 Strategist 不读取原型,固定写入 `template_reuse_scope: style` 与 flat 结构;其他情况读取全部有效原型(有 Layout 时用 Layout,否则用 Deck)和当前内容,生成页面/原型计划,并把 `mirror`、`layout` 或 `style` 记录为内部导出值。按 mirror 创建的工作区因此只提供原样复用能力,不会强制使用。
+安装模板不会让沟通问题消失。Stage 1 把同一份开放式沟通契约与模板选择同时确认,但两者相互独立:沟通目标(受众、意图、结果、核心信息、交付场景与成品后续生命)只来自当前请求、源材料事实、对话约束和项目初始化状态;上下文中已有的模板事实只可影响推荐画布与页数范围,与项目初始化不同的画布是 Stage 1 中可见的决定。Stage 1 完成且所选模板安装后,最终 Stage 2 才读取该状态,并确认完整方案与制作计划。Brand 提供身份约束、结构仍然自由;Style 提供方法和视觉默认值候选并保持 flat;Layout 提供结构能力;Deck 提供描述性的可复用应用语境供对照,但不充当当前项目契约。Style-only 时 Strategist 不读取原型,固定写入 `template_reuse_scope: style` 与 flat 结构;其他情况读取全部有效原型(有 Layout 时用 Layout,否则用 Deck)和当前内容,生成页面/原型计划,并把 `mirror`、`layout` 或 `style` 记录为内部导出值。按 mirror 创建的工作区因此只提供原样复用能力,不会强制使用。
Default 仍提供三套符合模板约束的设计方向。其中的推荐方向是最充分表达解析后模板上下文的可行方案;另外两套只在模板和用户留白的维度上变化。Quick 不生成候选集,而是直接执行同一套推荐规则。
diff --git a/docs/zh/templates-guide.md b/docs/zh/templates-guide.md
index f29107eb..390eb4f5 100644
--- a/docs/zh/templates-guide.md
+++ b/docs/zh/templates-guide.md
@@ -78,8 +78,11 @@ Layout 提供结构,否则由 Deck 提供。指定地址最多选一个,并
对于当前所有模板类型,显式路径都是**模板工作区根目录**。若精确路径与索引中的注册 root 一致,页面可以把它显示为 `library`;未注册 root 则单独标为 `explicit`,并由服务端解析其中真实的限定名 spec。`explicit` 只是来源,不是第五种类型,也不提高优先级。Stage 1 会原子校验每个已选 root;确认后,每个不同 root 的 spec 和真实包自有 `images/`、`icons/` 只映射一次,并只安装有效结构 roster(有 Layout 时用 Layout,否则用 Deck),始终不复制 `exports/`。Deck/Layout root 会在应用优先级前各自校验 structured SVG 合同;Brand/Style 校验各自无 roster 的 spec。路径可以指向 `skills/ppt-master/templates/<kind>/<id>/` 下的内置库工作区、`projects/<name>/` 下的项目工作区,或其他保持同样路由的工作区。当前对话刚完成 Create Template 时,可把精确的已验证工作区根目录直接交给下一次 Stage-1 选择器。
模板选择与 Stage 1 共用页面和提交动作,但仍作为独立 sidecar 决策保存。
-沟通推荐只使用当前请求、源材料事实、对话约束和项目初始化状态;候选元数据、
-所选 root、已安装内容及模板画布均不得影响它。合并确认后,非自由设计选择才
+沟通目标(受众、意图、结果、核心信息、交付场景与成品后续生命)只来自当前请求、
+源材料事实、对话约束和项目初始化状态;候选模板的存在、摘要或原型都不会扭曲它。
+上下文中已有的模板事实——本次对话中由 Create Template 交接的 root,或精确 root
+的 kind 与画布——只可影响推荐画布与页数范围;与项目初始化不同的画布是 Stage 1
+中可见的决定。合并确认后,非自由设计选择才
运行统一 apply 阶段,把所选工作区分别校验并安装到当前项目的 `templates/`、
`images/`、`icons/`。最终 Stage 2 再把已确认沟通契约与安装状态适配;
`template_application` 只描述**如何使用**,不负责决定**选哪个模板**。