error · Section 3: Verbs
Rule 3.2: Use only approved verb forms and tenses
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.
What a checker looks for
A clear deviation from the rule.
- 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.
What this rule does not cover
- 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.
How to fix it
Rewrite using one of the six approved forms — most often by converting a perfect or progressive construction to the simple past or simple present tense, or to the imperative for procedural instructions. If a mechanical tense substitution would change the intended time relationship (e.g. an action that is genuinely ongoing, future, or still relevant now), restructure the sentence instead — for example by splitting it into two sentences or adding a time reference — rather than forcing it into simple past. Caution: a sentence originally in the past/present progressive or perfect can carry an overlap, ongoing, or still-relevant-now meaning that a mechanical switch to simple past/present can silently drop (e.g. 'was checking ... when the alarm activated' describes an action in progress when a second event interrupted it, which 'checked ... when the alarm activated' does not preserve) — for those cases, restructure the sentence (e.g. split into two sentences, or add an explicit time reference) instead of substituting the tense.
Constraints on the fix
- Preserve the intended time relationship of the original sentence (do not turn future or ongoing information into simple past unless that changes no meaning).
- Verify the rewritten sentence still expresses the same aspect/time meaning as the original before accepting it; do not perform a blind tense substitution.
Examples
Not STE: The system has failed twice this month.
STE: The system failed twice this month.
Not STE: The system has failed twice this month.
STE: The system failed twice this month.
Not STE: The volume control can be adjusted.
STE: You can adjust the volume control.
Related rules
Where this fits in AI governance
A rule a checker can test is a rule a model can be held to. The same discipline, on the governance side of this site.
- Testing AI systems
Verb-form rules are deterministic tests, which is what makes them a useful regression suite for generated text. - Model drift, performance regression and versioning
A rule-level pass rate is a baseline; a provider update that changes the model changes the pass rate. - Output validation guardrails
A controlled language is a checkable output constraint. This is the control that treats model output as something to be checked rather than trusted.
Source
ASD-STE100 Issue 9, Section 3 - Verbs, page 1-3-2.
This page is commentary and does not reproduce the standard. About this rule pack.