neqsim-prose-english

Prose English

prose_english is the short alias for this style. It turns verified engineering content into clear prose without making the writing sound simplified, promotional, or machine-generated.

When to Use

• Use during the final reporting step for executive summaries, discussions, conclusions, recommendations, decision rationales, and root-cause narratives.
• Use for a generated summary that interprets evidence rather than prescribing a procedure.
• Use whenever the user explicitly requests prose_english.
• Do not activate for analysis notes, ordinary chat, source extraction, code, or technical data structures.

Inputs

• Verified findings, evidence, uncertainty, limitations, and recommendations.
• The intended reader and the decision the document must support.
• Mandatory terminology, headings, citations, and template requirements.
• An optional explicit user style choice.

Outputs

• Final prose that states actors, actions, evidence, consequences, and uncertainty directly.
• Natural paragraph structure shaped by the argument rather than a fixed response template.
• A style record of prose_english when the reporting workflow records provenance.

Engineering Method

1. Decide the meaning before drafting. Identify the claim, evidence, responsible actor, affected object, consequence, and uncertainty.
2. Name concrete actors and actions. Prefer "the valve closed in 4 s" to "a rapid closure event occurred".
3. Use familiar, precise words. Keep specialized engineering terms when they carry necessary meaning, and define them when the audience may not know them.
4. Replace stock phrases, dead metaphors, inflated diction, euphemism, and abstract noun chains with the fact or mechanism they conceal.
5. Prefer active voice when the actor matters. Use passive voice when the actor is unknown, irrelevant, or less important than the result.
6. Put measured quantities and observed consequences ahead of adjectives. Never make a sentence vivid at the cost of technical accuracy.
7. Vary sentence length and cadence deliberately. Let emphasis follow the meaning rather than a prefabricated rhythm.
8. State uncertainty, failure, adverse consequence, and responsibility plainly. Do not use style to make an unwelcome result disappear.
9. Break a style rule when strict compliance would make the statement misleading, unnatural, or technically wrong.