SYN-015
Hard constraint
layer: sentence
Resolve misplaced relative clause
IF a relative clause can attach to the wrong noun, THEN move it beside the intended antecedent or repeat the noun ELSE retain.
Why the rule exists
Relative-clause attachment determines which entity receives the description.
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.
- relative_clause.attachment_ambiguous eq true
Facts this rule reads
| Path | Source |
|---|---|
relative_clause.attachment_ambiguous |
You supply it |
Then
- move — target
relative_clause - replace — target
relative_pronoun
Else
- retain — target
current_text, No triggering condition is present.
LAKA
- Smallest sufficient intervention
- Yes
- Primary axes
Sources
-
The Copyeditor's Handbook — Amy Einsohn; Marilyn Schwartz
Professional copyediting practice, grammar, and editorial process. -
The Sense of Style — Steven Pinker
Reader-centered clarity informed by linguistics and cognition.
The raw rule record
Verbatim from 09-syntax-and-sentence-rules.json. Also available at /v1/rules/SYN-015.
{
"id": "SYN-015",
"name": "Resolve misplaced relative clause",
"domain": "syntax",
"layer": "sentence",
"strength": "hard_constraint",
"human_logic": "IF a relative clause can attach to the wrong noun, THEN move it beside the intended antecedent or repeat the noun ELSE retain.",
"when": {
"path": "relative_clause.attachment_ambiguous",
"operator": "eq",
"value": true
},
"then": [
{
"action": "move",
"target": "relative_clause",
"destination": "after_antecedent"
},
{
"action": "replace",
"target": "relative_pronoun",
"when": "movement_insufficient",
"with": "antecedent_noun_phrase"
}
],
"else": [
{
"action": "retain",
"target": "current_text",
"reason": "No triggering condition is present."
}
],
"unless": [],
"because": "Relative-clause attachment determines which entity receives the description.",
"diagnostics": [],
"examples": {},
"source_ids": [
"BK-007",
"BK-008"
],
"laka": {
"smallest_sufficient_intervention": true,
"primary_axes": [
"scope",
"depth",
"magnitude",
"reversibility"
]
}
}
Other syntax rules
- SYN-001 Complete clause for formal prose IF a unit is presented as a formal prose sentence AND lacks an independent clause, THEN attach it, complete it, or label it as a fragment ELSE retain. Hard constraint
- SYN-002 Separate fused independent clauses IF adjacent independent clauses have no valid boundary, THEN add a coordinator and punctuation, a semicolon, or a period ELSE retain. Hard constraint
- SYN-003 Prefer visible actor–action order IF the reader must act or identify responsibility AND no stronger reason favors passive voice, THEN place the actor before the action ELSE retain. Context default
- SYN-004 Use passive voice for a reason IF a clause is passive, THEN retain it only when the receiver is the topic, the actor is unknown or irrelevant, blame should be softened, or domain convention requires it ELSE convert to active. Context default
- SYN-005 Put conditions before instructions IF an instruction applies only under a condition, THEN state the condition before the imperative ELSE give the action directly. Context default
- SYN-006 One principal action per procedural step IF a step contains multiple independently verifiable actions, THEN split them into ordered steps ELSE retain a tightly coupled action. Context default
- SYN-007 Limit nested clauses for general audiences IF clause nesting exceeds two levels AND the audience is not expert-only, THEN split or promote a buried clause ELSE retain necessary complexity. Heuristic
- SYN-008 Given information before new information IF a sentence introduces new information before the anchor it depends on, THEN reorder from shared context to new contribution ELSE retain a deliberate surprise. Heuristic