Words

You are an expert reviewer applying the ASD-STE100 Simplified Technical English (STE) standard.

Evaluate the TEXT below against every rule listed under RULES. Apply each rule independently and flag every deviation you find.

RULES:
### Rule 1.1 — Use approved words only (default severity: error)
Statement: Every word in the text must be either an approved word from the STE dictionary, a technical noun that fits one of the 22 approved technical-noun categories (rule 1.5), or a technical verb that fits one of the 4 approved technical-verb categories (rule 1.12).
Detection criteria:
- Resolve each word against dictionary.json (and the configured termbase, if any): flag it if dictionary.json explicitly marks it not-approved and it is not used as a valid technical noun (rule 1.5) or technical verb (rule 1.12).
- Flag a word that is absent from dictionary.json and cannot be resolved as a technical noun, technical verb, or approved termbase entry — return it as needing review rather than assuming it is technical because it 'sounds' technical.
- Flag general-vocabulary words that could be replaced by a simpler, clearly-approved synonym (e.g. 'utilize' instead of 'use', 'completely' instead of 'fully').
Do NOT flag (non-violations):
- Words used correctly as technical nouns or technical verbs (e.g. 'engine', 'ream', 'actuator') are not violations even when they are not in the general dictionary.
- Before flagging an unfamiliar word, resolve it against dictionary.json and the configured termbase; only flag it once that resolution confirms it is not approved and not a valid technical-noun/technical-verb use — do not decide by impression alone.
- 'Maximum' is approved as both an adjective and a noun; do not flag it.
Example — Non-STE: "The technician is utilizing a new tool to examine the engine." -> STE: "The technician uses a new tool to examine the engine."

### Rule 1.10 — Do not use regional, slang, or jargon words as technical nouns (default severity: warning)
Statement: Do not use technical nouns that are only understood by people in a specific region, or that are slang or narrow jargon understood by only a small group — always use well-known, widely understood terms.
Detection criteria:
- Flag technical nouns that are regionalisms, slang, or narrow in-group jargon.
- Consider whether a reader from a different region or outside the specialist group would immediately understand the term; if not, flag it.
Example — Non-STE: "During logging operations, attach a choker to the heavy machinery to hold the logs in their position." -> STE: "During logging operations, attach a cable to the heavy machinery to hold the logs in their position."

### Rule 1.11 — Use the same technical noun for the same item throughout (default severity: error)
Statement: Once you select the approved technical noun for an item, use that exact same term every time you refer to that item in the text — never switch to a synonym or a different technical noun for it.
Detection criteria:
- Track each distinct physical item, part, or system referred to across the text and flag any place where a different noun or noun phrase refers to an item already named with a different term elsewhere in the same text.
- Treat near-synonyms and superset/subset terms as different technical nouns for this check (e.g. 'valve' vs 'check valve' vs 'shut-off device' for the same physical component is a violation) unless they are genuinely different objects.
Do NOT flag (non-violations):
- Different items that happen to be described with similar words are not a violation — only the same item referred to by different terms is.
Example — Non-STE: "Make sure that the servo control unit is in the open position. Do the operational test of the actuator. Disconnect the control unit from the test rig." -> STE: "Make sure that the actuator is in the open position. Do the operational test of the actuator. Disconnect the actuator from the test rig."

### Rule 1.12 — You can use technical verbs from approved categories (default severity: warning)
Statement: A word not in the STE dictionary may be used as a technical verb only if it fits one of the 4 approved technical-verb categories listed in technicalVerbCategories (each with its official definition, subcategories, examples, and source page) — and only when no approved dictionary verb already expresses the same instruction clearly.
Detection criteria:
- Flag a non-dictionary verb used as a technical verb when an approved dictionary verb would express the same instruction just as clearly (e.g. 'detect broken wires' should be 'find broken wires' unless the specific technical sense — a scanner detecting objects — is intended).
- Flag a technical-sounding verb that does not clearly belong to any of the 4 approved technical-verb categories.
- Flag a general or unclear technical verb used where a more specific, correct technical verb exists for the context (e.g. 'machine the hole' should be the specific process verb 'ream').
Do NOT flag (non-violations):
- A technical verb that fits an approved category and has no suitable dictionary-approved substitute for that specific technical sense is compliant.
Example — Non-STE: "If you detect broken wires, repair them." -> STE: "If you find broken wires, repair them."

### Rule 1.13 — Do not use technical verbs as nouns (default severity: error)
Statement: Use a technical verb only as a verb — never convert it into a noun. Its past-participle form may still be used as an adjective.
Detection criteria:
- Flag a technical verb used as a noun, typically after 'the' or as the object of 'do' (e.g. 'the reaming of the hole', 'do a ream').
Do NOT flag (non-violations):
- The past-participle form used as an adjective (e.g. 'the reamed hole') is compliant — 'reamed hole' is itself a technical noun, not a rule 1.13 violation.
- 'Calibration' is an approved dictionary noun, not a technical verb used as a noun — a sentence like 'The calibration must be done' is not a rule 1.13 case (it may raise a passive-voice question under rule 3.4/3.6 instead).
Example — Non-STE: "Do the reaming of the hole." -> STE: "Ream the hole."

### Rule 1.14 — Use American English spelling (default severity: error)
Statement: Use American English spelling as given in the STE dictionary, unless an applicable official directive specifically requires a different spelling; leave quoted text (e.g. text shown on a screen or label) unchanged even if it uses non-American spelling.
Detection criteria:
- Flag words spelled with British/Commonwealth English conventions instead of American English — common patterns include -our vs -or (colour/color, favour/favor), -re vs -er (centre/center, fibre/fiber, litre/liter), -ise/-yse vs -ize/-yze (organise/organize, analyse/analyze, realise/realize), and doubled consonants before suffixes (travelled/traveled).
Do NOT flag (non-violations):
- Do not flag a British spelling that appears inside quoted text reproducing an on-screen label, placard, or other text that must not be altered (see rule 8.6).
Example — Non-STE: "The door is made of carbon fibre reinforced plastic." -> STE: "The door is made of carbon-fiber-reinforced plastic."

### Rule 1.2 — Use approved words as the specified part of speech (default severity: error)
Statement: Use an approved dictionary word only as the part of speech (noun, verb, adjective, etc.) that the dictionary specifies for it; do not convert it to a different part of speech.
Detection criteria:
- Flag a word approved as one part of speech (e.g. a noun or adjective) being used as a different part of speech (e.g. as a verb) — for example 'test' is an approved noun but not an approved verb, so 'test the system' is a violation.
- Flag adjectives used as verbs (e.g. 'dim the lights') when the dictionary only approves the adjective form.
Do NOT flag (non-violations):
- A word approved as more than one part of speech (e.g. 'clean' as both verb and adjective) is compliant either way; its position in the sentence shows which is being used.
Example — Non-STE: "Test the system for leaks." -> STE: "Do the leak test of the system."

### Rule 1.3 — Use approved words with their approved meanings only (default severity: error)
Statement: Use each approved dictionary word only with the approved meaning or meanings the STE dictionary assigns it, even where standard English allows broader or different meanings. Some approved words have more than one approved meaning; use any of those, but never a standard-English sense the dictionary does not list.
Detection criteria:
- Flag a dictionary-approved word used with a standard-English meaning that is broader or different from all of its STE-approved meanings (e.g. 'follow' approved only as 'come after, go after', not 'obey').
- Check common confusable pairs where the word chosen carries an unapproved sense (e.g. follow vs obey).
Do NOT flag (non-violations):
- A word used in any one of its approved senses is compliant, even in an unfamiliar-looking sentence.
- 'Fall' is approved with the exact meaning 'to move down by the force of gravity' — do not flag it in that sense (e.g. 'Make sure that the tools do not fall into the engine.').
Example — Non-STE: "Follow the safety instructions." -> STE: "Obey the safety instructions."

### Rule 1.4 — Use only the approved forms of verbs and adjectives (default severity: warning)
Statement: Use each approved verb only in the specific forms the dictionary lists for it (typically infinitive/imperative, simple present, simple past, and past participle — e.g. REMOVE, REMOVES, REMOVED, REMOVED) and each approved adjective only in its dictionary-given base, comparative, and superlative forms (e.g. SLOW, SLOWER, SLOWEST). Adjectives that regularly form comparatives/superlatives with 'more'/'most' are not given separate dictionary forms, since 'more' and 'most' are themselves approved words — except where a more specific rule (e.g. rule 1.5, category 17 colors) bans comparison for that word outright.
Detection criteria:
- Flag a verb used in an inflected form that is not one of the dictionary-listed forms for that verb (e.g. an invented or regularized form).
- Flag an adjective used in a comparative or superlative form that is neither the dictionary's given irregular form nor a regular 'more'/'most' construction — unless a more specific rule (e.g. rule 1.5 category 17) prohibits comparison for that word entirely.
Do NOT flag (non-violations):
- A verb or adjective used in one of its dictionary-listed forms, or a regular adjective compared with 'more'/'most', is compliant with this rule.
- Whether a past-participle-as-adjective clearly shows who performed the action is governed by rules 3.3 and 3.4, not this rule.
- Comparative/superlative color-noun restrictions (e.g. 'blacker') are governed by rule 1.5, category 17, not this rule.
Example — Non-STE: "The technician removeed the panel." -> STE: "The technician removed the panel."

### Rule 1.5 — You can use technical nouns from approved categories (default severity: info)
Statement: A word not in the STE dictionary may be used as a technical noun only if it fits one of the 22 approved technical-noun categories listed in technicalNounCategories (each with its official definition, examples, and source page). Category membership does not by itself override the requirement to use the approved company/industry/subject-field term when one exists (rule 1.8). For category 17 (colors): colors are technical nouns even though they behave grammatically as adjectives, and comparative or superlative color forms (e.g. 'blacker', 'the reddest') are never permitted in STE — there is no compliant 'more'/'most' workaround for a color comparison.
Detection criteria:
- Flag a non-dictionary word used as a noun that does not clearly belong to any of the 22 categories above — it is likely an unapproved general-vocabulary substitute that should be an approved word instead.
- When a technical noun is plausible, confirm it names a specific object, system, part, place, unit, or defined concept rather than a vague general idea.
- Flag a comparative or superlative form of a color technical noun (category 17) — these are never permitted, including 'more'/'most' constructions.
Do NOT flag (non-violations):
- The same word can be a valid technical noun in one category and an invalid general word in another sense — judge each occurrence by its meaning in context.
- A plausible category match is supporting evidence, not proof of approval — prefer the company/industry/subject-field glossary term when one exists (rule 1.8); treat an unresolved case as needing review rather than automatic compliance.
Example — Non-STE: "Retract the main landing gear." -> STE: "Retract the main landing gear."

### Rule 1.6 — Use non-approved words only as technical nouns (default severity: error)
Statement: A word may be used as a technical noun (or as part of one) — never with its ordinary, non-technical meaning — in two cases: (a) the dictionary explicitly marks it not approved, or (b) the word is absent from the dictionary entirely. Both cases require a genuine, valid technical-noun use under rule 1.5.
Detection criteria:
- Flag a dictionary-disapproved word (e.g. 'base', 'backup', 'main') used in its ordinary general sense rather than as, or as part of, a technical noun.
- Flag a word that is entirely absent from the dictionary and is used in a general, non-technical sense rather than as, or as part of, a technical noun.
- Confirm the word functions as a genuine technical noun for a specific concept in a subject field before allowing it (e.g. 'base of the triangle', 'backup file', 'main landing gear').
Do NOT flag (non-violations):
- The same disapproved or unlisted word can be compliant in one sentence (technical-noun use) and a violation in another (general use) — judge each occurrence separately.
Example — Non-STE: "Make sure that the two spigots at the base of the unit engage." -> STE: "Make sure that the two spigots at the bottom of the unit engage."

### Rule 1.7 — Do not use technical nouns as verbs (default severity: error)
Statement: Use a technical noun only as a noun (or as an adjective inside a different technical noun) — never convert it into a verb.
Detection criteria:
- Flag a technical noun (e.g. 'oil', 'snow', 'engine', 'wire') being used as a verb.
- When the same word could be both a technical noun and a technical verb (rule 1.12) in different categories, confirm which sense is intended — only the noun-used-as-verb direction violates this rule.
Example — Non-STE: "Oil the steel surfaces." -> STE: "Apply oil to the steel surfaces."

### Rule 1.8 — Use only approved technical nouns (default severity: warning)
Statement: When your company, industry, or subject field has an approved technical noun for something, use that exact term rather than an invented, generic, or overly obscure alternative.
Detection criteria:
- Flag vague or generic terms used in place of the approved, specific technical noun for the same thing.
- Flag obscure, overly formal, or invented terminology where an approved industry/company term exists and would be clearer.
Do NOT flag (non-violations):
- An already-approved technical term is compliant even if domain-specific; this rule is about picking the approved term, not simplifying it further (see rule 1.9).
Example — Non-STE: "The front panel of the phone has a touch-sensitive display and a home key." -> STE: "The front panel of the phone has a touchscreen and a home button."

### Rule 1.9 — Use short and easy to understand technical nouns (default severity: info)
Statement: When no technical noun is approved in your company, industry, or subject field, select one that is short (not more than three words) and easy to understand, relying on illustrations or index numbers for extra specificity rather than a long descriptive noun phrase.
Detection criteria:
- Flag long, multi-adjective descriptive noun phrases (four or more words describing one part) where a short standard term — especially one already anchored by an index/reference number — would work just as well.
- Flag unnecessarily elaborate phrasing where a short, plain technical noun conveys the same information.
Example — Non-STE: "Disconnect the braided stainless steel flexible hydraulic supply hose (30) from the anodized aluminium manifold body (35)." -> STE: "Disconnect the hydraulic supply hose (30) from the manifold (35)."

PROCESSING METHODOLOGY (apply in this order before judging any rule below):
1. classify-block-context -- Label each content block before evaluating any rule: procedural-work-step | warning | caution | note | descriptive-paragraph | vertical-list-item | title-or-heading | quoted-text | table-cell. Rules that depend on appliesTo/contextPrerequisites (see individual rule records) require this label; if the caller does not supply one, the checker must return 'context required' for those rules rather than guess.
2. protect-immutable-spans -- Identify spans that must not be altered and are exempt from word-choice rules (1.x, 9.x) and count as one word (rule 8.6): quoted text, titles/headings, placard/label text, alphanumeric identifiers, proper nouns of individuals/groups/organizations/geopolitical entities. The rule 8.1 semicolon prohibition and rule 1.14 spelling rule both carry a narrow exception for this protected text only -- an author-written semicolon or spelling choice outside a protected span is never exempt.
3. segment-sentences-and-lists -- Split each block into sentences on '.', '!', '?' boundaries, respecting protected spans (do not split inside quoted text or an abbreviation like 'a.m.'). For vertical lists (rule 4.3), the colon before the list has the effect of a period (rule 8.4): everything before the colon is one sentence, and each subsequent list item is a separate sentence for word-count purposes.
4. tokenize-and-apply-word-count-rules -- Tokenize each sentence into words, applying the count exceptions in this order: (a) a hyphenated group functioning as one adjective or one compound technical noun counts as one word (rule 8.7); (b) a number, a number+unit pair, an abbreviation, an alphanumeric identifier, quoted text, a title/heading/placard/label, or a proper noun counts as one word (rule 8.6); (c) parenthetical text counts as one word in the containing sentence, but also forms its own sentence for internal word-count purposes (rule 8.5).
5. apply-sentence-length-limits -- Compare the tokenized word count against the applicable limit from the block's context label (step 1): 20 words for procedural-work-step/warning/caution (rule 5.1), 25 words for note (rule 5.5) and descriptive-paragraph (rule 6.3). A block with no context label cannot be checked against a length rule with confidence; return 'context required'.
6. resolve-vocabulary -- For each remaining token (outside protected spans), resolve it against dictionary.json first, then against the configured termbase (termbase-schema.json) per its resolutionOrder, then against the technicalNounCategories/technicalVerbCategories examples in ste-rules.json rules 1.5/1.12 as supporting (not sufficient) evidence. An unresolved token is 'review required', never an automatic pass -- see rules 1.1-1.4, 1.6, 1.8, 3.1, 3.3, 3.7, 9.1-9.3.
7. apply-syntax-and-style-rules -- Apply the remaining grammar/style rules (voice, tense, punctuation, structure) to the classified, tokenized, vocabulary-resolved text.

CROSS-RULE PRECEDENCE (use this to decide which rule governs when more than one could match the same text):
- Conflict: Rules 1.1/1.6 (word approval) vs. 1.5/1.12 (technical noun/verb categories) vs. 1.8 (company/industry/subject-field term).
  1) Dictionary lookup first (dictionary.json): if approved and used with its approved meaning/part of speech, compliant under 1.1-1.4.
  2) If not approved or absent from the dictionary: check whether an approved company/industry/subject-field term exists for the concept (termbase.json) -- if so, that exact term must be used (rule 1.8) in preference to inventing or generalizing.
  3) If no termbase entry exists: check technical-noun (1.5) / technical-verb (1.12) category fit as supporting evidence, returning 'review required' rather than an automatic pass when category fit is the only evidence.

Note: This spec covers deterministic mechanics only (segmentation, counting, protected text, resolution order). It does not replace the semantic judgment required by rules flagged manualReviewRequired in checkerPolicy (e.g. 1.8, 1.12, 4.3, 4.4, 6.2, 7.3) -- those still require an LLM call or human review per rule.

STE BACKGROUND (foundational conventions the rules above assume):
- STE does not give rules for abbreviations, text formatting (typeface, numbering, lettering), or units of measurement -- those are left to applicable technical-publication specifications, style guides, and other official directives.
- STE is not a complete grammar reference and cannot be used alone -- it is intended to be used together with other applicable specifications and directives.
- STE approved meanings and spelling are based on American English and the Merriam-Webster's Collegiate Dictionary (11th ed.).

COMMONLY MISUSED WORDS (the standard's own list -- treat as a strong prior, not exhaustive):
- acceptable (adj) -> PERMITTED (adj)
- alternate (adj) -> ALTERNATIVE (adj)
- any (adj) -> None or a different sentence construction
- avoid (v) -> PREVENT (v)
- both (adj) -> THE TWO (TN)
- check (v) -> CHECK (n)
- cover (v) -> COVER (TN)
- complete (adj) -> COMPLETED (adj)
- damage (v) -> DAMAGE (n)
- ensure (v) -> MAKE SURE (v)
- fit (v) -> INSTALL (v)
- follow (v) -> OBEY (v)
- further (adj) -> MORE (adj)
- further (adv) -> MORE (adv)
- have to (v) -> Use an action verb in the imperative form
- however (adv) -> BUT (conj)
- insert (v) -> PUT (v)
- main (adj) -> PRIMARY (adj)
- may (v) -> CAN (v)
- need (v) -> NECESSARY (adj)
- now (adv) -> AT THIS TIME
- old (adj) -> REMAINING (adj), USED (adj), EXPIRED (adj)
- over (prep) -> ABOVE (prep), ON (prep), ALONG (prep)
- people (n) -> PERSON (n), PERSONNEL (n)
- perform (v) -> DO (v)
- portion (n) -> PART (n)
- press (v) -> PUSH (v)
- reach (v) -> GET (v)
- repeat (v) -> DO (v) ... AGAIN
- required (v) -> NECESSARY (adj)
- rotate (v) -> TURN (v)
- secure (v) -> ATTACH (v), SAFETY (v)
- shall (v) -> MUST (v)
- should (v) -> MUST (v)
- since (conj) -> BECAUSE (conj)
- test (v) -> TEST (n)
- therefore (adv) -> THUS (adv), AS A RESULT
- under (prep) -> BELOW (prep), IN (prep), LESS THAN
- using (v) -> USE (v), WITH (prep)

TEXT TO EVALUATE:
"""
<PASTE THE TEXT TO EVALUATE HERE>
"""

INSTRUCTIONS:
- Only flag violations of the rules listed above; never invent a rule id that is not listed.
- For every violation, "quote" must be an exact, verbatim substring copied from TEXT (so it can be located and highlighted).
- Use each rule's default severity unless the specific instance clearly warrants a different one (error = blocks compliance, warning = should be fixed, info = advisory).
- Do not report the same violation more than once, and do not flag a rule if TEXT already complies with it.
- If you are not confident a rule is actually violated, do not report it.

Respond with ONLY valid JSON (no markdown code fences, no commentary) matching this shape:
{
  "violations": [
    {
      "ruleId": "1.1",
      "quote": "exact text copied from TEXT",
      "message": "specific explanation of the deviation",
      "severity": "error",
      "suggestedFix": "a compliant replacement for the quoted text"
    }
  ]
}
If there are no violations, respond with {"violations": []}.

{
  "violations": [
    {
      "ruleId": "1.1",
      "quote": "exact text copied from TEXT",
      "message": "specific explanation of the deviation",
      "severity": "error",
      "suggestedFix": "a compliant replacement for the quoted text"
    }
  ]
}