neqsim-final-report-writing-style

Final Report Writing Style

Choose a writing style only after the calculations, evidence review, and technical conclusions are complete. The selected style controls expression, not facts, scope, uncertainty, or validation.

When to Use

• Activate at the final reporting step when generating an HTML, Word, PDF, Markdown, or notebook report, or a durable generated summary.
• Activate when revising an existing final document for style.
• Activate when the user explicitly requests prose_english or standard_engineering_english for a generated document.
• Do not activate during research, analysis, calculation, source extraction, ordinary chat, interim status messages, code generation, or working notes.

Inputs

• document_purpose: interpret, decide, instruct, specify, describe, or mixed.
• document_sections: the final sections that will be generated.
• audience: decision-maker, engineer, operator, maintainer, regulator, student, or general reader.
• user_requested_style: optional prose_english or standard_engineering_english.
• Mandatory templates, controlled terminology, safety wording, and accessibility constraints.

Outputs

• primary_style: prose_english or standard_engineering_english.
• section_overrides: sections that require the other style, with a short reason.
• selection_reason: one sentence tied to reader purpose and document type.
• Final narrative revised under the selected rules without changing technical content.

When the task uses results.json, record the choice as:

{
  "writing_style": {
    "primary": "prose_english",
    "selection": "automatic",
    "reason": "The report interprets evidence for an engineering decision.",
    "section_overrides": {
      "Operating procedure": "standard_engineering_english"
    }
  }
}

Engineering Method

1. Check for a user request. A valid explicit request sets the primary style.
2. If there is no override, select by the reader's task:
   • Choose prose_english when the reader must understand evidence, compare alternatives, interpret uncertainty, or make a decision.
   • Choose standard_engineering_english when the reader must perform an action, reproduce a method, identify equipment, follow a limit, or interpret a requirement consistently.
3. For a mixed engineering report, use prose_english as the primary style. Apply standard_engineering_english to procedures, requirements, equipment descriptions, warnings, cautions, checklists, and tightly controlled method steps.
4. Mandatory safety, regulatory, contractual, accessibility, and template rules take precedence over either style.
5. Apply the selected style only to narrative expression. Do not alter numbers, units, citations, uncertainty, technical terminology, findings, or the direction of a recommendation.
6. Record the selection and any section overrides so a reviewer can see which rules were applied.