Bow Tie Kreative Writing System

Rules / editing

EDT-010 Heuristic layer: document

Reverse proofread for surface errors

IF content is structurally final and proofreading is active, THEN inspect sentences or lines in reverse order for local mechanics ELSE do not use reverse order for meaning review.

Why the rule exists

Reverse order weakens semantic prediction and exposes local surface errors.

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
    • document.structure_final eq true
    • edit.pass eq "proofread"

Facts this rule reads

Fact paths read by EDT-010 and whether the analyser derives them
PathSource
document.structure_final You supply it
edit.pass You supply it

Then

  1. inspect — target document

Else

  1. 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 raw rule record

Verbatim from 19-editing-diagnostic-rules.json. Also available at /v1/rules/EDT-010.

{
  "id": "EDT-010",
  "name": "Reverse proofread for surface errors",
  "domain": "editing",
  "layer": "document",
  "strength": "heuristic",
  "human_logic": "IF content is structurally final and proofreading is active, THEN inspect sentences or lines in reverse order for local mechanics ELSE do not use reverse order for meaning review.",
  "when": {
    "all": [
      {
        "path": "document.structure_final",
        "operator": "eq",
        "value": true
      },
      {
        "path": "edit.pass",
        "operator": "eq",
        "value": "proofread"
      }
    ]
  },
  "then": [
    {
      "action": "inspect",
      "target": "document",
      "order": "reverse",
      "focus": [
        "spelling",
        "punctuation",
        "formatting",
        "duplication"
      ]
    }
  ],
  "else": [
    {
      "action": "retain",
      "target": "current_text",
      "reason": "No triggering condition is present."
    }
  ],
  "unless": [],
  "because": "Reverse order weakens semantic prediction and exposes local surface errors.",
  "diagnostics": [],
  "examples": {},
  "source_ids": [
    "BK-007"
  ],
  "laka": {
    "smallest_sufficient_intervention": true,
    "primary_axes": [
      "scope",
      "depth",
      "magnitude",
      "reversibility"
    ]
  }
}

Other editing rules

  1. EDT-001 Do not polish before purpose is stable IF audience, purpose, outcome, or controlling idea is unresolved, THEN perform strategy or developmental editing before line editing ELSE continue. Hard constraint
  2. EDT-002 Separate editing passes IF one pass attempts strategy, structure, evidence, style, mechanics, and proofing simultaneously, THEN separate the passes ELSE retain. Context default
  3. EDT-003 Protect meaning before changing form IF an edit changes denotation, scope, polarity, actor, time, modality, evidence strength, or legal effect without authorization, THEN reject or escalate it ELSE retain. Hard constraint
  4. EDT-004 Apply smallest sufficient intervention IF a diagnosed failure can be fixed at a lower layer without creating another failure, THEN use that lower-layer fix ELSE escalate one layer. Context default
  5. EDT-005 Track the reason for substantive edits IF an edit changes argument, order, emphasis, evidence, obligation, or reader action, THEN attach a concise rationale ELSE silent mechanical correction is allowed by policy. Context default
  6. EDT-006 Style sheet records local decisions IF spelling, capitalization, hyphenation, numerals, terminology, citation, locale, or exceptions repeat, THEN record the decision in a style sheet ELSE retain. Context default
  7. EDT-007 Query instead of guessing intent IF two plausible interpretations require different edits and context cannot resolve them, THEN ask a focused query ELSE edit. Hard constraint
  8. EDT-008 Verify facts outside copyediting scope IF names, dates, numbers, citations, quotations, links, calculations, or cross-references are present, THEN verify according to assignment scope and flag the rest ELSE retain. Context default