Bow Tie Kreative Writing System
Run the engine

Rules / structure

STR-007 Context default layer: section

Section answers one reader question

IF a section answers multiple unrelated reader questions, THEN split and label them ELSE retain.

Why the rule exists

Question-based sections improve findability and reuse.

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.

  • section.unrelated_reader_question_count gt 1

Facts this rule reads

PathSource
section.unrelated_reader_question_count You supply it

Then

  1. split — target section
  2. generate — target section.headings

Else

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

LAKA

Smallest sufficient intervention
Yes
Primary axes

Sources

  • Principles of plain language — Digital.gov / U.S. General Services Administration link
    Design content so the intended audience can find, understand, and use it.
  • DITA 1.3 Technical Content Specification — OASIS link
    Topic-based concept, task, reference, troubleshooting, and reuse architecture.
  • Developing Quality Technical Information — Michelle Carey; Moira Lanyi; Deirdre Longo; et al.
    Quality dimensions for usable technical information.
The raw rule record

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

{
  "id": "STR-007",
  "name": "Section answers one reader question",
  "domain": "structure",
  "layer": "section",
  "strength": "context_default",
  "human_logic": "IF a section answers multiple unrelated reader questions, THEN split and label them ELSE retain.",
  "when": {
    "path": "section.unrelated_reader_question_count",
    "operator": "gt",
    "value": 1
  },
  "then": [
    {
      "action": "split",
      "target": "section",
      "by": "reader_question"
    },
    {
      "action": "generate",
      "target": "section.headings",
      "from": "reader_questions"
    }
  ],
  "else": [
    {
      "action": "retain",
      "target": "current_text",
      "reason": "No triggering condition is present."
    }
  ],
  "unless": [],
  "because": "Question-based sections improve findability and reuse.",
  "diagnostics": [],
  "examples": {},
  "source_ids": [
    "WEB-002",
    "WEB-008",
    "BK-024"
  ],
  "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-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
  8. STR-009 Maintain heading hierarchy IF heading levels skip or reflect visual size rather than logical nesting, THEN repair the hierarchy ELSE retain. Hard constraint