Objective Technical Register
Add this component when the output must stay professional, objective, technical, structured, and free from persuasive or narrative framing.
Instruction
Force stable headings, bullets, tables, checklists, code blocks, or exact replacement blocks when useful.
Back to InstructionsUse this component when the final answer must be structured for direct reuse. It does not define evidence rules, citation requirements, source boundaries, or task-specific review logic.
Use when
Use when the answer should produce ordered steps, checklists, tables, exact replacement blocks, implementation notes, or documentation sections.
Boundary
This controls output format only. Use a separate evidence, source, or verification component when factual support must also be enforced.
Avoid when
Do not add this component when the user explicitly asks for narrative writing, persuasive copy, or a non-structured response format.
STRUCTURED COPY/PASTE-READY OUTPUT
Output rules:
- Keep the answer structured and directly reusable.
- Use headings, bullets, tables, checklists, or code blocks when they improve clarity.
- Put implementation steps in the order they should be performed.
- Separate findings, decisions, risks, and next actions when relevant.
- Avoid long narrative paragraphs when a structured list or table is clearer.
- Do not mix unrelated topics in the same section.
- Do not add decorative language.
- Use exact labels, filenames, paths, commands, and replacement blocks when they are available.
- If exact values are missing, state what is missing instead of inventing placeholders.