neqsim-standard-engineering-english

Standard Engineering English

standard_engineering_english is the short alias for this style. It is a compact house style inspired by ASD-STE100. It does not reproduce the ASD-STE100 dictionary and does not establish ASD-STE100 compliance.

When to Use

• Use during the final reporting step for procedures, operating steps, equipment descriptions, technical requirements, warnings, cautions, limits, checklists, and method summaries.
• Use for generated summaries whose main purpose is repeatable action or unambiguous technical interpretation.
• Use whenever the user explicitly requests standard_engineering_english.
• Do not activate for analysis notes, ordinary chat, source extraction, or code.

Inputs

• Verified technical content, actions, conditions, limits, hazards, units, and terminology.
• The project glossary, approved component names, abbreviations, and spelling convention.
• The document type: procedure, description, requirement, safety instruction, or summary.
• Mandatory regulatory wording and an optional explicit user style choice.

Outputs

• Short, complete sentences with stable terminology and explicit logical relations.
• Procedures with conditions before commands and normally one instruction per sentence.
• Descriptions organized around one subject per sentence and one topic per paragraph.
• A style record of standard_engineering_english when the reporting workflow records provenance.

Engineering Method

1. Build or use the project glossary. Use one preferred term for each concept and one meaning for each term. Do not vary synonyms merely to improve rhythm.
2. Use a word in its approved meaning and grammatical role. If a familiar word is ambiguous, rewrite the sentence instead of relying on context.
3. Use the project spelling convention consistently. If none exists, use American spelling. Preserve spelling in quotations and official names.
4. Keep sentences complete. State the subject and verb, and include articles where normal English requires them. Do not use contractions.
5. Prefer active voice. In descriptive text, use passive voice when the agent is unknown or unimportant. Never invent an agent to avoid passive voice.
6. Keep noun clusters short. Aim for no more than three consecutive nouns. Expand longer clusters with a preposition, relative clause, or defined short form.
7. Put conditions before actions. In a procedure, begin the action with an imperative verb and normally give one instruction per sentence. Combine actions only when they occur at the same time.
8. Keep procedural sentences at 20 words or fewer where practical. Keep descriptive sentences and notes at 25 words or fewer where practical. Split a sentence before deleting necessary meaning.
9. Give one subject per descriptive sentence, one topic per paragraph, and no more than six sentences per paragraph where practical.
10. Use notes only for information. Do not hide actions, requirements, limits, or safety controls in a note.
11. For safety text, state the condition or command, the hazard, and the consequence. Use warning for risk of injury or death and caution for equipment damage only when that distinction matches the governing domain standard.
12. Use vertical lists when they make complex alternatives or sequences easier to scan. Keep all items grammatically parallel and do not mix procedures with descriptions in one list.
13. Follow the project rules for units, numbers, symbols, abbreviations, and typography. This style does not define those conventions.