Integrate confirmed report workflow and review inputs (0.9.0)

2026-10-20 10:25:03 +08:00
parent 3b7de84c49
commit 4729693a9e
9 changed files with 108 additions and 13 deletions
@@ -6,7 +6,7 @@ These rules apply across templates and authoring routes. **Required** rules prot

 - **C01 · Recommended:** consume the supplied audience, purpose, material boundary and page content plan, including the intended understanding, necessary premises and progression within the current page. Establish the production route, template and review rhythm from settled choices. If no plan is provided, form only the brief needed for the current authorized work; substantial report planning and example-derived content rules belong to the optional `report-structure` Skill. See [content handoff](content-handoff.md).
 - **C02 · Required:** preserve facts, numbers, conditions, causal relationships and strength of conclusions. Distinguish source statements, inference and added material. Do not invent unknown values. Identify synthetic examples and retain traceable sources for material claims.
- **C03 · Required meaning and visual correspondence, recommended composition:** preserve the supplied page purpose, intended understanding, evidence and key steps. Make the association between each conclusion and its evidence visible, and check the actual page's progression and necessary context. Choose a suitable composition and reading order for those relationships; concrete layout methods may vary. Do not silently change chapter order or move essential content to notes. Return meaningful omissions, contradictions or capacity conflicts to the content plan; do not create a parallel report-structure rule library. Summarize only within the authorized content scope and without changing meaning; C02 governs required content fidelity.
+- **C03 · Required meaning and visual correspondence, recommended composition:** preserve the supplied page purpose, intended understanding, evidence and key steps. Every text, formula, label, visualization and meaningful decorative group serves the page, section and report goals. Make the association between each conclusion and its evidence visible, and check the actual page's progression and necessary context. Choose a suitable composition and reading order for those relationships; concrete layout methods may vary. Preserve demonstrated contributions and judgments without defaulting to limitations lists or preventive self-doubt. Do not silently change chapter order or move essential content to notes. Return meaningful omissions, contradictions or capacity conflicts to the content plan; do not create a parallel report-structure rule library. Summarize only within the authorized content scope and without changing meaning; C02 governs required content fidelity.
 - **C04 · Recommended:** keep hierarchy, color semantics, terminology, units, legends, strokes, icon grammar and component scale consistent across pages. Use declared template exceptions where needed.
 - **C05 · Recommended:** choose layout and columns from content relationships, then place components. Maintain grouping, alignment, spacing, reading order and moderate density. Add decoration for a purpose. Resolve excess content through the template's rewrite/layout/split policy; keep its declared typography and grid rules.
 - **C06 · Recommended:** inspect suitable components and page-library examples before authoring. Read their rationale and method; adapt, combine or create as needed. Remove example content, update data and metadata, and preserve reference attribution.
@@ -22,7 +22,7 @@ These rules apply across templates and authoring routes. **Required** rules prot

 - **C11 · Required:** implement text, shapes, connectors, tables and charts according to the selected route. Do not claim a full-page screenshot is editable completion. Use supported tools and disclose technical limits; do not silently change backend, depend on another installed Skill or introduce an online provider. [Native objects](native-objects.md) describes actual object support.
 - **C12 · Required:** retain source data, page content/code, notes, assets, generation parameters, template version, environment and necessary metadata. When content changes, synchronize chart cache/workbook, SVG fallback and current previews. Use relocatable project paths. A cached export or final PPTX alone is not a rebuildable project. See [project workspace](project-workspace.md).
- **C13 · Recommended:** complete content, visual and implementation checks at the authorized review granularity. Even an authorized batch needs page checks. Multiple authors share a frozen brief/style; the coordinator checks cross-page progression, terminology and appearance. Revisions preserve premises, key steps, evidence associations and agreed content destinations across source, page and notes. Existing page-by-page authorization remains binding. See [page collaboration](page-collaboration.md).
+- **C13 · Required agreed execution, recommended organization:** follow the once-confirmed review/production/ImageGen choices and selected alternatives; do not silently replace a declined tool or Agent arrangement. Complete content, visual and implementation checks at the authorized granularity. Even an authorized batch needs page checks. Multiple authors share a frozen brief/style/content revision; the coordinator checks cross-page progression, terminology and appearance. Revisions preserve premises, key steps, evidence associations and content destinations across source, page, explanation PDF and notes. Apply the agreed post-revision review, using non-leading inputs and accurately distinguishing independent review from main-Agent self-check or skipped scope. Existing page-by-page authorization remains binding. See [execution and review](execution-and-review.md) and [page collaboration](page-collaboration.md).

 ## Verify, revise and deliver