Verbs

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 3.1 — Use only the verb forms that are given in the dictionary (default severity: error)
Statement: For each approved verb, use only the specific inflected forms listed for it in the STE dictionary (typically the base/infinitive, the simple present, the simple past, and the past participle). Do not use, invent, or regularize any form of an approved verb that is not one of the forms the dictionary gives for it, even if that form would be grammatically valid in general English.
Detection criteria:
- For each verb used in the text, check whether the specific inflected form matches one of the forms listed in the dictionary entry for that verb (e.g. GIVE -> GIVES, GAVE, GIVEN); flag any form that is not among them.
- Pay particular attention to irregular verbs — flag a regularized or invented form (e.g. 'gived' instead of 'gave') or any extra form beyond the ones the dictionary lists.
Do NOT flag (non-violations):
- A form that matches one of the dictionary-listed forms for the verb is compliant with this rule regardless of which tense/voice it is used in — tense and voice correctness are covered separately by rules 3.2-3.6.
Example — Non-STE: "The technician gived the tool to the mechanic." -> STE: "The technician gave the tool to the mechanic."

### Rule 3.2 — Use only approved verb forms and tenses (default severity: error)
Statement: Use verbs only in one of these forms or tenses: the infinitive form, the imperative (command) form, the simple present tense, the simple past tense, the simple future tense, or the past participle used as an adjective. Do not use other tenses or constructions such as the present/past perfect, the present/past progressive, or any other complex (multi-auxiliary) verb construction.
Detection criteria:
- Flag present perfect ('have/has adjusted') and past perfect ('had adjusted') constructions.
- Flag present or past progressive constructions ('is/was adjusting').
- Flag any other complex verb construction that combines an auxiliary verb with a participle in a way that is not one of the six approved forms.
- Confirm every finite verb in the text is one of: infinitive, imperative, simple present, simple past, simple future, or a past participle functioning as an adjective.
Do NOT flag (non-violations):
- A past participle functioning as an adjective (before a noun, or after 'to be'/'to become'/'to stay') is allowed under rule 3.3 — do not confuse it with the disallowed perfect-tense construction that also uses a past participle.
Example — Non-STE: "The system has failed twice this month." -> STE: "The system failed twice this month."

### Rule 3.3 — Use the past participle form as an adjective (default severity: warning)
Statement: A verb's past participle form may be used as an adjective — either directly before the noun it modifies, or after a form of 'to be,' 'to become,' or 'to stay' — to show the condition of something; this is not passive voice. Only use a past participle as an adjective if it (or its adjective sense) is listed in the dictionary, including approved adjectives such as 'permitted' or 'damaged' whose underlying verb is not itself approved.
Detection criteria:
- Confirm each past-participle-as-adjective is positioned either immediately before the noun it modifies, or after a copular verb ('is/are/was/were,' 'become(s),' 'stay(s)') — not as part of a compound/perfect verb tense (which instead violates rule 3.2 or 3.4).
- Flag a past participle used as an adjective if it is not listed in the dictionary as an approved adjective or as an approved verb whose past-participle form is given.
Do NOT flag (non-violations):
- 'The unit is disassembled' or 'the disassembled unit,' describing a state or condition, is compliant STE even though it resembles a passive-voice sentence; distinguish state-description (adjective) uses from true passive-voice action clauses (rule 3.6) by checking whether the sentence is describing an action being done to the subject or simply the subject's condition.
- Approved adjectives derived from a non-approved verb (e.g. 'permitted,' 'damaged') are fine to use if the dictionary lists them with part of speech '(adj)', even though the underlying verb is not approved for use.
- Rule 1.4 governs which verb/adjective forms are dictionary-approved; it does not restrict a compliant past-participle-as-adjective use under this rule to only cases where the actor is stated — that clarity question is decided here and in rule 3.4, not by rule 1.4.
Example — Non-STE: "Do not put more than the weight that is permitted on the trolley." -> STE: "Do not put more than the permitted weight on the trolley."

### Rule 3.4 — Do not use auxiliary verbs to make complex verb constructions (default severity: error)
Statement: Do not build complex verb constructions with auxiliary verbs used as the main verb of a perfect tense or a passive/modal construction — for example 'have/has' plus a past participle to form a perfect tense, or 'is/are/can/must/will' plus a past participle to form a modal or passive construction where the participle functions as the action verb, not as an adjective. This does not cover a past participle used purely as an adjective (rule 3.3) or the narrow permitted descriptive passive with a genuinely unknown agent (rule 3.6) — those are separate, permitted constructions that happen to share the same surface 'be + past participle' form. These disallowed constructions produce non-approved tenses and passive-voice sentences. Instead, identify the true agent of the action and use it as the subject of an approved simple tense (see rule 3.2), or use the imperative for procedural instructions.
Detection criteria:
- Flag 'have/has + past participle' (present perfect, e.g. 'has adjusted') and other auxiliary + past-participle combinations that create a perfect tense.
- Flag modal or auxiliary passive constructions such as 'is to be installed,' 'can be adjusted,' 'must be adjusted,' 'will be adjusted by.'
- Flag these constructions even when combined across a full sentence, e.g. 'The seat is to be installed before you install the cushion.'
Do NOT flag (non-violations):
- A past participle used purely as an adjective after 'to be/become/stay' (rule 3.3) is not a violation of this rule — only participles functioning as the main verb of a complex tense or passive construction are.
- When the text or context names the actual agent (e.g. 'The robot will adjust the sleeve.'), keep that agent as the subject — do not replace a stated agent with 'you'/'we'.
Example — Non-STE: "The operator has adjusted the linkage." -> STE: "The operator adjusted the linkage."

### Rule 3.5 — Use the "-ing" form of a verb only as a technical noun or noun modifier (default severity: error)
Statement: Do not use a word with an '-ing' form as part of a verb phrase (a progressive tense) or to build long modifying clauses attached to a noun. The '-ing' form may be used in two separate, independent ways: (1) as a valid technical noun (for example in a procedure title or heading) or as a functional modifier within a technical noun describing the function of a system, component, part, tool, or material — this path does not require the specific '-ing' word to also appear in the small dictionary-approved general list; or (2) as one of the small number of dictionary-approved general '-ing' words. A word only needs to satisfy one of these two paths, not both.
Detection criteria:
- Flag any '-ing' word used as part of a verb phrase (progressive tense, e.g. 'is opening,' 'are doing') rather than as a technical noun or noun-modifier.
- Flag '-ing' words used to build long modifying phrases or dependent clauses attached to a noun (e.g. 'a mechanic opening a door without observing the safety precautions...').
- For an '-ing' word used as a noun or noun-modifier, confirm it is EITHER a valid technical noun/functional modifier within an approved technical noun (e.g. 'air-conditioning system,' 'grinding wheel,' 'welding torch') OR one of the small dictionary-approved general set (e.g. lighting, opening, routing, servicing as nouns; mating, missing, remaining as adjectives; something as a pronoun; during as a preposition) — it does not need to satisfy both.
Do NOT flag (non-violations):
- '-ing' words used as procedure/section titles or headings (e.g. 'Cleaning,' 'Testing and Fault Isolation,' 'Troubleshooting') are compliant technical-noun uses, not violations.
- An '-ing' word functioning as a modifier describing a component's function within a multi-word noun (e.g. 'switching relay') is compliant.
Example — Non-STE: "When you are doing this procedure, obey all the safety precautions." -> STE: "When you do this procedure, obey all the safety precautions."

### Rule 3.6 — Use the active voice (default severity: error)
Statement: Always write in the active voice, where the grammatical subject performs the action of the sentence. In descriptive writing only, the passive voice is permitted when the agent (the person or thing that does the action) is genuinely unknown; procedural (instructional) writing must always use the active voice.
Detection criteria:
- Test each sentence with 'by whom or by what?' — if the grammatical subject receives the action (typically 'is/are/was/were + past participle,' often followed by a 'by <agent>' phrase), flag it as passive.
- In procedural/instructional text, flag any passive-voice sentence regardless of whether the agent is known — procedures must always be active or imperative.
- In descriptive text, flag a passive-voice sentence only when the agent is actually identifiable from context — do not flag genuine agent-unknown cases.
Do NOT flag (non-violations):
- A passive sentence in descriptive writing where the agent is truly unknown or unknowable (e.g. 'During transmission, the data was corrupted') is compliant and should not be flagged.
- Using 'something' as a placeholder agent is approved only when the agent is genuinely unknown/unknowable, not merely unstated.
- Using 'you' or 'we' as the subject is approved only with positive evidence of who the agent is: 'you' when the reader is genuinely the agent, 'we' when the writer's own organization is genuinely the agent. Do not default to 'you'/'we' just because no agent happens to be stated in the sentence — if the true agent is genuinely unknown, prefer the descriptive passive or 'something' instead.
Example — Non-STE: "The circuits are connected by a switching relay." -> STE: "A switching relay connects the circuits."

### Rule 3.7 — Use an approved verb to describe an action, not a noun or other part of speech (default severity: warning)
Statement: When an approved verb exists that describes the action you mean, use that verb directly rather than a nominalized construction (e.g. 'give an indication of,' 'before the removal of') or another part of speech. If a word is not approved as a verb in the dictionary, do not use it as a verb — restructure the sentence instead, for example with a 'do a/an <noun> of' construction.
Detection criteria:
- Flag nominalized action phrases such as 'do/perform/carry out the <noun> of,' 'give an indication of,' 'before the removal of' where a direct approved verb for that action exists (e.g. 'show,' 'remove').
- Flag a word used as a verb when it is not listed with a verb part of speech in the dictionary — such actions must instead be expressed with a noun-based construction (e.g. 'do a check of').
Do NOT flag (non-violations):
- A construction like 'do a check of' is compliant STE, not an unwanted nominalization, specifically when the underlying word (e.g. 'check') is not approved as a verb in the dictionary.
Example — Non-STE: "The ohmmeter gives an indication of 450 ohms." -> STE: "The ohmmeter shows 450 ohms."

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 3.3 (past participle as adjective), 3.4 (no auxiliary + participle complex constructions), and 3.6 (active voice / permitted descriptive passive) can all match the same surface form 'is/are/was/were + past participle'.
  1) If the participle describes a state/condition (before a noun, or after to be/become/stay, with no implied agent performing an action) -> rule 3.3 governs; compliant if the participle is dictionary-approved.
  2) Else, if the sentence is descriptive writing and the agent is genuinely unknown/unknowable -> rule 3.6's permitted descriptive passive governs; compliant.
  3) Otherwise -> rule 3.4 governs; flag as a disallowed complex/passive construction.

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"
    }
  ]
}