GRM-002
Hard constraint
layer: clause
Compound subject agreement
IF two or more singular subject heads are coordinated by AND, THEN use plural agreement ELSE evaluate the coordinator.
Why the rule exists
AND normally combines subject referents into a plural set.
Condition
The rule fires when this evaluates true. Paths marked below must be present in the fact base; the engine reports the rest rather than guessing them.
- ALL
- clause.subject.coordinator eq "and"
- clause.subject.head_count gte 2
- clause.subject.denotes_single_unit eq false
Facts this rule reads
| Path | Source |
|---|---|
clause.subject.coordinator |
You supply it |
clause.subject.head_count |
You supply it |
clause.subject.denotes_single_unit |
You supply it |
Then
- align — target
clause.verb.number, value"plural"
Else
- evaluate — target
clause.subject.coordinator
LAKA
- Smallest sufficient intervention
- Yes
- Primary axes
Sources
-
The Blue Book of Grammar and Punctuation — Jane Straus; Lester Kaufman
Accessible grammar, punctuation, examples, and exercises. -
Practical English Usage — Michael Swan
Advanced grammar and usage reference for learners and teachers. -
Grammar, Punctuation, and Sentence Structure — Purdue Online Writing Lab
link
Practical mechanics, clause, sentence, punctuation, and style guidance.
The raw rule record
Verbatim from 07-core-grammar-rules.json. Also available at /v1/rules/GRM-002.
{
"id": "GRM-002",
"name": "Compound subject agreement",
"domain": "grammar",
"layer": "clause",
"strength": "hard_constraint",
"human_logic": "IF two or more singular subject heads are coordinated by AND, THEN use plural agreement ELSE evaluate the coordinator.",
"when": {
"all": [
{
"path": "clause.subject.coordinator",
"operator": "eq",
"value": "and"
},
{
"path": "clause.subject.head_count",
"operator": "gte",
"value": 2
},
{
"path": "clause.subject.denotes_single_unit",
"operator": "eq",
"value": false
}
]
},
"then": [
{
"action": "align",
"target": "clause.verb.number",
"value": "plural"
}
],
"else": [
{
"action": "evaluate",
"target": "clause.subject.coordinator",
"rules": [
"or_nor_proximity",
"single_unit_exception"
]
}
],
"unless": [],
"because": "AND normally combines subject referents into a plural set.",
"diagnostics": [],
"examples": {},
"source_ids": [
"BK-002",
"BK-010",
"WEB-011"
],
"laka": {
"smallest_sufficient_intervention": true,
"primary_axes": [
"scope",
"depth",
"magnitude",
"reversibility"
]
}
}
Other grammar rules
- GRM-001 Subject–verb number agreement IF a finite clause has an expressed subject AND neither quoted dialect nor an agreement exception applies, THEN align the finite verb with the subject in number ELSE retain. Hard constraint
- GRM-003 Or/nor proximity agreement IF subject alternatives are joined by OR or NOR, THEN agree with the closest subject OR rewrite when the result sounds unstable ELSE retain. Context default
- GRM-004 Pronoun–antecedent agreement IF a pronoun refers to an antecedent AND the antecedent is known, THEN align person and number while respecting singular THEY ELSE request the missing referent. Hard constraint
- GRM-005 Unambiguous pronoun reference IF a pronoun has two or more plausible antecedents OR none, THEN replace it with the intended noun phrase ELSE retain. Hard constraint
- GRM-006 Stable grammatical person IF a passage shifts person without changing speaker, audience, or viewpoint, THEN restore the established person ELSE preserve the motivated shift. Context default
- GRM-007 Tense consistency within a time frame IF tense changes but event time and narrative viewpoint do not, THEN restore the established tense ELSE keep the meaningful time shift. Context default
- GRM-008 Sequence of tenses IF a dependent clause is temporally related to a governing clause, THEN select tense and aspect that express the intended ordering ELSE do not normalize automatically. Hard constraint
- GRM-009 Complete comparative relation IF a comparison can attach to more than one comparison set, THEN state the full set or rewrite ELSE retain. Hard constraint