Bow Tie Kreative Writing System
Run the engine

The rules

Every rule, and how hard it binds

228 base rules across 14 domains and 9 structural layers. Filter them, then open one to see its condition tree, both branches, its exceptions and its sources.

16 rules match. Clear filters

  1. SYN-006 One principal action per procedural step IF a step contains multiple independently verifiable actions, THEN split them into ordered steps ELSE retain a tightly coupled action. Context default
  2. STR-007 Section answers one reader question IF a section answers multiple unrelated reader questions, THEN split and label them ELSE retain. Context default
  3. STR-011 Order by reader task IF the document supports an action, THEN order information by the reader’s task rather than the organization’s internal structure ELSE select chronological, causal, spatial, or importance order. Context default
  4. STR-018 Separate reusable topics IF a unit has one subject, independent value, and repeated reuse, THEN make it a standalone topic with links ELSE keep it in context. Heuristic
  5. STR-020 Apply progressive disclosure IF novice and expert readers share a document, THEN put the essential path first and route detail to optional layers ELSE match one depth to the known audience. Heuristic
  6. CLR-018 Test instructions by execution IF content instructs a real task, THEN have a representative reader or test environment execute it and record failures ELSE review semantically. Hard constraint
  7. TEC-001 Choose an information type IF a technical topic is being created, THEN classify it as concept, task, reference, troubleshooting, glossary, or mixed with explicit boundaries ELSE do not draft a generic blob. Hard constraint
  8. TEC-002 Concept answers what and why IF the reader asks what something is or why it matters, THEN use a concept topic with definition, model, relationship, boundary, and example ELSE select another type. Context default
  9. TEC-003 Task answers how to achieve a goal IF the reader wants to achieve an outcome, THEN use a task topic with goal, prerequisites, steps, results, recovery, and verification ELSE select another type. Context default
  10. TEC-004 Reference supports lookup IF the reader needs facts about an entity or interface, THEN use stable repeated fields, valid values, defaults, constraints, examples, and links ELSE select another type. Context default
  11. TEC-005 Prerequisites before steps IF a task requires permissions, state, tools, knowledge, inputs, or safety conditions, THEN list them before step 1 ELSE state that none are required only when useful. Hard constraint
  12. TEC-007 Expected result follows uncertain action IF a step’s success is not self-evident, THEN state the observable result immediately after it ELSE retain. Context default
  13. TEC-008 Recovery follows known failure IF a step has a common or consequential failure mode, THEN provide symptom, cause or check, corrective action, and verification ELSE retain. Context default
  14. TEC-009 Troubleshooting begins with observable symptom IF troubleshooting advice begins with an assumed cause, THEN reframe from the user-observable symptom and branch by tests ELSE retain. Hard constraint
  15. TEC-019 Reuse single-source facts IF the same volatile fact appears in multiple documents, THEN centralize it or generate references from one source ELSE retain independent stable statements. Heuristic
  16. EDT-012 Regression-check dependent text IF terminology, fact, interface label, promise, or structural link changes, THEN search and test dependent occurrences ELSE retain. Hard constraint