Bow Tie Kreative Writing System
Run the engine

Rules / clarity

CLR-008 Heuristic layer: paragraph

Use concrete examples after abstractions

IF a central abstraction lacks a concrete instance AND the audience knowledge gap is moderate or large, THEN add one representative example ELSE retain.

Why the rule exists

Examples let readers test an abstract model against a concrete case.

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
    • paragraph.central_abstraction exists true
    • paragraph.example_count eq 0
    • context.knowledge_gap in [moderate, large, unknown]

Facts this rule reads

PathSource
paragraph.central_abstraction You supply it
paragraph.example_count You supply it
context.knowledge_gap You supply it

Then

  1. insert — target paragraph.example

Else

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

LAKA

Smallest sufficient intervention
Yes
Primary axes

Sources

  • The Sense of Style — Steven Pinker
    Reader-centered clarity informed by linguistics and cognition.
  • On Writing Well — William Zinsser
    Clarity, simplicity, voice, and nonfiction craft.
  • Made to Stick — Chip Heath; Dan Heath
    Simple, unexpected, concrete, credible, emotional stories.
The raw rule record

Verbatim from 11-clarity-style-rules.json. Also available at /v1/rules/CLR-008.

{
  "id": "CLR-008",
  "name": "Use concrete examples after abstractions",
  "domain": "clarity",
  "layer": "paragraph",
  "strength": "heuristic",
  "human_logic": "IF a central abstraction lacks a concrete instance AND the audience knowledge gap is moderate or large, THEN add one representative example ELSE retain.",
  "when": {
    "all": [
      {
        "path": "paragraph.central_abstraction",
        "operator": "exists",
        "value": true
      },
      {
        "path": "paragraph.example_count",
        "operator": "eq",
        "value": 0
      },
      {
        "path": "context.knowledge_gap",
        "operator": "in",
        "value": [
          "moderate",
          "large",
          "unknown"
        ]
      }
    ]
  },
  "then": [
    {
      "action": "insert",
      "target": "paragraph.example",
      "require": [
        "representative",
        "clearly_labeled",
        "boundary_not_overgeneralized"
      ]
    }
  ],
  "else": [
    {
      "action": "retain",
      "target": "current_text",
      "reason": "No triggering condition is present."
    }
  ],
  "unless": [],
  "because": "Examples let readers test an abstract model against a concrete case.",
  "diagnostics": [],
  "examples": {},
  "source_ids": [
    "BK-008",
    "BK-013",
    "BK-037"
  ],
  "laka": {
    "smallest_sufficient_intervention": true,
    "primary_axes": [
      "scope",
      "depth",
      "magnitude",
      "reversibility"
    ]
  }
}

Other clarity rules

  1. CLR-001 Prefer the precise familiar word IF two words are equally accurate AND one is more familiar to the audience, THEN use the familiar word ELSE keep the precision-bearing term. Context default
  2. CLR-002 Define necessary jargon IF a domain term is necessary AND the intended reader may not know it, THEN define it at first use and use it consistently ELSE replace it with plain language. Context default
  3. CLR-003 Expand unfamiliar abbreviations IF an abbreviation is not universally familiar to the audience, THEN spell it out at first use and pair it with the abbreviation ELSE retain. Context default
  4. CLR-004 One term per concept IF multiple terms refer to the same technical concept without rhetorical need, THEN select one preferred term and replace the variants ELSE retain. Context default
  5. CLR-005 One concept per term IF the same term denotes multiple concepts in one context, THEN rename or qualify the concepts ELSE retain. Hard constraint
  6. CLR-006 Replace vague reference words IF THIS, THAT, IT, THEY, FORMER, or LATTER has an uncertain referent, THEN repeat or summarize the referent ELSE retain. Hard constraint
  7. CLR-007 Quantify actionable vagueness IF vague quantity, frequency, time, or probability affects a decision, THEN provide a range, threshold, date, or defined category ELSE retain approximate language. Context default
  8. CLR-009 State implied steps for novice readers IF success requires an unstated inference that a novice may not make, THEN state the step or prerequisite ELSE retain expert compression. Context default