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(rules): add ownership.md, rule-owners registry, SKILL vocabulary; prescriptive prompt-style
hugohe354358d2b16ba
diff --git a/AGENTS.md b/AGENTS.mdindex 78900c0e..e61b3d3c 100644--- a/AGENTS.md+++ b/AGENTS.md@@ -43,7 +43,7 @@ PPT Master turns source material into natively editable DrawingML PPTX. Generate- **Repo-wide style rules** — when editing prompt files under [`skills/ppt-master/references/`](skills/ppt-master/references/), Python under [`skills/ppt-master/scripts/`](skills/ppt-master/scripts/), or any other code/prose in the repo, follow the matching style rule in [`docs/rules/`](docs/rules/).- **Prompt content layers** — follow [`docs/rules/prompt-layers.md`](docs/rules/prompt-layers.md): a prompt file holds craft (design judgment) and the minimal contract the model writes; enforced grammar, importer behavior, and restated procedure live in [`scripts/docs/`](skills/ppt-master/scripts/docs/), one owner per rule with pointers elsewhere.-- **Prompt decision ownership** — follow [`docs/rules/prompt-style.md`](docs/rules/prompt-style.md) §4.1. Default Strategist prepares project-local resources and Executor realizes them; Quick's current agent decides and prepares before SVG authoring. This is not downstream acquisition. Every project icon is prepared material; `icons.inventory` indexes the default plan's curated bundled pool, not page usage or an execution whitelist. Sounds follow [`animations.md`](skills/ppt-master/references/animations.md) §2.2.+- **Prompt decision ownership** — follow [`docs/rules/ownership.md`](docs/rules/ownership.md); every cross-file rule has one owner recorded in [`docs/rules/rule-owners.md`](docs/rules/rule-owners.md). Default Strategist prepares project-local resources and Executor realizes them; Quick's current agent decides and prepares before SVG authoring. This is not downstream acquisition. Every project icon is prepared material; `icons.inventory` indexes the default plan's curated bundled pool, not page usage or an execution whitelist. Sounds follow [`animations.md`](skills/ppt-master/references/animations.md) §2.2.- **Markdown language consistency** — follow [`docs/rules/language.md`](docs/rules/language.md): one language per file, mirroring the siblings in that directory; a non-English string may appear in an English file only as quoted content (user trigger text, sample values, rendered labels, proper nouns), never as the wording of a rule; never hard-code which language the model replies in. Chat replies are unaffected.## Compatibility Boundarydiff --git a/docs/rules/README.md b/docs/rules/README.mdindex ab918b45..4788d305 100644--- a/docs/rules/README.md+++ b/docs/rules/README.md@@ -4,8 +4,10 @@ Conventions and style guides for contributors and AI agents working in this repo| Rule | Scope ||---|---|-| [`prompt-style.md`](./prompt-style.md) | Style guide for files under `skills/ppt-master/references/` — voice, sectioning, table-first, forbidden patterns |-| [`prompt-layers.md`](./prompt-layers.md) | What belongs in a prompt file — craft vs minimal contract vs tool documentation, where each lives, and how to move content out without losing a rule |+| [`prompt-style.md`](./prompt-style.md) | Style guide for every runtime-loaded file (`SKILL.md`, `references/`, `workflows/`, `templates/*.md`) — voice, one rule per sentence, labels, tables, exemplars |+| [`prompt-layers.md`](./prompt-layers.md) | What belongs in a prompt file — craft, minimal contract, procedure, or tool documentation — where each lives, and how to move content out without losing a rule |+| [`ownership.md`](./ownership.md) | Which role decides what — the plan / execution / Reference tiers, capability before selection, the core volume ceiling, preparation timing |+| [`rule-owners.md`](./rule-owners.md) | Registry of every cross-file rule: its one owner section and the files that may only point to it || [`code-style.md`](./code-style.md) | Style guide for Python under `skills/ppt-master/scripts/` — file headers, imports, CLI entry points, error handling, no-tests rule || [`language.md`](./language.md) | Language rule for agent-facing Markdown and `docs/` — one language per file, non-English as content but never as a rule, no hard-coded output language |diff --git a/docs/rules/ownership.md b/docs/rules/ownership.mdnew file mode 100644index 00000000..a30f2964--- /dev/null+++ b/docs/rules/ownership.md@@ -0,0 +1,102 @@+# Decision Ownership: Plan, Execution, and Reference++> Which role decides what in the Generate runtimes, and how strongly a written decision binds. [`prompt-layers.md`](prompt-layers.md) says what a prompt file may contain and [`prompt-style.md`](prompt-style.md) how it is written; this rule says who owns each decision. Classify a decision here before writing any rule about it, and keep each tier's rules in its own role's files.+++Constraint strength and decision ownership are independent. Preserve this chain whenever writing, compressing, or reviewing the default multi-role Generate prompts:++| Layer | Owns |+|---|---|+| User / initial materials | Supplied facts/assets, desired outcome, exclusions, and permission boundaries remain authoritative |+| Strategist / plan + preparation | Assess material sufficiency; trigger permitted topic research and retain its research/provenance pair without expanding adopted webpage URLs; decide the approved content, resources, keys, identity anchors, and exact page roster; record each page's semantic units and their source-stated relationships. While composing the roster, decide which pages need a prepared image, lettering, or illustrated-icon resource and derive the external-resource rows from that need. Sketch macro composition, visual focus, and continuity as Reference when useful, without selecting a carrier mix, a local authoring capability, or element geometry; materialize the planned project-local inventory or record an explicit `Needs-Manual` dependency before execution. For icons, prepare a curated project pool with broad semantic fit rather than assigning files to pages |+| Executor / realization | Use only prepared project-local assets; preserve approved content, relationships, resources, and identity anchors; realize each page by resolving the actual carrier combination, geometry, composition, hierarchy, and treatment together before coordinates — the carrier mix has no upstream owner. Discover and invoke local deterministic authoring capabilities without an upstream capability selection. Treat every Reference as a starting sketch to adjust freely for the page's purpose; follow a `(binding)` field literally. For icons, the complete `<project>/icons/` pool is prepared material; `icons.inventory` is a curated bundled-pool index, not a page-use plan or whitelist, and Executor chooses prepared icons per page without a coverage quota. Sparse local font/color garnish is allowed only while non-structural and non-recurring |++**Hard rule — three ownership tiers**: classify a decision before writing any+rule about it, and keep each tier's rules in its own role's files.++| Tier | Test | Examples | Contract |+|---|---|---|---|+| Plan-only | Needs a prepared file before authoring; holds only across the whole roster; needs one user confirmation; or comes from source semantics | Contract, canvas, page count, roster ids/order, `page_rhythm`, identity anchors (color, type, spacing, icons, style, mode), resources, per-page content, facts, semantic units and their relationships | Execution never reopens or substitutes it; a misfit returns upstream |+| Execution-only | Judged only with the objects on the canvas | Carrier mix, geometry and native contours, composition, coordinates, spacing, hierarchy treatment, effects, per-page icon and image treatment, wrapping | Plan writes no detail here, not even as advice |+| Reference (grey zone) | Useful as a first sketch, decidable either way | Macro composition and focus, continuity and motif, cover/closing composition, Chart/Table `family/key`, image `Layout pattern`, motion suggestions | Plan writes a starting sketch; Executor adjusts or replaces it freely for the page's purpose, with no upstream repair and no stated reason. It carries no binding semantics — anything that must hold is written in a plan-only field. It binds only when labeled `(binding)` because the user, a template, or a resource contract requires that property (explicit *must* / *only* / *exactly* / *verbatim*); Executor then follows it literally |++Depth test: one plan given to two competent Executors yields the same content+with different looks — converging looks mean the plan wrote execution,+diverging content means it left semantics open. `design_spec_depth` changes+only wording completeness and Reference length, never which plan-only fields+are written.++**Hard rule — capability knowledge precedes selection**: a role must know that+a capability exists before choosing among capabilities; otherwise a load trigger+circularly depends on a choice made without that capability. The always-read+core of the authoring role therefore carries the recall of every construction+capability — the everyday device menu and effects, the complete preset+vocabulary, the Structure decision, and one routing row per deeper module —+while the deeper module itself (effects beyond the everyday block, native-shape+authoring, relationship grammar and topology assembly, and the rarer formula,+hyperlink, chart/table, structured-template, video, animation, and web-image+files) is loaded when its observable trigger appears — evaluated once over the+whole roster before P01, or at the page that first reaches an unforeseen+capability — read completely, and kept for the run. The owning rule is+[`prompt-layers.md`](prompt-layers.md) §2.++**Hard rule — core volume ceiling**: the always-read core of an authoring role+stays small enough that its own content is not diluted by what follows. Measured+against the v2.13.0 baseline, an Executor-phase core of roughly 1,300 lines+across a role file plus a shared technical file produced richer pages than a+4,000-line, 12-file mandatory bundle; the larger bundle flattened expression+while passing every structural gate. Treat that as the working ceiling. When a+core grows past it, shrink it by removing what is not authoring guidance or by+moving a deeper module behind a trigger whose recall stays in the core. The+enforced form of this ceiling is the `stage.generate.executor.flat` load-set+budget in `scripts/prompt_audit_manifest.json`; the line count above is the+measurement that set it. What may stay in a+prompt file at all — craft, minimal contract, tool documentation, or procedure — and the+procedure for moving content out are owned by+[`prompt-layers.md`](prompt-layers.md).++Default Strategist's planning bundle covers resource/preparation and high-level+expression options without local authoring parameters, because those choices are+persisted into artifacts other roles consume. Only post-selection mechanics whose+trigger is independently observable stay conditional: an actual `ai` / `slice`+resource row triggers Image_Generator backend, prompt-assembly, and per-image+type details after planning, and those mechanics are not a missing Strategist+capability.++**Hard rule — native shapes are authoring capabilities, not prepared+resources**: a prepared resource needs a stable project-local file/path before+realization because page authoring cannot acquire or generate it in place.+Office presets, SVG primitives, Connectors, Boolean helpers, and necessary+freeform geometry are locally callable construction capabilities. Strategist+never inventories them or promotes a concrete preset, primitive, Connector,+Boolean/freeform operation, or authoring parameter into a binding planning+selection. A macro Reference may mention a technique as optional inspiration+without prescribing or gating construction. The Design Spec / lock create no+native-shape field; Executor reads the complete current preset vocabulary and+chooses the page-fit construction during realization.++**Preparation timing**: In the default pipeline, topic research and import of+its two-artifact research pair may run before final confirmation. Facts JSON+URLs are not auto-expanded. AI / web / slice acquisition runs only from the+completed `design_spec.md §VIII` and `spec_lock.md`, after final confirmation+and before Executor. Only after normal image search fails may one relevant+adopted page become a Markdown + companion-image source package; review it and+promote accepted files individually, never the whole package. Image_Generator,+Image_Searcher, and icon-sync tooling execute Strategist-owned preparation;+they are not independent decision owners.++**Post-motion sound exception**: optional transition/object sound is not a+page-authoring ingredient and never enters Strategist planning,+`design_spec.md`, or `spec_lock.md`. After the SVG roster and visual motion+solution are complete, the active animation/export stage may discover bundled+sound ids and sync only a concretely selected cue into the project. With no+selected cue, it creates no `<project>/sounds/` directory. This exception does+not permit Executor to acquire visual resources.++**Hard rule — default pipeline**: downstream freedom exists in every dimension the plan leaves open, and every Reference is open by definition. A named binding outcome retains identity; a broad semantic request or expression recommendation permits in-class choice. Once the plan resolves a plan-only choice or a `(binding)` Reference, execution cannot reopen or substitute it. For icons, library/stroke and the prepared-project boundary bind, while per-page choice within the prepared pool is realization. Executor never searches, generates, downloads, syncs, invents, or replaces a resource; missing material returns to Strategist-owned preparation or upstream repair.++**Explicit Quick Generate exception**: [`quick-generate`](../../skills/ppt-master/workflows/profiles/quick-generate.md) removes the separate Strategist/confirmation handoff. The current main agent therefore owns both its active-context decisions and the preparation of project-local sources, images, icons, and provenance before it begins SVG realization; native formulas are authored directly from exact mathematical content rather than acquired as resources. This exception does not move acquisition into a default-pipeline Executor and does not permit resource reselection while a page is being realized. Explicit user facts, choices, exclusions, and permissions remain upstream authority; unspecified routine choices are resolved automatically without a confirmation stop.++> Mnemonic — restaurant contract: the customer supplies initial ingredients and the desired dish; Strategist plans the dish and prepares the complete mise en place; Executor cooks from that prepared inventory. “Mapo tofu” cannot become tomato-and-eggs or tofu soup, while “a tofu dish” leaves deliberate in-class freedom. Equally: the plan is the general contractor — materials, structure, and a first blueprint; Executor is the crew that builds the finished work on that structure, adapting to the site.++**Review gate**: treat any prompt refactor that erases the selected profile's ownership chain, moves acquisition into the default-pipeline Executor, turns a permission into a quota, or turns flexible realization into silent resource/identity reselection as a semantic regression even when the compressed wording is shorter.diff --git a/docs/rules/prompt-layers.md b/docs/rules/prompt-layers.mdindex a634e045..9b7b94e3 100644--- a/docs/rules/prompt-layers.md+++ b/docs/rules/prompt-layers.md@@ -2,7 +2,7 @@> Which content belongs in a prompt file at all, and where each kind lives. Applies to every file the runtime loads: `skills/ppt-master/references/`, `skills/ppt-master/workflows/`, `skills/ppt-master/templates/*.md`, `SKILL.md`, and `AGENTS.md`. [`prompt-style.md`](prompt-style.md) governs how those files are written; this rule governs what goes into them.-The prompt files are read by a model before it plans a deck and hand-writes SVG slides. Everything in them competes for the model's attention with the design decisions it is about to make. A paragraph earns its place only by being one of the first two kinds below.+The prompt files are read by a model before it plans a deck and hand-writes SVG slides. Everything in them competes for the model's attention with the design decisions it is about to make. A paragraph earns its place only by being craft, minimal contract, or the owning statement of a procedure; the fourth kind never enters a prompt file.---@@ -12,7 +12,8 @@ The prompt files are read by a model before it plans a deck and hand-writes SVG|---|---|---|---|| **Craft** — design judgment | Changing it changes what the page looks like or says | The prompt file of the phase that makes the decision, once | The Visual Job Router, the elevation table and one-light-source default, overlay recipes, the contour-before-encoding gate, the communication-contract table, the cover and closing rules || **Contract** — minimal form | The one canonical form the model must write, plus a boundary the tools cannot enforce | Beside the craft that uses it, as one example and one line | One XML example per effect; "a gradient stroke needs a path with both width and height"; "never put `filter` and `clip-path` on the same `<image>`" |-| **Tool documentation** — converter and importer behavior | The checker or exporter already enforces it, or it describes import/normalization/`--strict` behavior, or it restates a procedure another phase owns | `skills/ppt-master/scripts/docs/`, never a prompt file | Accepted-but-warned spellings, DrawingML numeric ranges, crop-transport quantization, closed transform/path grammars, server lifecycle, sidecar schemas |+| **Procedure** — what to run, in what order, with which gate | It is a step, command, gate, or checkpoint of one route or stage, and the model executes it rather than judges it | The route authority or stage runbook that owns that step, once; every other file points to the step | `project_manager.py init` in Generate Step 2, the early/final gate commands and their cadence, the confirm-server launch/wait/shutdown sequence, `[TEMPLATE_BRIEF_CONFIRMED]` |+| **Tool documentation** — converter and importer behavior | The checker or exporter already enforces it, or it describes import/normalization/`--strict` behavior, or it restates a procedure another file already owns | `skills/ppt-master/scripts/docs/`, never a prompt file | Accepted-but-warned spellings, DrawingML numeric ranges, crop-transport quantization, closed transform/path grammars, server lifecycle, sidecar schemas |**Hard rule — enforced grammar is not prose**: a rule that `svg_quality_checker.py` or `svg_to_pptx` preflight already rejects needs nothing in the prompt beyond its canonical form. The failing check teaches the boundary at the moment it matters, with the exact message; a paragraph read before authoring cannot compete with that.@@ -24,16 +25,18 @@ The prompt files are read by a model before it plans a deck and hand-writes SVG| Location | Holds | Loaded by ||---|---|---|-| `references/<role>*.md`, `workflows/**.md` | Craft and contract, one owner per rule, organized by the phase that decides it (Plan: Strategist and the Generate Steps 1–5 / Quick §2; Do·Check·Act: Executor and Steps 6–7 / Quick §3–4 — see [`SKILL.md`](../../skills/ppt-master/SKILL.md) Phase Frame) | The runtime load sets in `scripts/prompt_audit_manifest.json` |+| `references/<role>*.md` | Craft and contract, one owner per rule, organized by the phase that decides it (Plan: Strategist / Quick §2; Do·Check·Act: Executor / Quick §3–4 — see [`SKILL.md`](../../skills/ppt-master/SKILL.md) Phase Frame) | The runtime load sets in `scripts/prompt_audit_manifest.json` |+| `workflows/**.md` | Procedure — the route's steps, commands, gates, and checkpoints — plus the craft that only that route decides; the owner of each cross-file rule is recorded in [`rule-owners.md`](rule-owners.md) | The runtime load sets || `scripts/docs/<topic>.md` | Tool documentation. A contract reference that mirrors a prompt file keeps that file's section numbers (`svg-contract.md` §1.1–§2.2 mirror `shared-standards-core.md`, Part II §6.2–§6.10 mirror `svg-effects.md`) so a pointer resolves in either direction | Nobody during generation; `coverage.exempt` in the manifest with a reason || `templates/*_reference.md`, `templates/schemas/*.json` | Artifact grammar the model authors against (`design_spec.md`, `spec_lock.md`) | Read at authoring time by the owning Step |-**Hard rule — contract before craft, both short**: inside a file, and inside-each section, state the contract first — the routing/menu rows and the one-canonical form — then the craft that uses it. A recall index (a routing table,-the Visual Job Router, the everyday device menu) counts as contract: it is the-list of what exists, and it stays at the top because a capability the model-has not seen is a capability it will not use. Anything that is plain SVG or+**Hard rule — recall first, craft second, boundary last**: inside a file, and inside+each section, open with the recall index — the routing/menu rows, the list of+what exists, the one canonical form — then the craft that uses it, and close+with the boundary the tools cannot enforce. A recall index (a routing table,+the Visual Job Router, the everyday device menu) leads because a capability the+model has not seen is a capability it will not use; a boundary trails because a+prohibition read before the capability crowds it out. Anything that is plain SVG orXML behavior — what `<use>` does, what a path command means, that a transformcomposes — gets one line or nothing; the model knows SVG, and the prompt onlyrecords where this pipeline departs from it. Craft is written as the decision@@ -65,6 +68,7 @@ Run this procedure paragraph by paragraph; do not classify by section heading.## 4. What this rule does not permit-- Deleting craft to hit a token target. The ceiling in [`prompt-style.md`](prompt-style.md) §4.1 is met by moving the other two kinds, never by thinning design judgment.+- Deleting craft to hit a token target. The ceiling in [`ownership.md`](ownership.md) is met by moving the other kinds, never by thinning design judgment.+- Compressing several rules into one sentence to save lines. Length is counted in decisions per paragraph ([`prompt-style.md`](prompt-style.md) §3.1); a long sentence with nested exceptions is bloat in a different shape.- Turning a `Hard rule` into a pointer to a tool document when no tool enforces it.- Restating a moved rule "briefly" in the file it left. Brief restatements are the mechanism that produced the bloat.diff --git a/docs/rules/prompt-style.md b/docs/rules/prompt-style.mdindex ca112aed..8c84e876 100644--- a/docs/rules/prompt-style.md+++ b/docs/rules/prompt-style.md@@ -1,8 +1,8 @@# Reference Document Style Guide-> Style rules for files under `skills/ppt-master/references/`. Follow these when writing or reviewing role definitions and shared specs.+> Style rules for every file the runtime loads: `skills/ppt-master/SKILL.md`, `references/**/*.md`, `workflows/**/*.md`, and `templates/*.md`. Follow these when writing or reviewing role definitions, route authorities, stages, and shared specs. [`prompt-layers.md`](prompt-layers.md) says what may go into such a file; [`ownership.md`](ownership.md) says which role decides it; this file says how it is written.-The reference layer drives runtime LLM behavior. Style consistency across these files matters as much as correctness — divergent voice / structure forces the model to re-interpret each file from scratch and bloats the loaded context.+These files drive runtime LLM behavior. Style consistency across them matters as much as correctness — divergent voice / structure forces the model to re-interpret each file from scratch and bloats the loaded context. The house pattern that has proved readable is the catalog format of `references/visual-styles/*.md`: one file per subject, a fixed section skeleton shared by every sibling, short labelled paragraphs written as positive vocabulary, and one example where a form is easier shown than told.---@@ -53,6 +53,21 @@ Role definition for the **web image acquisition path**: translate Strategist int**Hard rule — retain failure predicates**: Cut narrative teaching and background motivation. Keep one compact protected invariant or failure predicate when it determines the rule's strength, scope, or safe generalization; attach it to the rule or one `> Note` line. Runtime prompts need the behavior and its objective failure boundary, not the full rationale.+### 3.1 One Rule per Sentence++A sentence states one rule. An exception is its own sentence, or a row in a table; it is never a clause nested inside the rule it qualifies. A labelled paragraph states one decision in roughly sixty words or fewer; a second decision starts another labelled paragraph or a table row. When a rule needs three or more cases (`never X unless Y, and only when Z`), write the cases as a two-column table. Concision is measured in decisions per paragraph, not words per sentence: a compression pass that folds several rules into one long sentence has made the file harder to follow, not shorter.++❌ Avoid: a 100-word sentence that names the rule, two exceptions, the owning file, and the fallback.+✅ Prefer: the rule in one sentence; the exceptions as a table; the owning file as one pointer.++### 3.2 Pointers Name the File to Open++A pointer exists so the model knows which file to read next — `[`svg-effects.md`](./svg-effects.md) §6.4` — and appears where that reading is needed. Ownership bookkeeping written for the maintainer ("owned by", "belongs to", "lives in", "is not restated here") does not belong in a prompt file; the owner of every cross-file rule is recorded once in [`rule-owners.md`](rule-owners.md).++### 3.3 One Meaning per Term++Every term used in a rule has exactly one meaning across the loaded corpus, defined once in the vocabulary section of [`SKILL.md`](../../skills/ppt-master/SKILL.md) or in the section that owns it. Do not give an existing term a second meaning; when two concepts share a word, rename one (record the rename in [`rule-owners.md`](rule-owners.md) with every file it touches). A term used in a `Hard rule` or `Mandatory` that no loaded file defines is a defect: the obligation cannot be followed.+---## 4. Bold Inline Labels@@ -95,102 +110,9 @@ Boundary cases go by this test, not by how strong the verb feels: "never split a> Note: only a MUST with a concrete objective trigger may become a `svg_quality_checker.py` rule. SHOULD is at most a `warning`; MAY is never checked — encoding taste as a check turns the checker into a de-facto spec.-### 4.1 Ownership Contract: Ingredients → Plan + Preparation → Realization+### 4.1 Ownership Contract-Constraint strength and decision ownership are independent. Preserve this chain whenever writing, compressing, or reviewing the default multi-role Generate prompts:--| Layer | Owns |-|---|---|-| User / initial materials | Supplied facts/assets, desired outcome, exclusions, and permission boundaries remain authoritative |-| Strategist / plan + preparation | Assess material sufficiency; trigger permitted topic research and retain its research/provenance pair without expanding adopted webpage URLs; decide the approved content, resources, keys, identity anchors, and exact page roster; record each page's semantic units and their source-stated relationships. While composing the roster, decide which pages need a prepared image, lettering, or illustrated-icon resource and derive the external-resource rows from that need. Sketch macro composition, visual focus, and continuity as Reference when useful, without selecting a carrier mix, a local authoring capability, or element geometry; materialize the planned project-local inventory or record an explicit `Needs-Manual` dependency before execution. For icons, prepare a curated project pool with broad semantic fit rather than assigning files to pages |-| Executor / realization | Use only prepared project-local assets; preserve approved content, relationships, resources, and identity anchors; realize each page by resolving the actual carrier combination, geometry, composition, hierarchy, and treatment together before coordinates — the carrier mix has no upstream owner. Discover and invoke local deterministic authoring capabilities without an upstream capability selection. Treat every Reference as a starting sketch to adjust freely for the page's purpose; follow a `(binding)` field literally. For icons, the complete `<project>/icons/` pool is prepared material; `icons.inventory` is a curated bundled-pool index, not a page-use plan or whitelist, and Executor chooses prepared icons per page without a coverage quota. Sparse local font/color garnish is allowed only while non-structural and non-recurring |--**Hard rule — three ownership tiers**: classify a decision before writing any-rule about it, and keep each tier's rules in its own role's files.--| Tier | Test | Examples | Contract |-|---|---|---|---|-| Plan-only | Needs a prepared file before authoring; holds only across the whole roster; needs one user confirmation; or comes from source semantics | Contract, canvas, page count, roster ids/order, `page_rhythm`, identity anchors (color, type, spacing, icons, style, mode), resources, per-page content, facts, semantic units and their relationships | Execution never reopens or substitutes it; a misfit returns upstream |-| Execution-only | Judged only with the objects on the canvas | Carrier mix, geometry and native contours, composition, coordinates, spacing, hierarchy treatment, effects, per-page icon and image treatment, wrapping | Plan writes no detail here, not even as advice |-| Reference (grey zone) | Useful as a first sketch, decidable either way | Macro composition and focus, continuity and motif, cover/closing composition, Chart/Table `family/key`, image `Layout pattern`, motion suggestions | Plan writes a starting sketch; Executor adjusts or replaces it freely for the page's purpose, with no upstream repair and no stated reason. It carries no binding semantics — anything that must hold is written in a plan-only field. It binds only when labeled `(binding)` because the user, a template, or a resource contract requires that property (explicit *must* / *only* / *exactly* / *verbatim*); Executor then follows it literally |--Depth test: one plan given to two competent Executors yields the same content-with different looks — converging looks mean the plan wrote execution,-diverging content means it left semantics open. `design_spec_depth` changes-only wording completeness and Reference length, never which plan-only fields-are written.--**Hard rule — capability knowledge precedes selection**: a role must know that-a capability exists before choosing among capabilities; otherwise a load trigger-circularly depends on a choice made without that capability. The always-read-core of the authoring role therefore carries the recall of every construction-capability — the everyday device menu and effects, the complete preset-vocabulary, the Structure decision, and one routing row per deeper module —-while the deeper module itself (effects beyond the everyday block, native-shape-authoring, relationship grammar and topology assembly, and the rarer formula,-hyperlink, chart/table, structured-template, video, animation, and web-image-files) is loaded when its observable trigger appears — evaluated once over the-whole roster before P01, or at the page that first reaches an unforeseen-capability — read completely, and kept for the run. The owning rule is-[`prompt-layers.md`](prompt-layers.md) §2.--**Hard rule — core volume ceiling**: the always-read core of an authoring role-stays small enough that its own content is not diluted by what follows. Measured-against the v2.13.0 baseline, an Executor-phase core of roughly 1,300 lines-across a role file plus a shared technical file produced richer pages than a-4,000-line, 12-file mandatory bundle; the larger bundle flattened expression-while passing every structural gate. Treat that as the working ceiling. When a-core grows past it, shrink it by removing what is not authoring guidance or by-moving a deeper module behind a trigger whose recall stays in the core. What may stay in a-prompt file at all — craft, minimal contract, or tool documentation — and the-procedure for moving content out are owned by-[`prompt-layers.md`](prompt-layers.md).--Default Strategist's planning bundle covers resource/preparation and high-level-expression options without local authoring parameters, because those choices are-persisted into artifacts other roles consume. Only post-selection mechanics whose-trigger is independently observable stay conditional: an actual `ai` / `slice`-resource row triggers Image_Generator backend, prompt-assembly, and per-image-type details after planning, and those mechanics are not a missing Strategist-capability.--**Hard rule — native shapes are authoring capabilities, not prepared-resources**: a prepared resource needs a stable project-local file/path before-realization because page authoring cannot acquire or generate it in place.-Office presets, SVG primitives, Connectors, Boolean helpers, and necessary-freeform geometry are locally callable construction capabilities. Strategist-never inventories them or promotes a concrete preset, primitive, Connector,-Boolean/freeform operation, or authoring parameter into a binding planning-selection. A macro Reference may mention a technique as optional inspiration-without prescribing or gating construction. The Design Spec / lock create no-native-shape field; Executor reads the complete current preset vocabulary and-chooses the page-fit construction during realization.--**Preparation timing**: In the default pipeline, topic research and import of-its two-artifact research pair may run before final confirmation. Facts JSON-URLs are not auto-expanded. AI / web / slice acquisition runs only from the-completed `design_spec.md §VIII` and `spec_lock.md`, after final confirmation-and before Executor. Only after normal image search fails may one relevant-adopted page become a Markdown + companion-image source package; review it and-promote accepted files individually, never the whole package. Image_Generator,-Image_Searcher, and icon-sync tooling execute Strategist-owned preparation;-they are not independent decision owners.--**Post-motion sound exception**: optional transition/object sound is not a-page-authoring ingredient and never enters Strategist planning,-`design_spec.md`, or `spec_lock.md`. After the SVG roster and visual motion-solution are complete, the active animation/export stage may discover bundled-sound ids and sync only a concretely selected cue into the project. With no-selected cue, it creates no `<project>/sounds/` directory. This exception does-not permit Executor to acquire visual resources.--**Hard rule — default pipeline**: downstream freedom exists in every dimension the plan leaves open, and every Reference is open by definition. A named binding outcome retains identity; a broad semantic request or expression recommendation permits in-class choice. Once the plan resolves a plan-only choice or a `(binding)` Reference, execution cannot reopen or substitute it. For icons, library/stroke and the prepared-project boundary bind, while per-page choice within the prepared pool is realization. Executor never searches, generates, downloads, syncs, invents, or replaces a resource; missing material returns to Strategist-owned preparation or upstream repair.--**Explicit Quick Generate exception**: [`quick-generate`](../../skills/ppt-master/workflows/profiles/quick-generate.md) removes the separate Strategist/confirmation handoff. The current main agent therefore owns both its active-context decisions and the preparation of project-local sources, images, icons, and provenance before it begins SVG realization; native formulas are authored directly from exact mathematical content rather than acquired as resources. This exception does not move acquisition into a default-pipeline Executor and does not permit resource reselection while a page is being realized. Explicit user facts, choices, exclusions, and permissions remain upstream authority; unspecified routine choices are resolved automatically without a confirmation stop.--> Mnemonic — restaurant contract: the customer supplies initial ingredients and the desired dish; Strategist plans the dish and prepares the complete mise en place; Executor cooks from that prepared inventory. “Mapo tofu” cannot become tomato-and-eggs or tofu soup, while “a tofu dish” leaves deliberate in-class freedom. Equally: the plan is the general contractor — materials, structure, and a first blueprint; Executor is the crew that builds the finished work on that structure, adapting to the site.--**Review gate**: treat any prompt refactor that erases the selected profile's ownership chain, moves acquisition into the default-pipeline Executor, turns a permission into a quota, or turns flexible realization into silent resource/identity reselection as a semantic regression even when the compressed wording is shorter.+Decision ownership across plan, execution, and the Reference grey zone — the ingredients → plan + preparation → realization chain, the three ownership tiers, the capability-before-selection rule, the core volume ceiling, preparation timing, and the review gate — is owned by [`ownership.md`](ownership.md). Classify a decision there before labeling its strength here.### 4.2 Admission Criterion for Prohibitions@@ -311,18 +233,19 @@ Items are evidence-driven (`file exists at path X`, `status N is Generated`), no----## 12. When This Guide Conflicts With Existing Files+## 12. Exemplars-Existing files take precedence as ground truth. If a current `references/*.md` violates a rule here, decide whether to (a) update this guide to match the de facto convention, or (b) refactor that file. Don't silently apply a divergent style to one new file.+This guide is prescriptive. A file that violates a rule here is refactored toward the rule; the rule changes only through an explicit decision recorded in the commit, never by treating the divergent file as the new convention.-The canonical exemplars to model new files after:+The canonical exemplars to model new or rewritten files after:| If you're writing... | Model after ||---|---|-| A role reference (Image_X / Strategist-style) | [`image-searcher.md`](../../skills/ppt-master/references/image-searcher.md), [`strategist.md`](../../skills/ppt-master/references/strategist.md) |-| A shared spec across roles | [`image-base.md`](../../skills/ppt-master/references/image-base.md), [`shared-standards-core.md`](../../skills/ppt-master/references/shared-standards-core.md) |-| A technical / format spec | [`canvas-formats.md`](../../skills/ppt-master/references/canvas-formats.md), [`svg-image-embedding.md`](../../skills/ppt-master/references/svg-image-embedding.md), [`image-layout-spec.md`](../../skills/ppt-master/references/image-layout-spec.md) |-| Stage runbook | [`workflows/stages/verify-charts.md`](../../skills/ppt-master/workflows/stages/verify-charts.md) |+| A catalog entry (one style, mode, rendering, type) | [`visual-styles/swiss-minimal.md`](../../skills/ppt-master/references/visual-styles/swiss-minimal.md), [`modes/pyramid.md`](../../skills/ppt-master/references/modes/pyramid.md) |+| A construction module loaded on a trigger | [`executor-structure.md`](../../skills/ppt-master/references/executor-structure.md), [`native-formula.md`](../../skills/ppt-master/references/native-formula.md) |+| A technical / format spec | [`canvas-formats.md`](../../skills/ppt-master/references/canvas-formats.md), [`semantic-svg.md`](../../skills/ppt-master/references/semantic-svg.md) |+| A route authority | [`workflows/edit-native-pptx.md`](../../skills/ppt-master/workflows/edit-native-pptx.md) |+| Stage runbook | [`workflows/stages/verify-charts.md`](../../skills/ppt-master/workflows/stages/verify-charts.md), [`workflows/stages/web-image-review.md`](../../skills/ppt-master/workflows/stages/web-image-review.md) |---@@ -339,6 +262,7 @@ Prompt compression is complete only after reviewing token reduction and semantic| Preparation timing | Strategist-owned acquisition and materialization did not move into Executor or before final confirmation || Capability discovery | Conditional deep specifications retain a short visible menu or an externally observable trigger before their load gate || Token delta | Report route/file budget changes separately; a budget pass does not prove semantic equivalence |-| Restriction census | Before each release, enumerate every `Hard rule` / `Mandatory` / `never` / quota in the Generate load sets (`route.generate.*`, `stage.generate.*` in `scripts/prompt_audit_manifest.json`) and classify each as EXPORT, SCRIPT-ENFORCED, PROCESS, or STYLE; Hard-rule counts are justified only by §4.2 mechanism citations; STYLE prohibitions are removed (capability entry, Reference, or example), and SCRIPT-ENFORCED prose keeps only the fix |+| Owner registry | Every cross-file rule the edit touches has one owner entry in [`rule-owners.md`](rule-owners.md); the other files carry a pointer, not a paraphrase. A new paragraph that restates an owned rule is the regression this table exists to catch |+| Restriction admission | Every `Hard rule` / `Mandatory` / `never` / quota the edit adds or keeps cites its §4.2 mechanism; a STYLE prohibition is removed (capability entry, Reference, or example), and SCRIPT-ENFORCED prose keeps only the fix |**Hard rule**: A shorter prompt that changes decision ownership, constraint strength, preparation timing, or capability discoverability is a semantic regression even when structural and token-budget audits pass.diff --git a/docs/rules/rule-owners.md b/docs/rules/rule-owners.mdnew file mode 100644index 00000000..41190e08--- /dev/null+++ b/docs/rules/rule-owners.md@@ -0,0 +1,44 @@+# Rule Owners++> Registry of every rule that more than one runtime file needs. Each rule has exactly one owner section, stated in full there; every other file in the "pointer only" column carries a one-line pointer to that section and no paraphrase. When a report-driven fix touches one of these rules, edit the owner, not the file where the report was noticed. When a new cross-file rule appears, add a row before writing the rule a second time. [`prompt-layers.md`](prompt-layers.md) §2 owns the one-owner principle; this file is its index.++## 1. Rules shared by Default and Quick++| ID | Rule (one line) | Owner | Pointer only |+|---|---|---|---|+| R01 | Final carrier-receipt review and "absence needs a reason": compare `[CARRIERS]` with retained page jobs, resource roles, and geometry signatures; a deck-wide zero or an under-carried relationship needs one stated reason per family or page | `references/executor-base.md` §3 Checkpoints | `workflows/generate-pptx.md` Step 6, `workflows/profiles/quick-generate.md` §4 |+| R02 | Checker cadence: every checker invocation follows a gate point whose pages all exist, or the end of one consolidated repair pass; early gate after P05 on rosters of seven or more pages | Default: `workflows/generate-pptx.md` Step 6; Quick: `workflows/profiles/quick-generate.md` §3 | `references/executor-base.md` §3 ("owned by the route"), the route completion checklists (ticks only) |+| R03 | Page SVG is hand-written by the current main agent; helpers emit fragments only after the agent chooses role, operands, paint, and z-order | `references/executor-base.md` §3 Technical contract | `workflows/generate-pptx.md`, `workflows/profiles/quick-generate.md` |+| R04 | Module loading: evaluate every routing trigger once over the roster before P01, read triggered modules in one batch, read an unforeseen module at the page that reaches it, write the per-page module line | `references/executor-base.md` routing table + §3 Checkpoints | `workflows/generate-pptx.md` Step 6, `workflows/profiles/quick-generate.md` §3, `references/shared-standards-core.md` routing table (non-Generate triggers only), `references/shared-standards.md` |+| R05 | Text width is calibrated once before P01 (`text_measure.py calibrate`) and estimated per role afterwards; no per-page measuring; never trim wording to satisfy an estimate | Default: `workflows/generate-pptx.md` Step 6 Design Parameter Confirmation; Quick: `workflows/profiles/quick-generate.md` §3 Typography | `references/executor-base.md` §3 bounds paragraph |+| R06 | Reference vs `(binding)`: a Reference is a starting sketch Executor adjusts freely without upstream repair or stated reason; `(binding)` is followed literally and appears only when the user, a template, or a resource contract requires the property | Plan side: `references/strategist.md` §1 Confirmed-value table; execution side: `references/executor-base.md` §2.1; artifact grammar: `templates/design_spec_reference.md` §2.4 | `references/strategist.md` Authority chain and §6.2, `references/artifact-ownership.md`, `docs/rules/ownership.md` (rule definition, not a runtime file) |+| R07 | Reading mode (`text` / `balanced` / `presentation`): what each carries on the page and in notes | `references/strategist.md` §6.1 table | `references/strategist.md` §c, `references/executor-base.md` §2.1 (per-page consumer line), `templates/design_spec_reference.md`, `references/executor-notes.md` §3 |+| R08 | Prose vs bullets: the semantic relationship chooses the form; bullets only for genuinely parallel or ordered material, never because a list is easier to lay out or a template exposes a list slot | `references/strategist.md` §6.1 Per-block expression | `references/executor-base.md` §2.1 authored texture (consumer: adapt within the page) |+| R09 | Font-size anchor band: a structural role uses its anchor or a value within ±2 px; a short non-structural display size may stay undeclared for at most two occurrences, the third needs a named role | `templates/spec_lock_reference.md` §6 | `references/strategist.md` §g, `references/executor-base.md` §2.1, `templates/design_spec_reference.md` §2.2, `references/executor-structured.md` §1.0, `references/visual-review.md` §0 |+| R10 | Font delivery target: an explicit user/template target, otherwise Windows PowerPoint; the authoring host's fonts never select a face; fonts are not embedded | `references/shared-standards-core.md` §4.1 | `references/strategist.md` §g, `workflows/profiles/quick-generate.md` §2 and §3, `references/executor-base.md` §5 |+| R11 | Icon library: one primary bundled stylistic library per pool; `simple-icons` for real brand marks only, never a confirmation choice; search by drawable object; complete case-sensitive `library/name` | `templates/icons/README.md` | `references/strategist.md` §f (confirmation procedure only), `references/executor-base.md` §4 (authoring syntax only), `templates/design_spec_reference.md`, `templates/spec_lock_reference.md` §4, `references/artifact-ownership.md` |+| R12 | Sound: selected only after the visual motion solution is final, from the complete vocabulary, one exact id, synced with `sound_sync.py`; no cue means no `sounds/`; never a planning resource | `references/animations.md` §2.2 | `workflows/stages/customize-animations.md` §3.3, `workflows/generate-pptx.md` Step 7.3, `workflows/profiles/quick-generate.md` §4, `templates/sounds/README.md`, `templates/README.md`, `docs/rules/ownership.md` |+| R13 | Chart/Table reference is a flexible page-local construction reference, never a type/geometry/style lock; native readiness is a separate per-object decision; `--native-charts-and-tables` is a second opt-in | Execution: `references/executor-visualization.md` §2; native marker contract: `references/native-data-interface.md` §2; planning: `references/strategist.md` Resource Need | `references/executor-chart.md`, `references/executor-table.md`, `templates/charts/README.md`, `templates/tables/README.md`, `templates/VISUALIZATION_TEMPLATE_AUTHORING.md`, `workflows/profiles/quick-generate.md` §2, `templates/design_spec_reference.md`, `templates/spec_lock_reference.md`, `scripts/docs/visualization-recall.md` |+| R14 | Motion is authored as page states (two pages for a continuous action); effects, pairing, order, and timing are post-processing; a §IX Motion suggestion never activates the custom stage | `references/animations.md` capability menu + §2.1 | `references/executor-base.md` §1, `references/executor-image.md`, `workflows/generate-pptx.md` Step 6, `workflows/profiles/quick-generate.md` §1, `workflows/stages/customize-animations.md` When to Run |++## 2. Planning-side rules (Default)++| ID | Rule (one line) | Owner | Pointer only |+|---|---|---|---|+| R20 | Three-direction construction: author three whole-solution intents first, freeze every basis id from the three indexes, read once only the deduplicated detail files, a novel custom reads none | `references/strategist.md` §d Hard rule | `references/strategist.md` §1 first paragraph, Layer 1 / Layer 2 GATEs, §2; `workflows/generate-pptx.md` Step 4; `references/modes/_index.md` §1/§3, `references/visual-styles/_index.md` §1/§4, `references/image-renderings/_index.md` §1 |+| R21 | Stage 1 is template-independent: authored from request, sources, and initialization only; no candidate, index, spec, or prototype is evidence | `workflows/generate-pptx.md` Step 4 | `references/strategist.md` §1, `references/strategist-template.md` §1, `references/confirm-surface.md` §2, `scripts/docs/confirm_ui.md` |+| R22 | Template discovery reads only the four `*_index.json` files; never scan kind directories; a bare name never resolves to a path; one root per kind, Layout precedes Deck | `workflows/routing.md` §7 | `workflows/generate-pptx.md` Step 3, `workflows/stages/apply-template-workspace.md` §1, `templates/README.md`, the four kind READMEs, `references/artifact-ownership.md`, `references/strategist-template.md` |+| R23 | Resource need is decided while composing the roster: which pages need a prepared image, lettering, or illustrated-icon file; the carrier mix itself is never planned | `references/strategist.md` Resource Need and Reference Planning | `workflows/profiles/quick-generate.md` §2 (until plan-core exists), `references/strategist-image.md` §1 |+| R24 | Whole-roster rhythm check: neighbors and section arcs compared, chapter entries reset, same-density runs intentional, motif carries a continuity job | `references/strategist.md` §6.2 | `workflows/profiles/quick-generate.md` §2 (until plan-core exists) |++## 3. Structured-template rules++| ID | Rule (one line) | Owner | Pointer only |+|---|---|---|---|+| R30 | Slot contract: a slot is one direct root `<g id>` with `data-pptx-placeholder`, positive design-zone `data-pptx-bounds`, and exactly one compatible `data-pptx-carrier` child; `object` + `proxy` for composites; zero-slot Layouts valid; ordinary Master/Layout `<g>` forbidden with the compact preset `<g>` as sole exception | `references/pptx-structure-interface.md` §2 | `references/semantic-svg.md` §2–§3 (canonical forms only), `references/executor-structured.md` §1.2, `references/template-designer.md` §2.2, `workflows/create-template.md` Step 4/5, `workflows/stages/apply-template-workspace.md` §3, `templates/layouts/README.md`, `templates/decks/README.md`, `scripts/docs/svg-pipeline.md` (exporter behavior may restate) |+| R31 | Legacy structured contracts (`baseline`, `template`, `preserve`, `layout_strategy`, `data-pptx-layout-kind`, `distilled` / `utility`, direct atomic placeholders) are never upgraded in place; create a new workspace | `references/pptx-structure-interface.md` §3 | `workflows/routing.md` §4, `references/executor-structured.md`, `references/strategist-template.md`, `workflows/stages/apply-template-workspace.md`, `references/artifact-ownership.md`, `scripts/docs/svg-pipeline.md` |+| R32 | Mirror preserves the reachable Slide → Layout → Master chain, text-node topology, placeholder facts, and similar presentation; it never synthesizes, renames, re-parents, or redesigns | `references/template-designer.md` Mirror mode | `workflows/create-template.md` Step 1A/1B/4, `workflows/create-template/create-layout.md`, `workflows/create-template/create-deck.md`, `references/executor-structured.md` §1.1 |++## 4. Term renames (recorded here when decided)++No rename has been decided yet. Candidates and the files each would touch are listed in the maintainer notes for the 2026-09 readability pass; a rename enters this table only with its complete file list and the code it changes.diff --git a/skills/ppt-master/SKILL.md b/skills/ppt-master/SKILL.mdindex 87852055..d31311df 100644--- a/skills/ppt-master/SKILL.md+++ b/skills/ppt-master/SKILL.md@@ -70,6 +70,30 @@ in the selected runtime authority's construction references.---+## Vocabulary++One meaning per term across every loaded file. Where a word is used in+more than one sense, the sense is named here and the files say which one.++| Term | Meaning |+|---|---|+| **Reference** (label) | A starting sketch the executing role adjusts or replaces freely, with no upstream repair or stated reason; `(binding)` after a field label removes that freedom |+| **Relationships** | The §IX line naming a page's semantic units and their source-stated `order` / `link` / `parent` / `membership` / `contrast` / `overlap`, or `none` |+| **Structure decision** | The per-page yes/no on whether geometry must carry the page's `Relationships`; unrelated to `pptx_structure.mode` |+| **`pptx_structure.mode`** | `flat` (every object Slide-local) or `structured` (declared Master/Layout/slot metadata); a packaging route, never information structure |+| **Layout** | Three senses: the §IX `Layout` line (a Reference for macro composition); a PowerPoint Layout under a Master; the Layout template kind. `Layout pattern` is the §VIII image-composition suggestion |+| **Device** | An everyday page carrier — card, band, icon-and-label, KPI tile, divider, quote block — recalled in the Executor's device menu |+| **Carrier** | Two senses: the content carrier a page unit sits in (a device, an image, native geometry), and the `data-pptx-carrier` child of a structured slot. The **carrier receipt** is the checker's per-page inventory of what was actually drawn |+| **Page job** | What one page must do for the reader; the input every carrier, contour, and effect decision is judged against |+| **Page field** | One large surface, outline, aperture, or off-canvas contour that organizes zones instead of a card per unit |+| **Contour / preset / atom** | A contour is a shape's silhouette; a preset is one of the 187 Office `prst` contours drawn through `preset_shape_svg.py`; an atom is one object that compiles to one DrawingML shape |+| **Geometry signature** | The retained line `page job → composition move → contour / edge language` kept per page and compared before the next page |+| **Texture** (of a block) | Whether a §IX block is prose, bullets, keywords, or labels; distinct from visual texture (grain, halftone) |+| **Anchor** | Two senses: a lock anchor (a deck-wide color, type, or spacing value) and the `page_rhythm` tag `anchor` for structural pages |+| **Sheet / slice / plate** | A sheet is one generated image holding several elements on a chroma key; a slice is one element cut from it; a plate is a registered full-canvas layer of several non-overlapping objects |+| **Module line** | The `P<NN> modules: …` line written before each page naming the triggered modules it uses |+| **Mode** | Named by qualifier: communication `mode` (how the deck argues), reading mode (`consumption_mode`), `generation_mode` (`continuous` / `split`), `pptx_structure.mode`, `replication_mode` (how a template was created) |+## Phase FrameEvery route is one Plan → Do·Check·Act cycle: Plan ends when every authoringdiff --git a/skills/ppt-master/references/native-shape-authoring.md b/skills/ppt-master/references/native-shape-authoring.mdindex e63a46f3..dea8e59b 100644--- a/skills/ppt-master/references/native-shape-authoring.md+++ b/skills/ppt-master/references/native-shape-authoring.md@@ -89,7 +89,7 @@ python3 ${SKILL_DIR}/scripts/shape_boolean_svg.py render <svg-file> \At topology scale, independent pieces, one body with dividers, overlapping siblings, fitted joints, intentional gaps, and retained `fragment` regions are common strategies, not a set; never map a topology name to a shape list or infer equal size or spacing.-**Default — running deck geometry check (may override for literal pages or isolated prototypes)**: after each page retain `page job → composition move → contour / edge language` (plus `relationship → topology` for `Structure=yes`) and compare before the next; repeat only for the same job / relationship or deliberate continuity — section, equal weight, style, and precedent are insufficient. No artifact, no second pass.+**Default — running geometry signature (may override for literal pages or isolated prototypes)**: the *geometry signature* of a page is the retained line `page job → composition move → contour / edge language` (plus `relationship → topology` for `Structure=yes`). After each page retain its signature and compare it with the previous pages' before drawing the next; repeat a signature only for the same job / relationship or deliberate continuity — section, equal weight, style, and precedent are insufficient. The final carrier-receipt review reads these signatures back. No artifact, no second pass.**Boolean decision gate**:diff --git a/skills/ppt-master/scripts/prompt_audit_manifest.json b/skills/ppt-master/scripts/prompt_audit_manifest.jsonindex 305bcd57..b1d9c730 100644--- a/skills/ppt-master/scripts/prompt_audit_manifest.json+++ b/skills/ppt-master/scripts/prompt_audit_manifest.json@@ -17,7 +17,7 @@},"file_budgets": {"AGENTS.md": 3250,- "skills/ppt-master/SKILL.md": 1750,+ "skills/ppt-master/SKILL.md": 2500,"skills/ppt-master/references/executor-base.md": 11000,"skills/ppt-master/references/executor-structured.md": 5500,"skills/ppt-master/references/executor-chart.md": 1750,