Bow Tie Kreative Writing System
Run the engine

Rules / structure

STR-012 Context default layer: section

Introduce lists with a clear purpose

IF a list appears, THEN make its category or task clear in a heading or lead-in ELSE retain.

Why the rule exists

Readers need to know what the items have in common.

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.

  • list.exists eq true

Facts this rule reads

PathSource
list.exists You supply it

Then

  1. verify — target list.introduction
  2. insert — target list.lead_in

Else

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

LAKA

Smallest sufficient intervention
Yes
Primary axes

Sources

  • Google Developer Documentation Style Guide — Google link
    Clear, consistent, audience-directed technical documentation.
  • Microsoft Writing Style Guide — Microsoft link
    Warm, clear, concise, helpful technical communication.
The raw rule record

Verbatim from 10-paragraph-document-rules.json. Also available at /v1/rules/STR-012.

{
  "id": "STR-012",
  "name": "Introduce lists with a clear purpose",
  "domain": "structure",
  "layer": "section",
  "strength": "context_default",
  "human_logic": "IF a list appears, THEN make its category or task clear in a heading or lead-in ELSE retain.",
  "when": {
    "path": "list.exists",
    "operator": "eq",
    "value": true
  },
  "then": [
    {
      "action": "verify",
      "target": "list.introduction",
      "require": "clear_category_or_task"
    },
    {
      "action": "insert",
      "target": "list.lead_in",
      "when": "missing"
    }
  ],
  "else": [
    {
      "action": "retain",
      "target": "current_text",
      "reason": "No triggering condition is present."
    }
  ],
  "unless": [],
  "because": "Readers need to know what the items have in common.",
  "diagnostics": [],
  "examples": {},
  "source_ids": [
    "WEB-003",
    "WEB-004"
  ],
  "laka": {
    "smallest_sufficient_intervention": true,
    "primary_axes": [
      "scope",
      "depth",
      "magnitude",
      "reversibility"
    ]
  }
}

Other structure rules

  1. STR-001 One controlling move per paragraph IF a paragraph performs more than one unrelated rhetorical move, THEN split it at the move boundary ELSE retain. Context default
  2. STR-002 Expose the paragraph point IF the paragraph’s controlling point is absent or recoverable only after rereading, THEN state or move it to a strategic position ELSE retain an intentional delayed reveal. Heuristic
  3. STR-003 Support consequential claims IF a paragraph makes a consequential factual claim, THEN provide evidence, cite it, qualify it, or remove the claim ELSE retain. Hard constraint
  4. STR-004 Keep evidence beside the claim IF evidence is separated from the claim it supports by unrelated material, THEN move it closer or label the relation ELSE retain. Context default
  5. STR-005 Use transitions that name the relation IF adjacent paragraphs have a meaningful but unstated relation, THEN add a transition that expresses that relation ELSE retain. Context default
  6. STR-006 Delete orphan paragraphs IF a paragraph neither advances the purpose nor supports another necessary move, THEN delete or relocate it ELSE retain. Heuristic
  7. STR-007 Section answers one reader question IF a section answers multiple unrelated reader questions, THEN split and label them ELSE retain. Context default
  8. STR-008 Heading predicts content IF a heading does not accurately predict its section, THEN rename the heading or repair the section ELSE retain. Hard constraint