Bow Tie Kreative Writing System
Run the engine

Rules / clarity

CLR-010 Heuristic layer: sentence

Prefer positive formulation

IF a negative construction can be stated positively with the same meaning and no safety loss, THEN use the positive form ELSE retain necessary prohibitions.

Why the rule exists

Positive statements often reduce mental reversal.

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
    • sentence.negative_form eq true
    • sentence.positive_equivalent_same_meaning eq true
    • sentence.prohibition_needed eq false

Facts this rule reads

PathSource
sentence.negative_form You supply it
sentence.positive_equivalent_same_meaning You supply it
sentence.prohibition_needed You supply it

Then

  1. replace — target sentence.polarity, value "positive_equivalent"

Else

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

LAKA

Smallest sufficient intervention
Yes
Primary axes

Sources

  • The Elements of Style — William Strunk Jr.; E. B. White
    Conciseness, conventional usage, and composition principles.
  • Principles of plain language — Digital.gov / U.S. General Services Administration link
    Design content so the intended audience can find, understand, and use it.
  • Making Content Usable for People with Cognitive and Learning Disabilities — W3C link
    Clear words, simple voice and tense, explicit instructions, and supportive structure.
The raw rule record

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

{
  "id": "CLR-010",
  "name": "Prefer positive formulation",
  "domain": "clarity",
  "layer": "sentence",
  "strength": "heuristic",
  "human_logic": "IF a negative construction can be stated positively with the same meaning and no safety loss, THEN use the positive form ELSE retain necessary prohibitions.",
  "when": {
    "all": [
      {
        "path": "sentence.negative_form",
        "operator": "eq",
        "value": true
      },
      {
        "path": "sentence.positive_equivalent_same_meaning",
        "operator": "eq",
        "value": true
      },
      {
        "path": "sentence.prohibition_needed",
        "operator": "eq",
        "value": false
      }
    ]
  },
  "then": [
    {
      "action": "replace",
      "target": "sentence.polarity",
      "value": "positive_equivalent"
    }
  ],
  "else": [
    {
      "action": "retain",
      "target": "current_text",
      "reason": "No triggering condition is present."
    }
  ],
  "unless": [],
  "because": "Positive statements often reduce mental reversal.",
  "diagnostics": [],
  "examples": {},
  "source_ids": [
    "BK-001",
    "WEB-002",
    "WEB-006"
  ],
  "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-008 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. Heuristic