Bow Tie Kreative Writing System
Run the engine

Rules / punctuation

PUN-012 Context default layer: word

Possessive form follows number and style

IF a noun is possessive, THEN apply the declared singular/plural/proper-name convention consistently ELSE retain.

Why the rule exists

Possessive conventions vary slightly, so declared consistency matters.

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.

  • noun.case eq "possessive"

Facts this rule reads

PathSource
noun.case You supply it

Then

  1. apply_policy — target noun.possessive_form

Else

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

LAKA

Smallest sufficient intervention
Yes
Primary axes

Sources

  • Garner's Modern English Usage — Bryan A. Garner
    Modern American usage and editorial judgment.
  • The Copyeditor's Handbook — Amy Einsohn; Marilyn Schwartz
    Professional copyediting practice, grammar, and editorial process.
  • The Chicago Manual of Style — The University of Chicago Press Editorial Staff
    Comprehensive editorial style, grammar, documentation, and publishing.
The raw rule record

Verbatim from 08-punctuation-rules.json. Also available at /v1/rules/PUN-012.

{
  "id": "PUN-012",
  "name": "Possessive form follows number and style",
  "domain": "punctuation",
  "layer": "word",
  "strength": "context_default",
  "human_logic": "IF a noun is possessive, THEN apply the declared singular/plural/proper-name convention consistently ELSE retain.",
  "when": {
    "path": "noun.case",
    "operator": "eq",
    "value": "possessive"
  },
  "then": [
    {
      "action": "apply_policy",
      "target": "noun.possessive_form",
      "policy_from": "document.style.possessives"
    }
  ],
  "else": [
    {
      "action": "retain",
      "target": "current_text",
      "reason": "No triggering condition is present."
    }
  ],
  "unless": [],
  "because": "Possessive conventions vary slightly, so declared consistency matters.",
  "diagnostics": [],
  "examples": {},
  "source_ids": [
    "BK-003",
    "BK-007",
    "BK-039"
  ],
  "laka": {
    "smallest_sufficient_intervention": true,
    "primary_axes": [
      "scope",
      "depth",
      "magnitude",
      "reversibility"
    ]
  }
}

Other punctuation rules

  1. PUN-001 Terminate complete sentences IF a prose sentence is complete, THEN end it with a mark matching statement, direct question, or strong exclamation ELSE keep it joined to its governing structure. Hard constraint
  2. PUN-002 No comma splice IF two independent clauses are joined only by a comma, THEN add a coordinator, use a semicolon, or make two sentences ELSE retain. Hard constraint
  3. PUN-003 Comma before coordinating conjunction IF a coordinating conjunction joins two independent clauses, THEN place a comma before it unless the clauses are very short and unambiguous ELSE retain. Context default
  4. PUN-004 Comma after introductory material IF introductory material is long, clausal, or potentially misread, THEN add a comma before the main clause ELSE use the lightest mark that preserves clarity. Context default
  5. PUN-005 Set off nonrestrictive material IF a modifier adds nonessential information rather than identifying the referent, THEN set it off with paired punctuation ELSE do not set it off. Hard constraint
  6. PUN-006 Do not isolate restrictive material IF a modifier identifies which person or thing is meant, THEN remove punctuation that falsely marks it as optional ELSE evaluate as nonrestrictive. Hard constraint
  7. PUN-007 Serial comma follows declared style IF a series contains three or more coordinated items, THEN apply the selected serial-comma policy consistently AND add a comma when omission causes ambiguity ELSE retain. Context default
  8. PUN-008 Semicolon joins related independent clauses IF two independent clauses are closely related AND no coordinator is used, THEN a semicolon is available ELSE choose another boundary. Context default