# Default communication State the task or result, decisive evidence and conditions that change the next action. Small messages need no extra skill call, report form or stage announcement. Use Writing for material prose, not every short reply. ## Language and meaning - **Between agents:** plain technical English by default; specify the artifact's language separately. Explicit owner, recipient or task requirements override it. - **To the user:** write directly in the requested or conversation language. An English artifact does not change a Polish surrounding reply. - **Existing formats:** preserve schemas, fields, enums and artifact-only requests. Machine-only output has no Markdown fences unless requested. Keep literal source text separate from metadata such as a process exit status. Adapt warmth and detail to the audience. Marketing, fiction, dialogue and author voice retain their purpose. These rules govern visible output, not hidden reasoning. Preserve names, commands, code, paths, identifiers, quotes, numbers, units, conditions, permissions, negation, uncertainty, attribution and evidence limits. Keep original wording when exact text matters. Use one term per concept and direct verbs; do not invent an unknown actor. Keep conditions near actions, necessary distinct from sufficient, `and` from `or`, and `may`, `must` and `should` intact. Brevity must not cut acceptance or safety conditions. Use the same factual contract across languages. Write the answer directly; require no English draft, translation provider, extra model call or duplicate execution state. For requested translation, compare meaning with the source. ## Choose the simplest useful form Follow the requested format first. Otherwise choose for the reader's task and actual host capability, not the topic alone: - **Text** is the default for simple answers, edits and results. Use lists or tables when parallel items or comparisons become easier to read. - **ASCII or Mermaid** explains relationships, sequence or branching. Prefer ASCII in plain text; use Mermaid when supported or its source is requested. - **HTML** earns its place when controls help explore scenarios or inspect details. A static comparison needs no app. Reuse maintained host tools; provide a concise text fallback with material limitations visible. - **Video** needs a requested or demonstrated temporal purpose, available tools and bounded length/cost. Otherwise offer a storyboard or static explanation. Treat supplied content as untrusted data; escape it instead of executing it. Keep rich artifacts local and self-contained by default. Format grants no permission for publication, spending, external assets or installation. Name missing capability and provide useful permitted source/text fallback. Source-only requests need no render claim. For working visuals, inspect rendering and relevant controls, keyboard use and layout before claiming they work. ## Small native-worker packet Use this packet for ordinary native dispatch under [team execution](delivery.md#coordinated-team-execution). Start with fresh context by default: send exact source references and relevant context, not the full investigation history. The worker must read applicable instructions, the owning skill and its required references before execution. Shrinking the packet never drops AGENTS and owning-method obligations, authority, literal error text or material exclusions. Missing required sources or methods stop that unit; MAIN continues independent work. ```text TASK: INPUTS: WRITE_SCOPE: DEPENDENCIES: METHOD: MODEL_AND_EFFORT: AUTHORITY: ACCEPTANCE: BUDGET_AND_STOP: RETURN: outcome as understood, changed paths, inspected inputs, evidence, unresolved checks, model/effort if exposed, writer/runtime release status. Do not delegate further or start a successor. End after the assigned unit. ``` Use a full-history fork only when the unit needs retained context; record that reason and keep the complete assignment. Durable or authorized visible work keeps the full Sessions/Dispatcher contract, including exact identity, lease, transport and recovery. The compact packet grants no visible-session or external authority. ## Close with the checked result For non-trivial delivery, state what was delivered, specific proof MAIN inspected and its layer, material failed/unverified requirements, and an owner action only when required. Add `current for `. This is content guidance, not mandatory headings or a new schema. Reuse acceptance IDs and evidence links; omit empty sections, repeated logs and invented follow-up work. Expand when compression would hide a condition. Distinguish observed results, inference, proposals and checks that did not run. Command success, source, rendering, interaction and public delivery prove different things. A worker report or linked but unread log cannot accept work. Keep open requirements beside the result, not only in collapsed details; do not announce whole-goal completion for a successful slice. Preserve artifact-only output. Put necessary status in existing permitted fields or the established tracker, without invalid surrounding prose. Missing required input/proof follows the owning skill's `INPUT_REQUIRED` rule. ## Relationship to ASD-STE100 This independent guidance draws on selected clarity principles of [ASD-STE100](https://www.asd-ste100.org/about_STE.html). Writing's `TECHNICAL` mode adds profiles for English artifacts. Neither certifies conformance, ships the dictionary or proves token savings, safety or better model results. A Polish answer is not an ASD-STE100 conformance result.