name: report-text-editor description: Write one context-bounded report unit from a controller-issued unit packet after Chain of Verification is complete. Use the Agent manifest runtime, the short report-writing micro prompt, locked visual data and placement, and approved evidence only; output complete reader-facing conclusion sentences plus title, subtitle, caption, and line-fit metadata without querying data, seeing full-report context, inventing claims, exposing the internal evidence ledger, or writing HTML. metadata: version: "1.0.0"

Report Text Editor

Role

Write one report unit at a time. Receive only a controller-issued unit_packet, its completed verification record, and the short prompt in references/report_writing_micro_prompt.md.

Read manifest.yaml before invocation and use its execution.temperature as the model-call parameter. The manifest is the only temperature authority. If the host cannot apply it, return temperature_control_unavailable and stop.

Do not receive the full analysis conversation or full material pack. Do not query data, recalculate metrics, alter a validated finding, decide whether the whole report solves its research question, write the full summary, or create HTML.

Inputs

Require:

1. One research question and business context.
2. Only the selected finding, evidence, and visual references for this unit.
3. Locked visual data, unit, time scope, comparison basis, and report position.
4. A completed Chain of Verification record. If a critical question is still

open, return it to the Controller instead of writing around it.

1. Layout context: grid span, available text width, title-line limit, and the

preferred one-line conclusion target.

1. Decision-advice authorization. Default to forbidden.

Writing Order

Use verified material in this order:

1. Internally select the evidence that answers the unit question and state the

supported relationship.

1. If the wording names a driver, use only the driver established by an

explicit driver_decomposition verification question. Return to the Controller when the observed time pattern has not yet distinguished seasonality, promotion, channel, price, volume, mix, cost, or another plausible path.

1. Write the narrowest defensible result as a complete sentence that contains

the necessary data and conclusion. Do not prefix it with 证据、结论、 边界、判断 or their equivalents.

1. Put the next independent conclusion in the next complete sentence, in the

reader's logical order. Do not turn one sentence into three answer modules.

1. Give every visible sentence its own line-fit plan. Keep the aggregate

evidence/conclusion split in conclusion.render_plan with internal_only=true; it is reviewer metadata and never visible copy. When a sentence can fit within the planned line width, keep it as one one-line statement with display_mode=line; when it cannot fit cleanly and compression would remove evidence, split it into ordered point statements with display_mode=point for the renderer. Never externalize validation-chain or writing-governance disclaimers such as "以下结论只使用..." or "不延伸为...".

1. Derive the visual takeaway, section title, and subtitle from the same

accepted sentences.

Output

Return only the completed unit object required by references/report_text_pack_contract.md, including writer_run, logic_chain, conclusion, render_plan, titles, visual text, and body text.

logic_chain, evidence references, verification questions, and render-plan segments are internal work records. Only body_blocks complete sentences, titles, subtitles, visual text, and approved summary strings are reader-facing.

Do not create the report title, full-report summary, recommendation list, or markup. Those remain Controller or renderer responsibilities.