schematex 0.9.3 → 0.9.5

package/dist/{chunk-JCJWSW5Y.js → chunk-N524SY5D.js}

@@ -1,4 +1,4 @@
-import { parseResult, renderResult } from './chunk-BP6MLXJU.js';
+import { parseResult, renderResult } from './chunk-LMNWUZMD.js';
 
 // src/ai/registry.ts
 var DIAGRAM_REGISTRY = [
@@ -387,6 +387,34 @@ var DIAGRAM_REGISTRY = [
       "IEC 60812"
     ]
   },
+  {
+    type: "rbd",
+    name: "Reliability Block Diagram (RBD)",
+    tagline: "The success-logic diagram that computes its own system reliability \u2014 series/parallel/k-of-n reduction, Birnbaum importance, and single-point-of-failure detection.",
+    useWhen: 'Use to model whether a system *works* from the reliability of its components, and to compute the overall figure \u2014 RAMS analysis, redundancy/high-availability design, fault-tolerance trade studies. Header `rbd`; nest `series { \u2026 }`, `parallel { \u2026 }`, and `kofn k/n { \u2026 }` success-logic groups around `block ID "Label" R=0.99` leaves (`p=0.01` failure prob or `R=99%` also accepted). The engine computes system reliability (\u220F for series, 1\u2212\u220F(1\u2212R\u1D62) for parallel, exact k-of-n), the Birnbaum reliability-importance of every block, and flags blocks whose failure alone fails the system (SPOF, drawn in red). Sibling of fault tree (\xA737) in the risk-reliability cluster.',
+    cluster: "risk-reliability",
+    standard: "IEC 61078:2016 \xB7 MIL-HDBK-338B; see 50-RBD-STANDARD.md",
+    syntaxKey: "rbd",
+    aliases: [
+      "RBD",
+      "Reliability Block Diagram",
+      "reliability diagram",
+      "availability block diagram",
+      "\u53EF\u9760\u6027\u6846\u56FE"
+    ],
+    keywords: [
+      "IEC 61078",
+      "system reliability",
+      "redundancy",
+      "series parallel",
+      "k-out-of-n",
+      "high availability",
+      "RAMS",
+      "Birnbaum importance",
+      "single point of failure",
+      "fault tolerance"
+    ]
+  },
   // ── Systems thinking / stochastic ────────────────────────────
   {
     type: "causalloop",
@@ -595,6 +623,36 @@ var DIAGRAM_REGISTRY = [
       "furniture placement",
       "space planning"
     ]
+  },
+  {
+    type: "playbook",
+    name: "Sports playbook",
+    tagline: "Multi-sport tactics boards from one paragraph of text \u2014 American football X&O, basketball half-court sets, and soccer team shapes drawn in coaching-standard notation, each sport on its own correctly-scaled field/court/pitch.",
+    useWhen: 'Use to diagram a single play, set, or team shape for American football, basketball, or soccer. Header `playbook "Title" sport football|basketball|soccer`. Place players by formation (football `formation i-form|spread|trips|...`, basketball `set horns|spread-pnr|5-out|...`, soccer `formation 4-3-3|4-4-2|...`) or individually with `player`. Draw assignments with movement verbs whose line style is coaching-correct per sport: football `route X go` / `run RB power right` / `block` / `pull` / `handoff` (solid routes, arrowheads, block T-bars) on a yard-scaled field with LOS, hashes, end zone and goalposts; basketball `pass` (dashed) / `cut` (solid) / `dribble` (wavy) / `screen` (T-bar) to named landmarks (rim, elbow, wing, corner) on an NBA half-court; soccer `pass` (solid) / `run` (dashed) / `dribble` (wavy) / `shot` on an IFAB pitch. Optional `defense` overlays man/zone shells. The engine resolves formations, named routes, and landmarks, and renders each sport in its own coordinate model. Not for play-by-play game film, statistics, or league-table graphics.',
+    cluster: "sports",
+    standard: "American Football Coaches Association X&O convention \xB7 FIBA/NBA half-court markings \xB7 IFAB Laws of the Game pitch (Law 1); see 49-SPORTS-PLAYBOOK-STANDARD.md",
+    syntaxKey: "playbook",
+    aliases: [
+      "Sports playbook",
+      "playbook",
+      "football play",
+      "X and O diagram",
+      "basketball play",
+      "soccer tactics",
+      "\u6218\u672F\u677F",
+      "\u6218\u672F\u56FE"
+    ],
+    keywords: [
+      "playbook",
+      "football play",
+      "X's and O's",
+      "basketball play",
+      "pick and roll",
+      "soccer formation",
+      "tactics board",
+      "route tree",
+      "coaching diagram"
+    ]
   }
 ];
 var DIAGRAM_SINCE = {
@@ -658,7 +716,11 @@ var DIAGRAM_SINCE = {
   // 0.8.1 — welding symbols (AWS A2.4 / ISO 2553)
   welding: "0.8.1",
   // 0.9.3
-  floorplan: "0.9.3"
+  floorplan: "0.9.3",
+  // 0.9.4 — multi-sport playbook (football X&O / basketball / soccer)
+  playbook: "0.9.4",
+  // 0.9.5 — reliability block diagram (IEC 61078)
+  rbd: "0.9.5"
 };
 function getDiagramSince(type) {
   const resolved = resolveDiagramType(type);
@@ -3126,6 +3188,261 @@ If the LED doesn't light up, three things to check, in order: LED polarity (the
 
 **Why P&ID, not PFD.** A process flow diagram (PFD) shows the same equipment but only the major process streams, mass balances, and operating conditions. A P&ID adds every instrument, every valve, every signal line, and every utility connection \u2014 it is the engineering document used by instrument engineers to write I/O lists, by safety engineers to perform HAZOP, and by construction teams to verify field installation. The DSL lets you build this level of detail from text, making it tractable for AI-assisted first drafts and version-controlled review cycles.`
   },
+  {
+    "slug": "playbook-basketball-backdoor",
+    "diagram": "playbook",
+    "title": "Backdoor Cut",
+    "description": "When the defender overplays the passing lane, cut behind him to the rim.",
+    "standard": "FIBA/NBA half-court markings \xB7 coaching legend",
+    "tags": [
+      "basketball",
+      "backdoor",
+      "cutting",
+      "Princeton"
+    ],
+    "complexity": 1,
+    "featured": false,
+    "dsl": 'playbook "Backdoor Cut" sport basketball\nset 5-out\ncut 3 rim\npass 1 to 4,6',
+    "notes": "The **backdoor** punishes a defender who denies the wing too aggressively: the wing `cut`s behind him to the `rim` and the top passes to the cutter (`pass 1 to 4,6`) for an easy finish. A staple of Princeton and motion offense."
+  },
+  {
+    "slug": "playbook-basketball-floppy",
+    "diagram": "playbook",
+    "title": "Floppy Action",
+    "description": "A shooter chooses a single or double screen off the baseline to get open on the wing.",
+    "standard": "FIBA/NBA half-court markings \xB7 coaching legend",
+    "tags": [
+      "basketball",
+      "floppy",
+      "off-ball-screens",
+      "shooting"
+    ],
+    "complexity": 3,
+    "featured": false,
+    "dsl": 'playbook "Floppy Action" sport basketball\nset 1-4-low\nscreen 4 2\nscreen 5 3\ncut 2 lwing\npass 1 2',
+    "notes": "**Floppy** starts a shooter under the basket with a single screen on one side and a double on the other. Reading the defense, the shooter curls off a screen (`screen 4 2`) up to the wing (`cut 2 lwing`) for a catch-and-shoot \u2014 `pass 1 2`."
+  },
+  {
+    "slug": "playbook-basketball-give-and-go",
+    "diagram": "playbook",
+    "title": "Give & Go",
+    "description": "The oldest play in basketball \u2014 pass, cut to the basket, get it back.",
+    "standard": "FIBA/NBA half-court markings \xB7 coaching legend",
+    "tags": [
+      "basketball",
+      "give-and-go",
+      "cutting",
+      "fundamentals"
+    ],
+    "complexity": 1,
+    "featured": false,
+    "dsl": 'playbook "Give & Go" sport basketball\nset 5-out\npass 1 2\ncut 1 rim\npass 2 1',
+    "notes": "The **give & go** is the first play every player learns: `pass` to a teammate, `cut` hard to the `rim`, and receive the return `pass` for a layup. Shown from a `5-out` alignment so the lane is empty for the cut."
+  },
+  {
+    "slug": "playbook-basketball-horns",
+    "diagram": "playbook",
+    "title": "Horns Twist",
+    "description": "A two-big set at the elbows that creates a ball screen with a re-screen counter.",
+    "standard": "FIBA/NBA half-court markings \xB7 coaching legend",
+    "tags": [
+      "basketball",
+      "horns",
+      "ball-screen",
+      "set-play"
+    ],
+    "complexity": 3,
+    "featured": false,
+    "dsl": 'playbook "Horns Twist" sport basketball\nset horns\nscreen 5 1\ndribble 1 to 11,16\ncut 5 rim\ncut 4 to 0,26\npass 1 3',
+    "notes": "**Horns** places two bigs at the elbows and two shooters in the corners. One big screens for the ball (`screen 5 1`) and rolls to the `rim` while the second pops to the top (`cut 4`), giving the ball-handler a roll-or-pop read plus a corner skip (`pass 1 3`)."
+  },
+  {
+    "slug": "playbook-basketball-pick-and-roll",
+    "diagram": "playbook",
+    "title": "Spread Pick & Roll",
+    "description": "The defining action of modern basketball \u2014 a ball screen with four shooters spacing the floor.",
+    "standard": "FIBA/NBA half-court markings \xB7 coaching legend",
+    "tags": [
+      "basketball",
+      "pick-and-roll",
+      "spacing",
+      "half-court"
+    ],
+    "complexity": 2,
+    "featured": true,
+    "dsl": 'playbook "Spread Pick & Roll" sport basketball\nset spread-pnr\nscreen 5 1\ndribble 1 to 11,17\ncut 5 rim\npass 1 2',
+    "notes": "The **pick & roll** is the most-run action in the sport. The big (`screen 5 1`) sets a ball screen, the guard `dribble`s off it, and the screener `cut`s (rolls) to the `rim`. With the other three players spaced behind the arc, help defense leaves a shooter open \u2014 `pass 1 2`. Note the basketball legend: dashed = pass, solid = cut, wavy = dribble."
+  },
+  {
+    "slug": "playbook-football-four-verticals",
+    "diagram": "playbook",
+    "title": "Four Verticals (vs Cover 2)",
+    "description": "The Air Raid staple \u2014 four receivers run vertical, stretching a two-deep shell until a seam opens.",
+    "standard": "AFCA X&O convention \xB7 NFL/NCAA Rule 1 field",
+    "tags": [
+      "football",
+      "passing",
+      "air-raid",
+      "cover-2"
+    ],
+    "complexity": 2,
+    "featured": true,
+    "dsl": 'playbook "Four Verticals" sport football\nfield down 2 distance 7 los 40\nformation spread\ndefense cover-2\nroute X go\nroute H seam\nroute Y seam\nroute Z go\nroute RB flat right',
+    "notes": "**Four Verticals** floods a two-deep coverage with four vertical threats: the outside receivers run `go` routes up the sidelines while the inner two bend to the `seam`, forcing the two deep safeties to choose. The back leaks to the `flat` as a checkdown. Drawn out of `spread` against `cover-2`, with each route on the football route tree."
+  },
+  {
+    "slug": "playbook-football-mesh",
+    "diagram": "playbook",
+    "title": "Mesh Concept",
+    "description": "Two shallow crossers rub underneath while a corner route clears the top \u2014 the classic man-and-zone beater.",
+    "standard": "AFCA X&O convention \xB7 NFL/NCAA Rule 1 field",
+    "tags": [
+      "football",
+      "passing",
+      "mesh",
+      "crossers"
+    ],
+    "complexity": 3,
+    "featured": false,
+    "dsl": 'playbook "Mesh Concept" sport football\nfield down 1 distance 10 los 35\nformation spread\ndefense cover-3\nroute Y drag\nroute H cross\nroute Z corner 12\nroute X hitch\nroute RB flat right',
+    "notes": "**Mesh** sends two receivers on shallow crossing routes (`drag` and `cross`) that brush past each other just over the ball, creating a natural rub against man coverage and a moving window against zone. The `corner` route clears the deep defender and the `hitch` plus `flat` give quick outlets."
+  },
+  {
+    "slug": "playbook-football-power-o",
+    "diagram": "playbook",
+    "title": "Power O",
+    "description": "The most-installed gap run in football \u2014 backside guard pulls to lead through the hole.",
+    "standard": "AFCA X&O convention \xB7 NFL/NCAA Rule 1 field",
+    "tags": [
+      "football",
+      "run",
+      "power",
+      "gap-scheme"
+    ],
+    "complexity": 3,
+    "featured": false,
+    "dsl": 'playbook "Power O" sport football\nfield down 1 distance 10 los 35\nformation i-form right\ndefense 4-3\nhandoff QB RB\nrun RB power right\npull LG right\nblock FB DE_S\nroute Z go',
+    "notes": "**Power O** is the foundational gap run: the play-side blocks down, the fullback kicks out the edge, and the backside guard (`pull LG`) wraps through the hole to lead for the back. Drawn from `i-form` against a `4-3` front with the handoff and pulling lineman shown."
+  },
+  {
+    "slug": "playbook-football-red-zone-fade",
+    "diagram": "playbook",
+    "title": "Red Zone \u2014 Play-Action Fade",
+    "description": "A goal-line play-action shot showing the end zone, goal line, and goalposts.",
+    "standard": "AFCA X&O convention \xB7 NFL/NCAA Rule 1 field",
+    "tags": [
+      "football",
+      "red-zone",
+      "play-action",
+      "fade"
+    ],
+    "complexity": 2,
+    "featured": false,
+    "dsl": 'playbook "Red Zone \u2014 Play-Action Fade" sport football\nfield down 1 distance 5 los 5 goal 5 hash nfl\nformation i-form right\ndefense cover-1\nhandoff QB RB\nroute Z corner 4\nroute X slant\nroute Y out 3\nrun RB dive right',
+    "notes": "Inside the 5-yard line the field changes: `goal 5` draws the end zone band, gold goal line, and goalposts. The play fakes the `dive` (`handoff` + `run`) to freeze the linebackers, then throws the back-corner `fade` with a `slant` and `out` as alternatives against `cover-1`."
+  },
+  {
+    "slug": "playbook-football-smash",
+    "diagram": "playbook",
+    "title": "Smash Concept",
+    "description": "A corner-over-hitch high-low that puts the cornerback in a bind \u2014 the textbook Cover 2 beater.",
+    "standard": "AFCA X&O convention \xB7 NFL/NCAA Rule 1 field",
+    "tags": [
+      "football",
+      "passing",
+      "smash",
+      "cover-2"
+    ],
+    "complexity": 2,
+    "featured": false,
+    "dsl": 'playbook "Smash Concept" sport football\nfield down 3 distance 6 los 45\nformation trips right\ndefense cover-2\nroute Z hitch\nroute Y corner 12\nroute X slant\nroute H flat right',
+    "notes": "**Smash** pairs a `hitch` underneath with a `corner` route over the top on the same side. The flat defender can cover one but not both: jump the hitch and the corner is open behind him; sink to the corner and the hitch sits down in front. Shown from `trips right` against `cover-2`."
+  },
+  {
+    "slug": "playbook-soccer-4-3-3-shape",
+    "diagram": "playbook",
+    "title": "4-3-3 Team Shape",
+    "description": "The default possession shape \u2014 a back four, a midfield three, and a front three.",
+    "standard": "IFAB Laws of the Game, Law 1 (pitch)",
+    "tags": [
+      "soccer",
+      "formation",
+      "4-3-3",
+      "shape"
+    ],
+    "complexity": 1,
+    "featured": true,
+    "dsl": 'playbook "4-3-3 Team Shape" sport soccer\nformation 4-3-3',
+    "notes": "A formation on its own draws the **team shape**. The **4-3-3** \u2014 four defenders, three midfielders, three forwards \u2014 is the modern possession default, giving width through the wingers and a passing triangle in midfield. Players are numbered by position on a full IFAB pitch."
+  },
+  {
+    "slug": "playbook-soccer-build-up",
+    "diagram": "playbook",
+    "title": "Build-Up From the Back",
+    "description": "Playing out of the defensive third \u2014 split the centre-backs, invite pressure, pass through the lines.",
+    "standard": "IFAB Laws of the Game, Law 1 (pitch)",
+    "tags": [
+      "soccer",
+      "build-up",
+      "possession",
+      "passing"
+    ],
+    "complexity": 2,
+    "featured": false,
+    "dsl": 'playbook "Build-Up From the Back" sport soccer\nformation 4-3-3\npass 1 4\npass 4 2\nrun 2 to 40,10\npass 4 6\nrun 6 to 62,24',
+    "notes": "**Building from the back** starts with the keeper (`pass 1 4`) and works the ball through the centre-back and full-back while the pivot drops to receive. Soccer draws passes **solid** and runs **dashed** \u2014 note the full-back's overlapping `run` and the pivot turning forward."
+  },
+  {
+    "slug": "playbook-soccer-counter-attack",
+    "diagram": "playbook",
+    "title": "Counter-Attack",
+    "description": "Win it in midfield and go \u2014 a vertical pass, a driving carry, and three forwards sprinting in behind.",
+    "standard": "IFAB Laws of the Game, Law 1 (pitch)",
+    "tags": [
+      "soccer",
+      "counter-attack",
+      "transition",
+      "through-ball"
+    ],
+    "complexity": 3,
+    "featured": false,
+    "dsl": 'playbook "Counter-Attack" sport soccer\nformation 4-3-3\npass 6 8\ndribble 8 to 66,28\npass 8 to 96,18\nrun 7 to 99,20\nrun 9 to 94,36\nrun 11 to 95,52',
+    "notes": "On the **counter**, speed beats numbers. The pivot wins it and finds a midfielder (`pass 6 8`) who carries into space (`dribble`), then releases a `pass` through ball as all three forwards sprint in behind (`run`). The solid pass + dashed runs read instantly as a transition moment."
+  },
+  {
+    "slug": "playbook-soccer-high-press",
+    "diagram": "playbook",
+    "title": "High Press 4-3-3",
+    "description": "Coordinated forward pressure \u2014 the front three and a midfielder hunt the ball in the opponent's half.",
+    "standard": "IFAB Laws of the Game, Law 1 (pitch)",
+    "tags": [
+      "soccer",
+      "high-press",
+      "gegenpress",
+      "defending"
+    ],
+    "complexity": 2,
+    "featured": false,
+    "dsl": 'playbook "High Press 4-3-3" sport soccer\nformation 4-3-3\nrun 9 to 98,34\nrun 7 to 94,20\nrun 11 to 94,48\nrun 8 to 76,40',
+    "notes": "A **high press** wins the ball back near the opponent's goal. The striker leads the press onto the centre-backs while the wingers curve their `run`s to cut the passing lanes to the full-backs, and a midfielder steps up to support \u2014 the coordinated forward movement that defines the gegenpress."
+  },
+  {
+    "slug": "playbook-soccer-overlap",
+    "diagram": "playbook",
+    "title": "Overlap & Cross",
+    "description": "The full-back overlaps the winger to get to the byline and deliver a cross into the box.",
+    "standard": "IFAB Laws of the Game, Law 1 (pitch)",
+    "tags": [
+      "soccer",
+      "overlap",
+      "cross",
+      "wide-play"
+    ],
+    "complexity": 3,
+    "featured": false,
+    "dsl": 'playbook "Overlap & Cross" sport soccer\nview half\nplayer 7 o at 75,12 label 7\nplayer 2 o at 60,15 label 2\nplayer 9 o at 88,30 label 9\nplayer 11 o at 85,52 label 11\nplayer 10 o at 80,38 label 10\ndribble 7 to 82,20\nrun 2 to 90,8\npass 7 to 90,8\npass 2 to 102,34\nrun 9 to 101,31\nrun 11 to 101,40',
+    "notes": "The **overlap** combines the winger and full-back: the winger drives inside (`dribble`) to fix the defender while the full-back `run`s outside and overlaps. The release pass down the line (`pass 7 to 90,8`) sets up a byline cross to the strikers attacking the box. Drawn with `view half` and explicit players for full control."
+  },
   {
     "slug": "prisma-dual-pipeline",
     "diagram": "prisma",
@@ -3164,6 +3481,114 @@ If the LED doesn't light up, three things to check, in order: LED polarity (the
     "dsl": "prisma\nmode: 2020-single\ntitle: Effect of exercise on chronic low-back pain \u2014 SR\n\nidentification:\n  databases:\n    n: 1418\n    sources: PubMed=600, Embase=450, Cochrane=184, Web of Science=184\n    duplicates-removed: 318\n\nscreening:\n  records-screened: 1100\n  excluded:\n    n: 870\n    reasons: irrelevant title=750, non-English=120\n\neligibility:\n  full-text-assessed: 230\n  excluded:\n    n: 195\n    reasons: wrong population=80, wrong intervention=60, wrong outcome=55\n\nincluded:\n  studies: 35\n  reports: 38",
     "notes": '## Scenario\n\nA research librarian produces the PRISMA 2020 flow diagram for a Cochrane review submission. The journal **requires** the diagram in the exact four-row structure \u2014 Identification \u2192 Screening \u2192 Eligibility \u2192 Included \u2014 with the count `(n = \u2026)` shown in every box and the excluded boxes itemizing reasons. With the dedicated `prisma` engine the librarian writes only counts and reasons; the rigid layout, the "Records removed before screening" side-box, and the exclusion side-boxes are produced automatically and are correct by construction.\n\n## Annotation key\n\n- **`mode: 2020-single`** \u2014 one Identification column (databases & registers). Use `mode: 2020-dual` to add the "other methods" column.\n- **`identification.databases`** \u2014 `n:` is the mandatory total; `sources:` renders the per-database breakdown; `duplicates-removed:` splits out into the right-column "Records removed before screening" box automatically.\n- **`screening` / `eligibility` `excluded:` blocks** \u2014 each has its own `n:` total and an optional `reasons:` breakdown rendered in a side-box to the right, connected by a horizontal arrow.\n- **`included.studies` / `reports`** \u2014 one study can yield several reports, so both counts render.\n\n## How to read\n\nTop to bottom mirrors the PRISMA 2020 template exactly. The left capsule bands label the three canonical stages; the orange bar spans the Identification column group. Counts reconcile across stages (1418 \u2212 318 = 1100 screened; 1100 \u2212 870 = 230 assessed; 230 \u2212 195 = 35 included) \u2014 the engine warns if they don\'t.\n\n## Standard reference\n\nPage MJ, McKenzie JE, Bossuyt PM, et al. *The PRISMA 2020 statement: an updated guideline for reporting systematic reviews.* BMJ 2021;372:n71. Template: [prisma-statement.org/prisma-2020-flow-diagram](https://www.prisma-statement.org/prisma-2020-flow-diagram).'
   },
+  {
+    "slug": "rbd-data-center-tier-iii",
+    "diagram": "rbd",
+    "title": "Data-center availability (Tier III power, cooling, network, storage)",
+    "description": "A four-stage reliability block diagram for a Tier III data center \u2014 dual-source power (utility in parallel with a generator-plus-ATS chain), N+1 (2-of-3) CRAC cooling, dual core switches, and mirrored storage. The engine reduces the whole nested structure to one availability figure.",
+    "standard": "IEC 61078 / Uptime Institute Tier III",
+    "tags": [
+      "rbd",
+      "reliability",
+      "availability",
+      "data-center",
+      "redundancy",
+      "n-plus-1",
+      "k-of-n",
+      "series-parallel"
+    ],
+    "complexity": 4,
+    "featured": true,
+    "dsl": 'rbd "Data Center Tier III Availability"\n  series {\n    parallel {\n      block UTIL "Utility feed" R=0.999\n      series {\n        block GEN "Diesel generator" R=0.98\n        block ATS "Transfer switch" R=0.995\n      }\n    }\n    kofn 2/3 {\n      block CRAC1 "CRAC unit 1" R=0.97\n      block CRAC2 "CRAC unit 2" R=0.97\n      block CRAC3 "CRAC unit 3" R=0.97\n    }\n    parallel {\n      block SW1 "Core switch A" R=0.995\n      block SW2 "Core switch B" R=0.995\n    }\n    parallel {\n      block ST1 "Storage node A" R=0.99\n      block ST2 "Storage node B" R=0.99\n    }\n  }',
+    "notes": "## What this shows\n\nA realistic Tier III topology where the whole facility is a **series** of four subsystems, each internally redundant. The **power** stage is the interesting one: the utility feed runs in **parallel** with a backup *chain* \u2014 a generator that only helps if its transfer switch also works (a nested `series`). Cooling is **N+1** (`2-of-3` CRAC units), and both the network and storage tiers are mirrored pairs.\n\n**The engine reduces the nesting to one number.** It rolls the generator chain (`0.98 \xB7 0.995`) into the power parallel, evaluates the 2-of-3 cooling exactly, and multiplies the four series stages to a **facility availability of \u2248 0.9972**. No single point of failure survives \u2014 every stage has redundancy \u2014 and the Birnbaum importance ranks which subsystem to harden first. This is the kind of nested success logic a generic diagram tool draws but never computes."
+  },
+  {
+    "slug": "rbd-dual-channel-safety",
+    "diagram": "rbd",
+    "title": "Dual-channel safety system (redundant chains)",
+    "description": "A reliability block diagram of a 1-out-of-2 safety instrumented function \u2014 two independent sensor\u2192logic\u2192actuator channels in parallel, each a series chain. Shows how a parallel of series strings removes every single point of failure.",
+    "standard": "IEC 61078",
+    "tags": [
+      "rbd",
+      "reliability",
+      "safety",
+      "redundancy",
+      "1oo2",
+      "series-parallel"
+    ],
+    "complexity": 2,
+    "featured": false,
+    "dsl": 'rbd "Dual-channel trip (1oo2)"\n  parallel {\n    series {\n      block S1 "Sensor A" R=0.97\n      block L1 "Logic A" R=0.995\n      block V1 "Valve A" R=0.98\n    }\n    series {\n      block S2 "Sensor B" R=0.97\n      block L2 "Logic B" R=0.995\n      block V2 "Valve B" R=0.98\n    }\n  }',
+    "notes": "## What this shows\n\nA **1-out-of-2 (1oo2)** safety architecture: two complete sensor\u2192logic\u2192valve channels run in parallel, so the trip still fires if either channel works end-to-end. Each channel is itself a **series** chain \u2014 a channel needs all three of its elements.\n\n**Redundancy removes the single points of failure.** Each channel alone has reliability `0.97\xB70.995\xB70.98 \u2248 0.946`; in parallel the system reaches `1 \u2212 (1\u22120.946)\xB2 \u2248 0.997`. Because no single block's failure drops the system to zero, the engine reports **no single point of failure** \u2014 the structural goal of a redundant safety function, proven by computation rather than asserted."
+  },
+  {
+    "slug": "rbd-flight-control",
+    "diagram": "rbd",
+    "title": "Fly-by-wire flight control (triple-redundant)",
+    "description": "A reliability block diagram of a fly-by-wire flight-control system \u2014 2-of-3 voting flight-control computers, triple-redundant hydraulics, and dual electrical buses, all in series. The engine computes the six-nines-class system reliability the architecture is designed to hit.",
+    "standard": "IEC 61078 / ARP4761",
+    "tags": [
+      "rbd",
+      "reliability",
+      "aerospace",
+      "fly-by-wire",
+      "redundancy",
+      "k-of-n",
+      "2oo3",
+      "triple-redundant"
+    ],
+    "complexity": 3,
+    "featured": false,
+    "dsl": 'rbd "Fly-by-wire Flight Control"\n  series {\n    kofn 2/3 {\n      block FCC1 "Flight computer 1" R=0.9995\n      block FCC2 "Flight computer 2" R=0.9995\n      block FCC3 "Flight computer 3" R=0.9995\n    }\n    parallel {\n      block HYDG "Hydraulics green" R=0.998\n      block HYDB "Hydraulics blue" R=0.998\n      block HYDY "Hydraulics yellow" R=0.998\n    }\n    parallel {\n      block AC1 "AC bus 1" R=0.999\n      block AC2 "AC bus 2" R=0.999\n    }\n  }',
+    "notes": `## What this shows
+
+A textbook fly-by-wire architecture, the kind certified under ARP4761: **2-out-of-3** voting flight-control computers (a single computer can fail or disagree without losing control), **three independent hydraulic systems** (the green/blue/yellow split of a modern airliner), and **dual electrical buses** \u2014 all in **series** because the aircraft needs computing, hydraulics, and power simultaneously.
+
+**The architecture's whole point is a number, and the engine computes it.** Each subsystem is driven so close to 1 that the product still lands at a system reliability of **\u2248 0.999998** \u2014 and Schematex prints the nines rather than rounding to "1", because in this domain the nines *are* the answer. No single point of failure remains, which is exactly the design intent the diagram now proves rather than merely asserts.`
+  },
+  {
+    "slug": "rbd-redundant-server",
+    "diagram": "rbd",
+    "title": "Redundant server reliability (series + parallel + k-of-n)",
+    "description": "A computed reliability block diagram for a server \u2014 a single power supply in series with a redundant fan pair and a 2-of-3 disk array. The engine reduces the success logic to one system-reliability figure and flags the power supply as the single point of failure.",
+    "standard": "IEC 61078",
+    "tags": [
+      "rbd",
+      "reliability",
+      "redundancy",
+      "series-parallel",
+      "k-of-n",
+      "spof",
+      "availability"
+    ],
+    "complexity": 2,
+    "featured": true,
+    "dsl": 'rbd "Redundant Server"\n  series {\n    block PSU "Power Supply" R=0.99\n    parallel {\n      block FAN1 "Fan A" R=0.95\n      block FAN2 "Fan B" R=0.95\n    }\n    kofn 2/3 {\n      block D1 "Disk 1" R=0.97\n      block D2 "Disk 2" R=0.97\n      block D3 "Disk 3" R=0.97\n    }\n  }',
+    "notes": "## What this shows\n\nThe three building blocks of reliability success logic in one diagram. The **single power supply** sits in series \u2014 everything depends on it. The **two fans** are in parallel, so the cooling subsystem survives either one failing. The **three disks** form a **2-of-3** array that tolerates one loss.\n\n**The number is computed, not drawn.** The engine reduces each group \u2014 fans to `1 \u2212 0.05\xB2 = 0.9975`, the disk array to `3\xB70.97\xB2\xB70.03 + 0.97\xB3 = 0.99735`, then multiplies the series chain \u2014 to a **system reliability of \u2248 0.9849**. It also derives each block's Birnbaum importance and flags the **power supply as the single point of failure** (red border): with no redundancy in series, its failure alone takes down the whole system, and it carries the highest importance \u2014 the first place to add redundancy."
+  },
+  {
+    "slug": "rbd-sif-emergency-shutdown",
+    "diagram": "rbd",
+    "title": "Safety instrumented function (SIF) \u2014 emergency shutdown",
+    "description": "A reliability block diagram of an IEC 61511 emergency-shutdown loop \u2014 2-of-3 voting pressure transmitters, a redundant logic solver, and 1-out-of-2 shutdown valves. The classic sensor \u2192 logic \u2192 final-element SIF architecture, with the engine computing the loop reliability.",
+    "standard": "IEC 61078 / IEC 61511 (SIF)",
+    "tags": [
+      "rbd",
+      "reliability",
+      "safety",
+      "sif",
+      "sil",
+      "iec-61511",
+      "k-of-n",
+      "2oo3",
+      "1oo2",
+      "redundancy"
+    ],
+    "complexity": 3,
+    "featured": false,
+    "dsl": 'rbd "Emergency Shutdown SIF (SIL 2)"\n  series {\n    kofn 2/3 {\n      block PT1 "Pressure Tx 1" R=0.98\n      block PT2 "Pressure Tx 2" R=0.98\n      block PT3 "Pressure Tx 3" R=0.98\n    }\n    parallel {\n      block LS1 "Logic solver A" R=0.999\n      block LS2 "Logic solver B" R=0.999\n    }\n    parallel {\n      block SDV1 "Shutdown valve A" R=0.96\n      block SDV2 "Shutdown valve B" R=0.96\n    }\n  }',
+    "notes": "## What this shows\n\nThe canonical safety-instrumented-function architecture from IEC 61511, laid out as a **series** of three subsystems: **sensing**, **logic**, and **final elements**. Sensing uses **2-out-of-3** voting transmitters (tolerates one failure *and* rejects one spurious trip); the **logic solver** is a redundant pair; the **final elements** are two shutdown valves in a **1-out-of-2** (parallel) arrangement so either can close the line.\n\n**The reliability is computed across the loop.** The engine evaluates the 2oo3 sensor group exactly, the two parallel pairs as `1 \u2212 (1\u2212R)\xB2`, and the series chain \u2014 giving a loop reliability of **\u2248 0.9972**. Because every subsystem is redundant, there's **no single point of failure**, and the importance ranking points at the valves (the lowest-reliability stage) as the place a SIL upgrade buys the most. The success-space companion to the fault tree a safety case also needs."
+  },
   {
     "slug": "sequence-combined-fragments-gallery",
     "diagram": "sequence",
@@ -4093,6 +4518,14 @@ var SYNTAX = {
   "floorplan": {
     "title": "Floor plan",
     "content": '## 1. Your first floor plan\n\nA header, one room, a door, and a window:\n\n```\nfloorplan "Studio"\nroom main "Studio" at 0,0 size 4x3\ndoor main south at 20%\nwindow main north at 50%\n```\n\nThree rules cover most usage:\n\n1. Start with `floorplan`, an optional quoted title, and `unit m` (default) or `unit ft`. **All numbers are in this unit.**\n2. Rooms are rectangles: `room id "Label" at x,y size WxH`. The label and computed area render centered in the room.\n3. Openings hang on walls: a wall reference (`main south`) positions along that wall at a percentage; `between A B` finds the shared wall automatically.\n\n---\n\n## 2. Rooms and placement\n\nPlace the first room at `0,0` and chain the rest relatively \u2014 adjacent rooms share an edge exactly, and their walls merge into a single band:\n\n```\nroom living  "Living Room" at 0,0 size 5.2x4.2\nroom kitchen "Kitchen"     right-of living size 3.0x4.2\nroom hall    "Hallway"     below living size 2.0x2.6\nroom bed1    "Bedroom 1"   right-of hall size 3.2x2.6\n```\n\n- `right-of` / `left-of` / `above` / `below` snap to the reference room\'s edge.\n- `align start|center|end` aligns the cross axis (default `start` = top/left edges flush); `offset n` shifts it.\n- `fill #e0f2fe` tints the floor; `nolabel` suppresses the name + area label (single-space plans like classrooms).\n- Coordinates are y-down: `at 0,0` is the top-left corner.\n\n**L/T/U-shaped rooms** use `extend` \u2014 declare the main rectangle, then grow it with edge-sharing rectangles. The walls merge along the seam, the area is summed into one number (exactly how professionals measure L-rooms), and the label centers on the largest part:\n\n```\nroom living "Living Room" at 0,0 size 5x4\nextend living at 5,2 size 2x2          # L-shape: notch at top-right\n```\n\nAn extension that doesn\'t touch the room, or overlaps it, is rejected with a quantified error. `north` (optionally `north 30` for rotated plans) adds the compass at the top right.\n\n---\n\n## 3. Doors, windows, openings\n\n```\ndoor hall west at 50% width 1.0 swing in          # exterior door on a wall\ndoor between hall bed1 at 50% hinge right          # interior door on the shared wall\ndoor between bed1 bath at 30% type sliding         # sliding door \u2014 no arc\nopening between living kitchen at 35% width 1.2    # archway, no leaf\nwindow living north at 30% width 1.8\n```\n\n- `between A B` resolves the shared wall segment and positions at the percentage **along the overlap** \u2014 no coordinates needed. Non-adjacent rooms are rejected with the measured gap.\n- Doors default to 0.9 m wide on exterior walls, 0.8 m on `between` walls; windows default to 1.2 m.\n- `hinge left|right` picks the jamb; `swing in|out` flips the quarter-arc (default swings into the owning room \u2014 the first room named).\n- Door `type single|double|sliding|pocket|bifold`: double draws two mirrored arcs; sliding/pocket draw offset leaf lines without an arc; bifold draws the two closet-door tent peaks.\n- Window `type fixed|sliding|casement|bay`: sliding = two offset panels, casement adds the outward swing arc, bay projects a splayed trapezoid outside the wall.\n- Openings clamp to fit their wall segment (with a warning) rather than overflowing.\n\n---\n\n## 4. Furniture\n\nFurniture is placed **relative to its room\'s interior top-left corner**, with optional `size`, `rotate`, and a label:\n\n```\nfurniture sofa in living at 0.25,2.9\nfurniture desk "Teacher" in class at 2,1.5 size 5x2.5 rotate 20\nfurniture counter "Cubbies" in class at 6,24.4 size 10x1.2\n```\n\nThe catalog spans residential, commercial, and site work (sizes default to industry-standard footprints):\n\n| Cluster | Types |\n| --- | --- |\n| Residential | `bed-double` `bed-single` `bed-queen` `bed-king` `bunk-bed` `crib` `sofa` `loveseat` `sectional` `armchair` `ottoman` `coffee-table` `side-table` `tv` `tv-stand` `fireplace` `floor-lamp` `rug` `wardrobe` `dresser` `nightstand` `bookshelf` `plant` `piano` `piano-upright` `pool-table` `ceiling-fan` `dining-table` |\n| Kitchen / bath | `counter` `wall-cabinet` `kitchen-sink` `stove` `range-hood` `fridge` `dishwasher` `island` `bar-stool` `toilet` `sink` `vanity` `bidet` `urinal` `bathtub` `shower` `washer` `dryer` |\n| Classroom / office | `desk-chair` `desk` `desk-l` `chair` `whiteboard` `smartboard` `bookcase` `cubbies` `filing-cabinet` `lockers` `kidney-table` `round-table-4/6/8/10` `conference-table` |\n| Event / banquet | `banquet-table` `head-table` `stage` `dance-floor` `bar` `dj-booth` `cocktail-table` `podium` `row-chairs` |\n| Retail / warehouse | `shelving` `checkout` `clothing-rack` `fitting-room` `pallet-rack` `loading-dock` `forklift` |\n| Salon / gym | `salon-chair` `shampoo-bowl` `manicure-table` `treadmill` `weight-bench` `power-rack` `yoga-mat` |\n| Stairs / structural | `stairs` `stairs-l` `stairs-u` `spiral-stairs` `elevator` `column` |\n| Site / outdoor | `tree` `car` |\n\n**Auto-seating** is built in: `round-table-8` draws 8 chairs on its circumference (60\u2033 top; `round-table-10` uses 72\u2033), `dining-table` / `banquet-table` / `conference-table` seat both long edges at one chair per 0.65 m, `head-table` seats one side facing the room, `manicure-table` seats a client and technician chair, and `row-chairs` places a theater strip at 0.55 m pitch. `rug`, `dance-floor`, `yoga-mat`, `counter`, `island`, `wall-cabinet`, `range-hood`, and `ceiling-fan` are underlays/overheads \u2014 other furniture can overlap them without a collision warning.\n\n`tree` and `car` are sized for the outdoors (canopy disc, parking-stall footprint), so a **site plan** is just zones tiled as adjacent rooms \u2014 front yard, house footprint, driveway, back yard \u2014 with trees and parked cars placed on top.\n\n**Stairs** follow the drafting conventions: tread lines at 0.28 m (11\u2033), a direction arrow starting at the lowest tread labeled `UP` (give the item a `"DN"` label for a descending run), and the 45\xB0 zigzag break line at the imaginary 4-ft cut plane, with dashed treads beyond. `stairs` is a straight run (orient with `size`/`rotate`), `stairs-l` turns 90\xB0 over a landing, `stairs-u` switches back 180\xB0, `spiral-stairs` is a circle with radial treads and a center pole.\n\n---\n\n## 5. Arrays \u2014 grid, row, arc\n\nRepeated furniture is one statement, not thirty:\n\n```\ngrid desk-chair in class rows 5 cols 6 count 27 area 5,8 25,24 itemsize 2x2.5\nrow round-table-8 in hall cols 3 area 8.8,13.4 15.2,13.4 itemsize 2.3x2.3\narc chair in hall count 13 center 12,8 radius 5 from 200 to 340\n```\n\n- `area x1,y1 x2,y2` gives the first and last item **centers**; items spread evenly between them.\n- `count` truncates **row-major** \u2014 27 desks in a 5\xD76 grid drops the last row\'s tail, exactly like a real classroom.\n- `arc` places items on a circular arc facing the center \u2014 semicircle classrooms, ceremony seating.\n\n---\n\n## 6. Units, areas, dimension lines\n\n- `unit ft` makes every number feet; dimension lines format as `32\'` / `15\'1"` and areas as `sq ft`. Internally everything is metric (1 ft = 0.3048 m).\n- Room areas are **computed by the engine** from the declared geometry, never typed by hand.\n- Dimension lines render outside the plan with architectural slash ticks: overall width + height always, plus per-room segments along the top and left exteriors.\n\n---\n\n## 7. Validation\n\nThe engine validates what LLMs (and humans) actually get wrong, with errors that name the offending elements and a fix direction:\n\n**Errors** (block rendering, shown in an error panel):\n\n- Room overlap \u2014 `rooms "bed1" and "bath" overlap by 0.40\xD72.60 m \u2014 move "bath" right-of "bed1" or shrink size`\n- Door between non-adjacent rooms \u2014 `door between "kitchen" and "bed2": rooms share no wall (gap 2 m on x-axis)`\n- Furniture outside its room \u2014 `furniture sofa #1 extends 1.7 m outside room "c" \u2014 move it or shrink size`\n\n**Warnings** (render anyway, listed under the plan):\n\n- Furniture collision \u2014 bounding boxes including **chair-ring envelopes**, so two banquet rounds whose chairs touch get flagged even when the table tops don\'t.\n- Opening clamped to fit its wall segment.\n\n---\n\n## 8. Grammar (EBNF)\n\n```text\nplan      ::= "floorplan" string? ("unit" ("m"|"ft"))? NL statement*\nstatement ::= room | extend | north | door | window | opening | furniture | array\nroom      ::= "room" id string? placement "size" dims ("fill" color)? ("nolabel")?\nextend    ::= "extend" id placement "size" dims\nnorth     ::= "north" num?\nplacement ::= "at" coord\n            | ("right-of"|"left-of"|"above"|"below") id ("offset" num)?\n              ("align" ("start"|"center"|"end"))?\ndoor      ::= "door" (wallref | "between" id id) "at" pct\n              ("width" num)? ("hinge" ("left"|"right"))? ("swing" ("in"|"out"))?\n              ("type" ("single"|"double"|"sliding"|"pocket"|"bifold"))?\nwindow    ::= "window" wallref "at" pct ("width" num)?\n              ("type" ("fixed"|"sliding"|"casement"|"bay"))?\nopening   ::= "opening" (wallref | "between" id id) "at" pct ("width" num)?\nfurniture ::= "furniture" type ("in" id) "at" coord ("size" dims)? ("rotate" num)? string?\narray     ::= ("grid"|"row"|"arc") type "in" id\n              ("rows" int)? ("cols" int)? ("count" int)?\n              ("area" coord coord)? ("itemsize" dims)? ("rotate" num)?\n              ("center" coord)? ("radius" num)? ("from" num "to" num)?\nwallref   ::= id ("north"|"south"|"east"|"west")\ncoord     ::= num "," num          dims ::= num "x" num          pct ::= num "%"?\n```\n\nComments run from `#` to end of line. CJK quotes (`\u201C\u201D`) are accepted as ASCII quotes.\n\n---\n\n## Related examples\n\n- [Two-bedroom apartment](/examples#floorplan) \u2014 relative placement, 7 doors, full furnishing\n- [27-desk classroom](/examples#floorplan) \u2014 `grid \u2026 count` truncation, `unit ft`\n- [Wedding reception for 120](/examples#floorplan) \u2014 auto-seated banquet rounds, dance floor'
+  },
+  "playbook": {
+    "title": "Sports playbook",
+    "content": '## 1. Your first play\n\nEvery diagram starts with a header naming the **sport**, then a **formation** (which places the players), then **assignments**:\n\n```\nplaybook "Give & Go" sport basketball\nset 5-out\npass 1 2\ncut 1 rim\npass 2 1\n```\n\n`pass 1 2` draws a pass from player 1 to player 2; `cut 1 rim` sends player 1 to the rim. Basketball draws passes **dashed** and cuts **solid** \u2014 the convention on every coaching whiteboard.\n\n---\n\n## 2. The three sports\n\nPick the sport in the header (`sport football|basketball|soccer`). Each uses its real unit and the conventional coaching viewpoint:\n\n| Sport | Unit | View | Surface |\n|---|---|---|---|\n| `football` | yards | offense at the bottom attacking **up**; downfield = up | green field with yard lines, hashes, end zone |\n| `basketball` | feet | NBA **half-court**; baseline + hoop at the top | light maple hardwood |\n| `soccer` | metres | full **105 \xD7 68 m** pitch (attack toward the right); or `view half` | green pitch with IFAB markings |\n\n---\n\n## 3. Players & formations\n\nThe fastest way to place players is a **formation** (football/soccer) or **set** (basketball):\n\n- **Football** \u2014 `formation i-form | shotgun | singleback | pistol | spread | trips | empty | goal-line | wishbone` with optional strength `left`/`right`. Receivers are `X Z H Y` (Y = tight end), backs `QB RB FB`, line `LT LG C RG RT`.\n- **Basketball** \u2014 `set horns | 1-4-high | 1-4-low | box | spread-pnr | 4-out | 5-out`. Players are numbered `1`\u2013`5`.\n- **Soccer** \u2014 `formation 4-3-3 | 4-4-2 | 4-2-3-1 | 4-5-1 | 4-4-1-1 | 3-5-2 | 3-4-3`. Players are numbered `1` (GK) \u2026 `11`.\n\nFor set-pieces or free-form diagrams, place players individually and crop to a half:\n\n```\nplaybook "Overlap & Cross" sport soccer\nview half\nplayer 7 o at 75,12 label 7\nplayer 2 o at 60,15 label 2\nplayer 9 o at 88,30 label 9\nplayer 11 o at 85,52 label 11\nplayer 10 o at 80,38 label 10\ndribble 7 to 82,20\nrun 2 to 90,8\npass 7 to 90,8\npass 2 to 102,34\nrun 9 to 101,31\nrun 11 to 101,40\n```\n\n---\n\n## 4. Movement verbs & line styles\n\nThe same line style means different things in different sports \u2014 Schematex draws each sport\'s own convention, and the legend always matches:\n\n| Verb | Football | Basketball | Soccer |\n|---|---|---|---|\n| `pass` | dashed (throw) | **dashed** | **solid** |\n| `run` / `cut` | solid | **solid** (cut) | **dashed** (run) |\n| `dribble` | \u2014 | wavy | wavy |\n| `screen` / `block` | T-bar \u22A5 | T-bar \u22A5 (screen) | T-bar \u22A5 |\n| `shot` | \u2014 | solid | double line |\n\n**Note the inversion:** basketball draws a pass *dashed* and a cut *solid*; soccer draws a pass *solid* and a run *dashed*. That is how the two coaching communities actually diagram \u2014 Schematex honours each.\n\nMove targets can be a **player id**, a **landmark** name, or explicit **coordinates** (`to x,y`).\n\n---\n\n## 5. Football \u2014 routes, runs, defense\n\nPass routes use the **route tree**: `go fly streak slant flat hitch out in dig curl comeback corner post wheel cross drag seam`. Run concepts: `dive iso power counter sweep toss draw trap`. Blocking uses `block`, `pull`, and `handoff`. Set `goal N` to draw the end zone and goalposts:\n\n```\nplaybook "Red Zone \u2014 Play-Action Fade" sport football\nfield down 1 distance 5 los 5 goal 5 hash nfl\nformation i-form right\ndefense cover-1\nhandoff QB RB\nroute Z corner 4\nroute X slant\nroute Y out 3\nrun RB dive right\n```\n\n`defense cover-0/1/2/3/4/6` draws the coverage shell; `defense 4-3 | 3-4 | nickel | dime` sets the front. `hash nfl|college|none` controls the hash marks.\n\n---\n\n## 6. Basketball \u2014 sets, landmarks, screens\n\nCuts and passes target **named landmarks** \u2014 `rim elbow wing corner short-corner block slot top high-post dunker` (prefix `l`/`r` for left/right). `screen A B` draws a ball-screen (T-bar) for player B; `dribble` is a wavy line:\n\n```\nplaybook "Spread Pick & Roll" sport basketball\nset spread-pnr\nscreen 5 1\ndribble 1 to 11,17\ncut 5 rim\npass 1 2\n```\n\n`defense man` matches each defender to a man; `defense zone-2-3 | zone-3-2 | zone-1-3-1` draws a zone front.\n\n---\n\n## 7. Soccer \u2014 shapes, runs, build-up\n\nA formation alone draws the team shape. Add `pass` (solid), `run` (dashed), and `dribble` (wavy) to show a phase of play:\n\n```\nplaybook "Build-Up From the Back" sport soccer\nformation 4-3-3\npass 1 4\npass 4 2\nrun 2 to 40,10\npass 4 6\nrun 6 to 62,24\n```\n\nLandmarks include `box top-box d penalty-spot near-post far-post six-yard center`. `defense low-block | mid-block | high-press` overlays the opponent\'s shape. Soccer renders daylight-only \u2014 `theme: dark` falls back to the default pitch.\n\n---\n\n## 8. Validation\n\nThe engine rejects the mistakes models actually make and lists the valid options:\n\n- unknown `sport`, `formation` / `set`, `defense`, or named route;\n- a move referencing an undeclared player id;\n- a malformed coordinate or a missing `to` target.\n\nSofter issues (e.g. a zero-length move) render with a warning rather than failing.\n\n---\n\n## 9. Grammar (EBNF)\n\n```text\nplaybook   = "playbook" string "sport" sport NL { stmt NL } ;\nsport      = "football" | "basketball" | "soccer" ;\nstmt       = field | formation | defense | player | move | zone | "view" view ;\nfield      = "field" { "down" num | "distance" num | "los" num\n                     | "goal" num | "hash" hash | "view" view } ;\nformation  = ( "formation" | "set" ) name [ "left" | "right" ] ;\ndefense    = "defense" scheme ;\nplayer     = "player" id pos "at" coord "label" text ;\nmove       = route | run | pass | cut | dribble | screen\n           | shot | motion | handoff | pull | block ;\nroute      = "route" id namedRoute [ num ] [ "left" | "right" ] ;\nrun        = "run" id ( concept [ "left" | "right" ] | "to" coord ) ;\npass       = "pass" id ( id | landmark | "to" coord ) ;\ncut        = "cut" id ( landmark | "to" coord ) ;\ndribble    = "dribble" id "to" coord ;\nscreen     = "screen" id id ;\nshot       = "shot" id [ "to" coord ] ;\nzone       = "zone" coord coord string ;\ncoord      = num "," num ;\nview       = "full" | "half" ;\nhash       = "nfl" | "college" | "none" ;\n```\n\n---\n\n## Related examples\n\nFive canonical plays per sport ship as examples \u2014 Four Verticals, Mesh, Smash, Power O, and a Red-Zone fade for football; Pick & Roll, Horns, Give & Go, Floppy, and a Backdoor cut for basketball; 4-3-3 shape, Build-Up, Overlap, High Press, and Counter-Attack for soccer.'
+  },
+  "rbd": {
+    "title": "Reliability Block Diagram",
+    "content": '## 1. Your first diagram\n\nEvery document starts with the `rbd` keyword (alias `reliability`), an optional title, then nested success-logic groups around `block` leaves:\n\n```\nrbd "Two redundant pumps"\n  parallel {\n    block A "Pump A" R=0.9\n    block B "Pump B" R=0.9\n  }\n```\n\nThe engine draws the two pumps on parallel rails between a split node and a join node, computes the system reliability `1 \u2212 (1\u22120.9)(1\u22120.9) = 0.99`, and prints it as the headline. A bare top-level list of blocks (no outer group) is treated as a **series** chain.\n\n## 2. Blocks\n\nA `block` is one component on a success path:\n\n```\nblock ID "Label" R=0.99\n```\n\n- `ID` \u2014 a short identifier (shown when no label is given).\n- `"Label"` \u2014 an optional display name (CJK quotes welcome).\n- Reliability is given as **`R=0.99`** (reliability/availability), **`p=0.01`** (probability of *failure*, \u2192 R = 1\u2212p), or a percentage **`R=99%`**. A block with no reliability leaves the system figure symbolic (`n/a`).\n\n## 3. Success-logic groups\n\nGroups nest freely, so you can model redundant chains, voting banks, and standby pairs:\n\n| Group | Succeeds when | Reliability |\n|-------|---------------|-------------|\n| `series { \u2026 }` | **every** child works | \u220F R\u1D62 |\n| `parallel { \u2026 }` | **any** child works | 1 \u2212 \u220F(1 \u2212 R\u1D62) |\n| `kofn k/n { \u2026 }` | **\u2265 k of n** children work | exact state enumeration |\n\n```\nseries {\n  block CTRL "Controller" R=0.995\n  parallel {\n    series { block P1 "Path 1 sensor" R=0.97\n             block A1 "Path 1 actuator" R=0.98 }\n    series { block P2 "Path 2 sensor" R=0.97\n             block A2 "Path 2 actuator" R=0.98 }\n  }\n}\n```\n\n## 4. Computed reliability, importance & SPOF\n\nAfter parsing, the engine computes:\n\n- **System reliability** \u2014 the headline figure, by recursive series/parallel/k-of-n reduction.\n- **Birnbaum importance** `I\u1D2E(i) = R_sys(R\u1D62=1) \u2212 R_sys(R\u1D62=0)` for every block; the highest-importance block (the improvement target) is accented.\n- **Single points of failure** \u2014 any block where `R_sys(R\u1D62=0) = 0` (its failure alone fails the system) is drawn with a red border. A non-redundant block in series is always a SPOF.\n\n## 5. Validation\n\nThe parser reports non-fatal warnings rather than failing:\n\n- a `kofn k/n` threshold with `k > n` is clamped to `n` (and `k < 1` to `1`);\n- a reliability outside `0..1` is clamped;\n- a duplicate block id is flagged.\n\n## 6. Theming\n\n`theme: default` uses the shared risk-reliability palette (neutral blocks, blue reliability numerals, red single-point-of-failure borders). `theme: monochrome` renders a black-and-white print version (SPOF by border weight); `theme: dark` is the Catppuccin dark variant.'
   }
 };
 
@@ -5352,6 +5785,44 @@ var PROFILES = {
       "'has no effect/cause' -> every failure mode needs at least one effect and one cause."
     ]
   },
+  rbd: {
+    type: "rbd",
+    header: 'rbd "Title"',
+    mode: "brace-nested success logic: series/parallel/kofn groups wrapping `block` leaves",
+    keywords: 'header: rbd | reliability \xB7 groups: series { \u2026 } | parallel { \u2026 } | kofn k/n { \u2026 } (nestable) \xB7 leaf: block ID "Label" R=0.99 (also p=0.01 failure prob, or R=99%) \xB7 engine computes system reliability + Birnbaum importance + SPOF',
+    forms: [
+      'rbd "Redundant Server"',
+      "series {",
+      '  block PSU "Power Supply" R=0.99',
+      "  parallel {",
+      '    block FAN1 "Fan A" R=0.95',
+      '    block FAN2 "Fan B" R=0.95',
+      "  }",
+      "  kofn 2/3 {",
+      '    block D1 "Disk 1" R=0.97',
+      '    block D2 "Disk 2" R=0.97',
+      '    block D3 "Disk 3" R=0.97',
+      "  }",
+      "}"
+    ],
+    prefer: [
+      "Single-word keyword is `rbd` (alias `reliability`). Nest `series`/`parallel`/`kofn k/n` groups with braces around `block` leaves.",
+      "Give every block a reliability: `R=0.99` (or failure prob `p=0.01`, or `R=99%`); the engine then computes system reliability.",
+      "Use `parallel { \u2026 }` for full redundancy and `kofn 2/3 { \u2026 }` for k-out-of-n voting redundancy.",
+      "Groups nest freely \u2014 e.g. a `parallel` of two `series` strings models redundant chains.",
+      "A bare top-level list of blocks (no outer group) is treated as a series chain."
+    ],
+    avoid: [
+      "Don't omit the `block` keyword's reliability if you want a number \u2014 a block with no R leaves the system reliability symbolic.",
+      "Don't forget to close every `{` with a `}` \u2014 groups are brace-delimited, not indentation-driven.",
+      "Don't write `kofn` without a `k/n` threshold (e.g. `kofn 2/3 { \u2026 }`)."
+    ],
+    repair: [
+      "'needs a k/n threshold' -> write `kofn 2/3 { \u2026 }` with the threshold before the brace.",
+      "'Unclosed group' -> add the missing `}`.",
+      "If system reliability shows 'n/a', a block is missing its `R=`/`p=`."
+    ]
+  },
   causalloop: {
     type: "causalloop",
     header: 'causalloop "Title"',
@@ -5626,6 +6097,37 @@ var PROFILES = {
       "'extends \u2026 outside room' -> reduce the furniture x,y or size; coordinates start at the room's top-left interior corner.",
       "'overlaps \u2026 by \u2026 m' (warning) -> spread the grid `area` corners or reduce rows/cols; remember chair rings extend ~0.45 m beyond a table edge."
     ]
+  },
+  playbook: {
+    type: "playbook",
+    header: 'playbook "Play Name" [sport football]',
+    mode: "formation preset + named routes off the route tree; coordinates in yards (x lateral from ball, y depth off LOS)",
+    keywords: 'field down N distance M los YARD hash nfl|college|none \xB7 formation i-form|shotgun|singleback|pistol|trips-right|trips-left|spread|empty|pistol|goal-line|wishbone [left|right] \xB7 defense 4-3|3-4|nickel|dime|cover-0|cover-1|cover-2|cover-3|cover-4|cover-6 \xB7 player id pos[o|c|ol|qb|rb|wr|te|x|dl|lb|db|s] [label "L"] [at x,y] \xB7 route PLAYER NAMED [depth] [left|right] \xB7 run PLAYER CONCEPT [left|right] \xB7 block BLOCKER TARGET \xB7 pull LINEMAN left|right \xB7 handoff QB BACK \xB7 motion PLAYER left|right [yards] \xB7 zone at x,y size rxXry "label" \xB7 route tree: go/fly/streak slant flat hitch out in/dig curl comeback corner/flag post wheel cross/drag seam screen \xB7 run concepts: dive iso power counter sweep toss draw trap \xB7 players from a formation use ids QB RB FB C LG RG LT RT Y(TE) X Z H',
+    forms: [
+      'playbook "Slant-Flat" sport football',
+      "field down 1 distance 10 los 35 hash nfl",
+      "formation trips-right",
+      "defense cover-2",
+      "route Z slant",
+      "route H flat",
+      "route X slant",
+      "run RB dive right"
+    ],
+    prefer: [
+      "Start from a `formation` preset \u2014 it places all 11 offensive players with standard ids (QB RB FB C LG RG LT RT, TE=Y, receivers X/Z/H). Then assign routes by id.",
+      "Use named routes from the tree (`route Z post`, `route H out 12`) \u2014 the optional number is the stem depth in yards off the LOS; an explicit `left`/`right` overrides the natural break side.",
+      "Use `run RB power right` for the ball carrier, `pull LG right` for a pulling lineman, `block FB DE_S` for a key block (T-bar drawn on the target), `handoff QB RB` for the mesh.",
+      "Add `defense cover-2` (or 4-3 / cover-3 \u2026) to drop in 11 defenders + coverage zone bubbles automatically.",
+      "Use `field down 1 distance 10 los 35` for the down-and-distance banner; `hash nfl|college` sets the hash-mark width."
+    ],
+    avoid: [
+      "Don't hand-place all 22 players with `at` unless you need a non-standard look \u2014 the formation/defense presets are far less error-prone.",
+      "Don't invent route names \u2014 stick to the tree (go/slant/out/in/curl/comeback/corner/post/flat/hitch/wheel/cross/seam/screen) and run concepts (dive/power/counter/sweep/toss/draw/iso/trap)."
+    ],
+    repair: [
+      "'route on unknown player \u2026' (warning) -> the player id isn't in the formation; check the roster ids (QB RB FB C LG RG LT RT Y X Z H) or add a `player` statement.",
+      "'block \u2026 on unknown target \u2026' (warning) -> the block target must be a declared defender id (e.g. DE_S, MLB) \u2014 add `defense \u2026` so the defenders exist."
+    ]
   }
 };
 function getGenerationProfile(type) {
@@ -5790,5 +6292,5 @@ function matchRepair(repairs, message) {
 }
 
 export { DIAGRAM_REGISTRY, DIAGRAM_SINCE, getAllDiagramTypes, getDiagramMeta, getDiagramSince, getExamples, getSyntax, listDiagrams, renderDsl, resolveDiagramType, validateDsl };
-//# sourceMappingURL=chunk-JCJWSW5Y.js.map
-//# sourceMappingURL=chunk-JCJWSW5Y.js.map
+//# sourceMappingURL=chunk-N524SY5D.js.map
+//# sourceMappingURL=chunk-N524SY5D.js.map