Bow Tie Kreative Writing System
Run the engine

Rules / syntax

SYN-016 Hard constraint layer: sentence

Keep correlative pairs balanced

IF BOTH/AND, EITHER/OR, NEITHER/NOR, or NOT ONLY/BUT ALSO joins items, THEN place each half before parallel units ELSE retain.

Why the rule exists

Balanced correlatives show exactly which units are alternatives or additions.

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.

  • coordination.correlative_pair exists true

Facts this rule reads

PathSource
coordination.correlative_pair You supply it

Then

  1. align — target coordination.correlative_positions

Else

  1. retain — target current_text, No triggering condition is present.

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.
  • The Copyeditor's Handbook — Amy Einsohn; Marilyn Schwartz
    Professional copyediting practice, grammar, and editorial process.
The raw rule record

Verbatim from 09-syntax-and-sentence-rules.json. Also available at /v1/rules/SYN-016.

{
  "id": "SYN-016",
  "name": "Keep correlative pairs balanced",
  "domain": "syntax",
  "layer": "sentence",
  "strength": "hard_constraint",
  "human_logic": "IF BOTH/AND, EITHER/OR, NEITHER/NOR, or NOT ONLY/BUT ALSO joins items, THEN place each half before parallel units ELSE retain.",
  "when": {
    "path": "coordination.correlative_pair",
    "operator": "exists",
    "value": true
  },
  "then": [
    {
      "action": "align",
      "target": "coordination.correlative_positions",
      "require": "parallel_constituent_boundaries"
    }
  ],
  "else": [
    {
      "action": "retain",
      "target": "current_text",
      "reason": "No triggering condition is present."
    }
  ],
  "unless": [],
  "because": "Balanced correlatives show exactly which units are alternatives or additions.",
  "diagnostics": [],
  "examples": {},
  "source_ids": [
    "BK-002",
    "BK-007"
  ],
  "laka": {
    "smallest_sufficient_intervention": true,
    "primary_axes": [
      "scope",
      "depth",
      "magnitude",
      "reversibility"
    ]
  }
}

Other syntax rules

  1. 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
  2. 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
  3. 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
  4. 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
  5. 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
  6. 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
  7. 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
  8. 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