@diagrammo/dgmo 0.48.2 → 0.50.0

package/docs/ai-integration.md

@@ -61,7 +61,7 @@ To teach Claude about DGMO in a specific project without the global skill, paste
 <!-- DGMO-AI-CORE:START -->
 ## DGMO AI Core
 
-_Generated from `language-reference.md` — the anti-patterns and 43-type index below are identical across every DGMO AI surface._
+_Generated from `language-reference.md` — the anti-patterns and 50-type index below are identical across every DGMO AI surface._
 
 ### Disambiguation — where DGMO diverges from LLM priors
 
@@ -115,7 +115,7 @@ Valid markup is the floor, not the goal. A good diagram reads at a glance. Apply
 - **Let the defaults show.** Don't add `no-*` opt-outs unless the user asked to hide or disable something — they strip helpful labels, values, and color.
 - **Pick a fitting direction.** Top-to-bottom for hierarchies and processes; left-to-right for pipelines and flows (where the type supports a direction).
 
-### Chart-type index (43) — pick the type, then fetch its section
+### Chart-type index (45) — pick the type, then fetch its section
 
 | id | when to use |
 | -- | ----------- |
@@ -130,6 +130,8 @@ Valid markup is the floor, not the goal. A good diagram reads at a glance. Apply
 | `sitemap` | site / app navigation structure |
 | `mindmap` | radial hierarchy of ideas from a central topic |
 | `org` | reporting hierarchy |
+| `family` | family tree / genealogy: unions (couples), children, remarriage, adoption, GEDCOM-style metadata |
+| `bracket` | single-elimination tournament bracket: winners auto-advance; seed the field for a day-0 skeleton or list results casually; two sides mirror to a championship |
 | `kanban` | task-board columns |
 | `gantt` | project scheduling with task dependencies and milestones |
 | `pert` | project network with three-point estimates and critical path |
@@ -137,6 +139,7 @@ Valid markup is the floor, not the goal. A good diagram reads at a glance. Apply
 | `version-control` | git / version-control branch-and-merge graph: commits, branches, merges, rebase, HEAD and remote-tracking (gitGraph-style) |
 | `timeline` | events, eras, and date ranges |
 | `event-line` | annotated narrative timeline — events on a line with descriptions, optionally not to scale (NOT the date-scaled `timeline`) |
+| `body` | human anatomy figure annotated by muscle name — for medical, exercise, and educational diagrams |
 | `journey-map` | UX flow with emotion scores, phases, annotations |
 | `cycle` | cyclical process (PDCA, OODA, DevOps loops) |
 | `raci` | tasks × roles responsibility matrix; variant (RACI / RASCI / DACI) is inferred from the markers used |
@@ -146,6 +149,10 @@ Valid markup is the floor, not the goal. A good diagram reads at a glance. Apply
 | `ring` | concentric rings of nested categories |
 | `treemap` | nested rectangles sized by value (budgets, disk usage, portfolios) |
 | `block` | author-controlled grid of nested, collapsible blocks (system / architecture layouts) |
+| `sketch` | GUI-first free-placement canvas: uniform shapes on a snap grid, arrows, tags (markup is app-generated) |
+| `goal` | single progress-toward-a-target value (`now` vs `target`) as a progress bar, thermometer, or gauge — KPIs, fundraising, quotas |
+| `countdown` | live "N days until X" that ticks every second and is accurate on every load — trip dates, launches, deadlines; the only dynamic chart type |
+| `clock` | live world-clock board: current time for people/places across time zones, ticking every second, with optional working-hours status and sundown line |
 | `map` | geographic concept map: regions, points, routes |
 | `wireframe` | low-fidelity UI layout with panels and controls |
 | `bar` | categorical comparisons (multi-series via `stack` / `group`) |
@@ -169,7 +176,7 @@ Valid markup is the floor, not the goal. A good diagram reads at a glance. Apply
 
 ### Common examples (curated, parse-clean)
 
-_The most common types, inline so you can generate them without a fetch. For the other 35, get the per-type section (see below)._
+_The most common types, inline so you can generate them without a fetch. For the other 42, get the per-type section (see below)._
 
 #### journey-map
 
@@ -281,6 +288,8 @@ ports
 ```dgmo
 class Ship Class Hierarchy
 
+solid-fill 
+
 interface Vessel
   + sail(): void
   + anchor(): void

package/docs/language-reference.md

@@ -42,7 +42,7 @@
 
 ## 0. AI Core
 
-The universal core: the cross-cutting anti-patterns (highest value per token) and the one-line index of all 45 chart types. The blocks below are machine-extracted (HTML-comment anchors) and embedded verbatim into every AI surface — IDE rule files, the Claude skill, the CLAUDE.md snippet — by `scripts/gen-ai-core.mjs`. Edit them here; never hand-edit a generated surface.
+The universal core: the cross-cutting anti-patterns (highest value per token) and the one-line index of all 46 chart types. The blocks below are machine-extracted (HTML-comment anchors) and embedded verbatim into every AI surface — IDE rule files, the Claude skill, the CLAUDE.md snippet — by `scripts/gen-ai-core.mjs`. Edit them here; never hand-edit a generated surface.
 
 <!-- AI-CORE:ANTIPATTERNS start -->
 ### Disambiguation — where DGMO diverges from LLM priors
@@ -101,7 +101,7 @@ Valid markup is the floor, not the goal. A good diagram reads at a glance. Apply
 <!-- AI-CORE:STYLING end -->
 
 <!-- AI-CORE:TYPE-INDEX start -->
-### Chart-type index (43) — pick the type, then fetch its section
+### Chart-type index (45) — pick the type, then fetch its section
 
 | id | when to use |
 | -- | ----------- |
@@ -116,6 +116,8 @@ Valid markup is the floor, not the goal. A good diagram reads at a glance. Apply
 | `sitemap` | site / app navigation structure |
 | `mindmap` | radial hierarchy of ideas from a central topic |
 | `org` | reporting hierarchy |
+| `family` | family tree / genealogy: unions (couples), children, remarriage, adoption, GEDCOM-style metadata |
+| `bracket` | single-elimination tournament bracket: winners auto-advance; seed the field for a day-0 skeleton or list results casually; two sides mirror to a championship |
 | `kanban` | task-board columns |
 | `gantt` | project scheduling with task dependencies and milestones |
 | `pert` | project network with three-point estimates and critical path |
@@ -123,6 +125,7 @@ Valid markup is the floor, not the goal. A good diagram reads at a glance. Apply
 | `version-control` | git / version-control branch-and-merge graph: commits, branches, merges, rebase, HEAD and remote-tracking (gitGraph-style) |
 | `timeline` | events, eras, and date ranges |
 | `event-line` | annotated narrative timeline — events on a line with descriptions, optionally not to scale (NOT the date-scaled `timeline`) |
+| `body` | human anatomy figure annotated by muscle name — for medical, exercise, and educational diagrams |
 | `journey-map` | UX flow with emotion scores, phases, annotations |
 | `cycle` | cyclical process (PDCA, OODA, DevOps loops) |
 | `raci` | tasks × roles responsibility matrix; variant (RACI / RASCI / DACI) is inferred from the markers used |
@@ -132,6 +135,10 @@ Valid markup is the floor, not the goal. A good diagram reads at a glance. Apply
 | `ring` | concentric rings of nested categories |
 | `treemap` | nested rectangles sized by value (budgets, disk usage, portfolios) |
 | `block` | author-controlled grid of nested, collapsible blocks (system / architecture layouts) |
+| `sketch` | GUI-first free-placement canvas: uniform shapes on a snap grid, arrows, tags (markup is app-generated) |
+| `goal` | single progress-toward-a-target value (`now` vs `target`) as a progress bar, thermometer, or gauge — KPIs, fundraising, quotas |
+| `countdown` | live "N days until X" that ticks every second and is accurate on every load — trip dates, launches, deadlines; the only dynamic chart type |
+| `clock` | live world-clock board: current time for people/places across time zones, ticking every second, with optional working-hours status and sundown line |
 | `map` | geographic concept map: regions, points, routes |
 | `wireframe` | low-fidelity UI layout with panels and controls |
 | `bar` | categorical comparisons (multi-series via `stack` / `group`) |
@@ -1710,6 +1717,51 @@ See spec §13A for full date-anchoring semantics, S-curve axes, and diagnostic c
 
 ---
 
+## 13AA. Family Diagrams (genealogy)
+
+<!-- TYPE:family -->
+
+<!-- TIPS start -->
+**Styling tips:** Two line shapes carry the whole tree: a **person line** (`Anne b: 1665, sex: f`) and a **union line** (`Anne + Jack m: 1701`), with children indented under the union. Declare each person **standalone** with their full metadata — per-side metadata on a union line is unsupported and re-stating a name just re-references the same person. Set `sex:` so cards color (m→blue, f→purple), but **treat the legend as the real sex channel**: blue and purple separate weakly under the 25% tint, so where color-vision matters distinguish with a `tag` group (labeled legend entries) instead. Reuse a name in a second union for remarriage (one card, two bars); a lone person with indented children is a single parent; a bare trailing `adopted` token marks an adopted child.
+<!-- TIPS end -->
+
+### Declaration
+
+```
+family [Title]
+```
+
+### Unions, children, remarriage
+
+A **union line** joins a couple with `+`; children are indented beneath it. Union-level metadata is only `m` (marriage year). Reuse a name to remarry; a lone person with indented children is a single parent.
+
+```dgmo
+family The Rackham Line
+
+Elizabeth Swann b: 1687, sex: f, occupation: Pirate King
+"Will Turner" b: 1685, sex: m
+
+Elizabeth Swann + "Will Turner" m: 1729
+  Henry Turner sex: m
+
+Henry Turner + Carina Smyth m: 1751
+  Joshamee sex: m
+  Anna adopted, sex: f
+```
+
+- **Person metadata** (fixed GEDCOM-flavored keys): `sex` (`m`/`f` → node color), `b`/`d` (birth/death year → a year-range row), `bp`/`dp` (birth/death place), `occupation`, `military`, `education`, `religion`, `burial`. Union-level: `m`. Unknown keys warn.
+- **Adoption:** a bare `adopted` token on a child line draws a dashed drop edge. A person literally named "Adopted" must be quoted.
+- **Divorce:** a bare `divorced` token on a union line (`A + B m: 1980 divorced`) draws a dashed marriage bar; children still attach.
+- **Deceased:** a person with a death year (`d:`) is auto-marked with a muted dagger (†) — derived, no syntax; add `no-daggers` to hide it.
+- **Children** are auto-ordered eldest→left by birth year (`b:`); undated children keep declaration order.
+- **Unknown/private person:** a bare `?` renders a faint, solid-bordered, name-only placeholder card; each `?` is a distinct person.
+- **`generations`** (option): draws a left gutter of Roman-numeral generation labels (`Gen I`, `Gen II`, …) plus subtle zebra shading behind alternating generations.
+- **`highlight <name>`** (directive): dims everyone outside that person's bloodline (ancestors + descendants + spouses stay lit).
+- **Sex → color:** `sex: m` → blue, `sex: f` → purple, unset → gray (25% tint). An explicit `tag`/inline color overrides the sex color.
+- The union split cuts `m:` metadata first, THEN splits ` + ` within the name region — so a `+` inside a quoted name (`"Anne + Jack"`) or a metadata value never mis-splits. Per-side `key: value` metadata on a union line is not supported — declare the person standalone.
+
+---
+
 ## 13B. Swimlane Diagrams
 
 <!-- TYPE:swimlane -->
@@ -1718,38 +1770,31 @@ See spec §13A for full date-anchoring semantics, S-curve axes, and diagnostic c
 **Styling tips:** Give each lane a color and let nodes inherit it — reach for a `tag` group only when you need a *second* dimension (e.g. risk) that deliberately breaks lane color. Echo the gateway/terminal delimiters (`<Review>`, `(Paid) success`) even though bare names also resolve — it keeps the source self-documenting. Put every edge label *inside* the arrow (`-invalid->`), never as a trailing word.
 <!-- TIPS end -->
 
-Swimlane diagrams model a cross-functional process: actors/systems are **lanes**, the process flows along the flow axis (`direction LR` default, `TB` transposes), and optional `[Phase]` columns group steps into stages. Nodes are tasks (bare), exclusive gateways (`<X>`), parallel gateways (`<+ X>`), terminals (`(X)`), and subprocesses (`[[X]]`). Edges go last as a flow block; a back-edge to an earlier node draws a routed loop.
+Swimlane diagrams model a cross-functional process: actors/systems are **lanes**, the process flows along the flow axis (`direction LR` default, `TB` transposes), and optional `[Phase]` columns group steps into stages. Nodes are tasks (bare), exclusive gateways (`<X>`), parallel gateways (`<+ X>`), terminals (`(X)`), and subprocesses (`[[X]]`). A `lane` block **owns its edges** — nodes and their outgoing `->` edges are written inline, no separate flow block. A back-edge to an earlier node draws a routed loop.
 
 ```
 swimlane Weekly Publishing
 direction LR
 
 lane Writer gray
+  Draft Post -> Review
+  Revise -> Review
 lane Editor blue
-lane Social green
-
-Writer
-  Draft Post
-  Revise
-Editor
   <Review>
-  Schedule
-  Publish
-Social
+    -changes-> Revise
+    -ok-> Schedule
+  Schedule -> Publish
+  Publish -> Promote
+lane Social green
   Promote
-
-Draft Post -> <Review>
-<Review>
-  -changes-> Revise -> <Review>
-  -ok-> Schedule -> Publish -> Promote
 ```
 
 ### Structure
 
-- `lane <Name> [color]` declares a row (occupant-neutral; person, system, or org) in order. The trailing color (§1.5) tints the band and is the default node fill.
-- A bare line matching a declared lane opens that lane's context; indented lines beneath it are nodes.
-- `[Phase]` opens a phase column (3-deep: phase ▸ lane ▸ node). With no `[Phase]`, the diagram is 2-deep (lane ▸ node). A node's phase membership can only push it right, never left of its column.
-- Node names are globally unique; the flow block references a node by name.
+- `lane <Name> [color]` declares a row (occupant-neutral; person, system, or org) **and opens its block** — the indented lines beneath are its nodes and their inline edges. The trailing color (§1.5) tints the band and is the default node fill. Lane order is first-appearance; re-opening a lane resumes it.
+- A node is owned by the lane where it is a **line-head** (bare node or arrow source); elsewhere the name is a reference. References may point forward. Names are **lane-scoped** — resolve own-lane-first → global-unique → ambiguous; qualify a shared name `Lane.Node`.
+- An unresolved target auto-creates only if **delimited** (`(…)`/`<…>`/`[[…]]`, taking the edge's lane/phase); an unresolved **bare task** is `E_SWIMLANE_UNKNOWN_NODE` (typo protection).
+- `[Phase]` opens a phase column (3-deep: phase ▸ `lane` block ▸ nodes). With no `[Phase]`, the diagram is 2-deep (lane ▸ nodes). A node's phase membership can only push it right, never left of its column.
 
 ### Node tokens
 
@@ -2170,18 +2215,18 @@ no-center-total          // pie: hide the center total (shown by default when `h
 
 - `no-name` — hide name (segment / point / cell / node / set)
 - `no-value` — hide numeric value
-- `no-percent` — hide share-of-total percentage (pie-family only)
+- `no-percent` — hide the percentage (share-of-total on pie-family; stage-over-stage conversion on funnel)
 
 Each chart honors the subset of flags that has a renderable atom on it:
 
 - pie / polar-area: all three
-- funnel: `no-name`, `no-value`
+- funnel: all three (`no-percent` hides the conversion %)
 - bar / line / radar: `no-value`
 - scatter: `no-name`
 - heatmap: `no-value`
 - sankey, arc, slope, quadrant, venn: name-suppression deferred — names render by default and cannot yet be hidden
 
-`no-percent` on a non-pie-family chart is silently ignored (the chart has no percent atom). Cartesian charts (bar, line) render values on each bar / point by default.
+`no-percent` on a chart with no percent atom is silently ignored. Cartesian charts (bar, line) render values on each bar / point by default.
 
 **Eras (line only):**
 
@@ -2331,6 +2376,8 @@ Signups 800
 Purchases 200
 ```
 
+Each stage renders its name to the left of the band (in the band's color), its value centered inside the band (falling back beside it when the band is too narrow), and a muted stage-over-stage conversion % to the right — no leader lines. The first stage has no % (nothing to convert from). `no-percent` hides the conversion %; `no-name` / `no-value` hide the other parts.
+
 ---
 
 ## 17. Visualizations
@@ -2471,6 +2518,53 @@ Group a run of events into a labeled section with a `[Name]` bracket, then **ind
 - `no-box` — card-less style for slides: a tag-colored label, a rule, and the description below (no box / fill / border).
 - `no-legend` — hide the tag legend.
 
+### 16.4C Body Diagrams
+
+<!-- TYPE:body -->
+
+<!-- TIPS start -->
+**Styling tips:** Reach for `body` when the drawing IS the human figure — colour muscle groups over a skin layer to show which parts a workout targets, where an injury sits, or how the musculature is organised. Choose the figure with `male`/`female` and `front`/`back`; each named muscle group takes a tag so the legend carries the meaning. Best for fitness, medical, exercise, and educational diagrams — not for generic part-to-whole (that's `pie`/`treemap`).
+<!-- TIPS end -->
+
+**Figures:** male and female, front and back — four figures. `skin` form renders any figure as a plain silhouette (with head + hair) instead of the segmented muscle map. `skeletal` is reserved.
+
+#### Declaration
+
+```
+body [Title]
+```
+
+#### Form / sex / view (bare directives)
+
+Set the figure with bare directives before the parts: `muscle` (default) or `skin`; `male` (default) or `female`; `front` (default) or `back`. Each is optional. **Name both `front` and `back`** to render the two views side by side in one diagram — a part is drawn on whichever view(s) contain it (`chest` on front, `lats` on back, `deltoids`/`calves` on both).
+
+#### Parts
+
+A bare line is a **catalog muscle name**, in any order, with optional trailing tag metadata and an indented body note. Names accept gym shorthand or formal anatomy (`pecs` / `pectoralis-major` → `chest`; `quads` → `quadriceps`).
+
+```
+body Push Day
+muscle
+
+tag Effort as e
+  Primary red
+  Secondary orange
+
+chest        e: Primary
+  Barbell bench press — 4×8
+deltoids     e: Primary
+triceps      e: Secondary
+abs          e: Secondary
+```
+
+- **Part** — a catalog name for the active figure. Front: `chest`, `deltoids`, `biceps`, `triceps`, `abs`, `obliques`, `trapezius`, `forearm`, `quadriceps`, `adductors`, `calves`, `tibialis`. Back: `lats`, `trapezius`, `rear-delts`, `triceps`, `lower-back`, `glutes`, `hamstring`, `calves`, `forearm`. Fine heads (`vastus-lateralis`, `serratus-anterior`, `biceps-femoris`, …) and gym/anatomical aliases (`pecs`/`pectoralis-major`→chest, `quads`→quadriceps, `glutes`→gluteal) both resolve. Unknown names warn.
+- **Tag** — trailing same-line metadata (`e: Primary`); colors the highlighted muscle, its leader, and its label.
+- **Note** — bare indented body line (like `pyramid`/`ring`); the first note prints beneath the muscle's gutter label.
+
+#### Options
+
+- `no-legend` — hide the tag legend.
+
 ### 16.4B Version-Control Diagrams
 
 <!-- TYPE:version-control -->
@@ -3528,6 +3622,317 @@ In the desktop app a block diagram is interactive: click a container header to c
 
 ---
 
+## 24E. Sketch Diagrams
+
+<!-- TYPE:sketch -->
+
+<!-- TIPS start -->
+**Styling tips:** Sketch is a GUI-authored format — the desktop and web canvas editors generate this markup, so hand-writing it is the exception. If you generate it anyway: keep it SMALL (sketches read best under ~15 shapes), and either omit `at:` everywhere (shapes flow into rows) or use integer half-slot coordinates with shapes at least 2 half-slots apart on one axis. Alias any shape an edge references (`as con`). Never write `size:`, colors, fonts, or a `shape:` outside the closed set (database, queue, cloud, person, document, note). In sketch, `~` dashed means secondary emphasis, NOT async. Categorize with a tag group instead of reaching for more shape kinds — kind-of-thing is meaning, and meaning lives in tags. Reach for `sketch` when the drawing itself is the content; reach for `boxes-and-lines` when topology should auto-lay-out.
+<!-- TIPS end -->
+
+A **GUI-first constrained canvas**: uniformly-sized shapes placed freely on a snap grid, arrows between them, meaning through tags. The renderer owns all styling — authors own placement, connection, naming, and tags. Every shape has ONE universal footprint (no resizing); text always fits (shrink → smart-wrap → `…`). Pick `sketch` when the spatial arrangement is yours to decide; pick `boxes-and-lines` when topology should auto-lay-out.
+
+### Declaration
+
+```
+sketch [Title]
+```
+
+### Example
+
+```
+sketch Plunder Pipeline
+
+tag Crew
+  Deck
+  Hold
+
+Spyglass Feed shape: cloud, at: 0 0, crew: Deck
+  -sightings-> con
+Captain's Console as con at: 2 0, crew: Deck
+  -orders-> bq
+Divvy Service as dvy at: 4 0, crew: Hold
+
+[Below Decks] at: 2 2, crew: Hold
+  Booty Queue as bq shape: queue, at: 0 0
+    ~haul~> dvy
+  Ship Ledger as ledger shape: database, at: 2 0
+
+[Armory] as armory at: 0 2, collapsed
+  Powder Store at: 0 0
+```
+
+### Shapes
+
+One top-level line = one shape — a **bare name** plus same-line `key: value` metadata. `shape:` morphs from the default rectangle: `database`, `queue`, `cloud`, `person`, `document`, `note` (rectangle is never written; unknown values warn and fall back). `note` renders as a sticky-style card with smaller left-aligned multiline text. Duplicate labels are legal **when aliased** (`Cache as c1` / `Cache as c2`); unaliased duplicates merge (standard dgmo semantics).
+
+### Coordinates — `at: C R`
+
+Integer **half-slot steps** (a slot = one footprint + the mandatory gap), origin-normalized; box children are relative to the box origin. `at:` is **optional** — un-positioned shapes flow-place in rows below existing content. Hand-authored overlap auto-resolves with a warning; nothing renders broken.
+
+### Lines
+
+Indented under the source shape, targeting an alias (or an unambiguous bare label). Six forms: `-label->` one head · `<-label->` both heads · `-label-` no heads, plus `~` dashed twins. Unlabeled headless lines are `--` / `~~`. No left-pointing arrows — write `B -> A`, never `A <- B`. A tag on the edge tail (`crew: Hold`) colors the line. Both ends must attach.
+
+### Boxes
+
+`[Brackets]` = a **box** (labeled group frame) — the only bracket meaning in sketch. Label mandatory; one level only (no nested boxes); taggable (frame tints, cascades to children, individual overrides); bare `collapsed` folds it to a card with the collapse-bar and edges re-target the card. Interactive fold/unfold in the app; static export renders the authored state.
+
+### Node Metadata
+
+| Key       | Type           | Default   | Description                                     |
+| --------- | -------------- | --------- | ----------------------------------------------- |
+| `shape`   | closed set     | rectangle | `database` / `queue` / `cloud` / `person` / `document` / `note` |
+| `at`      | `C R` integers | flow-placed | Half-slot position (origin-normalized)        |
+| `collapsed` | flag         | —         | Box only — start folded (collapse-bar)          |
+| `<tag>`   | declared value | untagged (neutral gray) | Tag value (cascades from box; edge tails color the line) |
+
+### Directives
+
+| Directive    | Effect                  |
+| ------------ | ----------------------- |
+| `no-legend`  | Hide the tag legend.    |
+
+### Interactivity vs export
+
+In the desktop and web app a sketch opens in the **canvas editor** (the code pane hides behind a toggle); boxes fold/unfold interactively. Static SVG / PNG export renders the authored state — the same interactive-vs-export split the map, treemap, and block charts use.
+
+---
+
+## 24E. Goal
+
+<!-- TYPE:goal -->
+
+<!-- TIPS start -->
+**Styling tips:** A single progress-toward-a-target reading — one `now` against one `target`, answering "how close am I?". Reach for it for a KPI tile, a fundraising thermometer, a quarterly quota, or a completion percentage; there is no time axis, series, or milestones (use `line` for a trend, `countdown` for a live deadline). Put the **unit in the title** (`Marathon Fund ($)`, `Grog Barrel Fill (L)`) — there is no format/currency directive. `now` and `target` are **space-separated `key value`** directives, no colon (`now 6400` / `target 10000`); the percent is `now / target` and values auto-compact (`6.4k`, `1.2M`). Pick the face for the story with a bare flag on its own line: the default progress **bar** for a plain KPI, `thermometer` for fundraising/fill-the-tank framings, `gauge` for a speedometer/quota dial — all three read the same value pair. The fill is **auto traffic-light** by completion (`< 50%` red, `50–80%` orange, `≥ 80%` green; over-target stays green) so the color already reads the number's health — leave it unless you have reason to override with a trailing color on the title line (`goal Marathon Fund ($) green`) or `no-auto-color` (flat palette color). Over-target clamps the fill at 100% while the `%` label stays truthful (`120%`). Add a `note` — inline (`note Still waiting on three crews`) or a block header on its own line with an indented body — to caption the number with context (who's still owed, what's left); it takes simple markdown (`**bold**`, `*italic*`, `` `code` ``) and `- ` bullets. `solid-fill` for a bolder fill; `no-percent` / `no-value` / `no-title` / `no-note` to drop labels.
+<!-- TIPS end -->
+
+A single progress-toward-a-target value: one `now` measured against one `target`, drawn in one of three static faces. No time axis, no series, no milestones — just "how close am I?". The face is a bare-flag mode directive under the title (like treemap's `radial`); all three faces consume the same value pair.
+
+### Declaration
+
+```
+goal [Title with unit]
+
+[thermometer | gauge]     // omit for the default progress bar
+now <number>
+target <number>
+```
+
+### Example
+
+```
+goal Doubloons Recovered ($)
+
+thermometer
+
+now 6400
+target 10000
+```
+
+### Directives
+
+| Directive              | Effect                                                        |
+| ---------------------- | ------------------------------------------------------------- |
+| `thermometer` / `gauge`| Select the render face (bare flag; omit for the progress bar). |
+| `now <number>`         | Current value (required; may exceed the target).              |
+| `target <number>`      | Goal value (required; must be > 0).                           |
+| `no-percent`           | Hide the `%` label.                                           |
+| `no-value`             | Hide the raw `now / target` label.                            |
+| `solid-fill`           | Full-saturation fill instead of the default 25% tint.         |
+| `no-title`             | Hide the banner title.                                        |
+| `no-note`              | Suppress the `note` block even if one is authored.           |
+| `no-auto-color`        | Disable the traffic-light bands; use the flat palette color.  |
+| `note <text>` / `note` + indented body | Free-text caption beside/below the face (§ note block). |
+
+### Note block
+
+An optional caption. Inline (`note Still waiting on three crews`) or a block header on its own line followed by an **indented body**:
+
+```
+goal Grog Barrel Fill (L)
+thermometer
+now 34
+target 50
+note
+  **Great job, crew!** Still waiting on tallies from:
+  - Seattle — first mate says "soon"
+  - Columbus — *almost there!*
+```
+
+The body supports inline `**bold**` / `*italic*` / `` `code` ``, `- `/`* ` bullets, and blank-line gaps. It renders in the left column for `thermometer`/`gauge` and under the bar for the default face. `no-note` hides it even when authored.
+
+### Values & color
+
+Values accept `_` separators (`10_000`) but not thousands commas; the unit lives in the title. Color precedence: (1) an explicit trailing color token on the title line (`goal Marathon Fund ($) green`, §1.5) always wins; (2) otherwise the **auto traffic-light** band by completion — `< 50%` red, `50–80%` orange, `≥ 80%` green (over-target stays green), which needs a `target`; (3) `no-auto-color` disables the bands and falls back to the palette series color. The fill is a 25% tint of the resolved color; `solid-fill` opts into full saturation.
+
+### Semantics
+
+Percent is `now / target`. Over-target clamps the fill at 100% while the `%` label shows the true value (e.g. `120%`); the gauge needle pins at max. A negative `now` clamps the fill to 0% but keeps the label truthful. A missing or ≤ 0 `target` emits an error-severity diagnostic and the chart falls back to a 0% shell; a missing `now` is treated as 0 with a warning.
+
+---
+
+## 24E. Countdown
+
+<!-- TYPE:countdown -->
+
+<!-- TIPS start -->
+**Styling tips:** The only dynamic chart — it ticks every second and is accurate on every load, so use it for a live "N days until X" widget, not a static report. Keep the title to the event (`Trip to Japan`); the target date renders as a caption automatically. `target` is a space-separated `key value` directive (no colon): a bare date (`2026-08-21`) counts to the viewer's local midnight, a datetime or offset is honored. Default `units days` reads best for weeks/months out; use `units full` for a launch-day `Nd HH:MM:SS` clock. Set `expired` to the celebration text (`🚀 Shipped!`); after the target passes every live surface shows it and the tick stops. On images (PNG export, `.svg` via `<img>`, GitHub camo) it can't tick and shows the whole-day count baked at export time — the correct fallback.
+<!-- TIPS end -->
+
+The only *dynamic* dgmo chart: a single "N days until X" recomputed against the viewer's clock on every load and ticking every second on any live surface. Distinct from `goal` (static) — a countdown has no `now`/`target` pair, just one future instant. The renderer bakes a whole-day fallback number (the no-JS floor); a tiny page-level ticker overwrites it live and, in `units full`, upgrades it to `Nd HH:MM:SS`.
+
+### Declaration
+
+```
+countdown [Title]
+
+target <ISO date | datetime | now>
+units <days | full>       // default days
+expired <text>            // default "Now!"
+```
+
+### Example
+
+```
+countdown Trip to Japan
+
+target 2026-08-21
+```
+
+### Directives
+
+| Directive               | Effect                                                                 |
+| ----------------------- | ---------------------------------------------------------------------- |
+| `target <iso>`          | The future instant (required). `2026-08-21`, `2026-08-21T18:00`, or with a tz offset. The literal `now` resolves at render (→ immediately expired; for testing). |
+| `units <days\|full>`    | `days` (default) shows whole days (ceil); `full` ticks `Nd HH:MM:SS` on live surfaces. |
+| `expired <text>`        | Shown once the target passes; the tick stops. Default `"Now!"`.        |
+
+### Values & color
+
+A bare `YYYY-MM-DD` counts to the viewer's **local midnight**; a datetime with no offset is viewer-local; an explicit offset is honored. The trailing-token color rule (§1.5) applies to the title line (`countdown Trip to Japan blue`) and tints the figure.
+
+### Semantics
+
+Days mode uses `ceil` — a target later *today* reads "1 day", not "0". Full mode floors the days and shows `HH:MM:SS` for the remainder. Once the target passes, the `expired` text replaces the number and that node stops ticking (no negative counts). Live surfaces recompute from the absolute target on every load/route-change/note-open, so there is **no persisted state** and no drift; image surfaces (PNG, `.svg`-as-image, GitHub camo) show the whole-day count baked at export time.
+
+---
+
+## 24Eb. Clock
+
+<!-- TYPE:clock -->
+
+<!-- TIPS start -->
+**Styling tips:** A live world clock — one panel per person or place, each showing the CURRENT time in its zone and ticking every second, accurate the instant the page loads. Reach for it to answer "what time is it for the crew right now": a distributed team's local times, a single collaborator's clock, or the overlap window for scheduling a call. The first line declares the type and a title (`Crew standups`). Each entry is one line, `<place> <IANA/Zone> [as <label>]`: a human-readable place, then a real IANA zone (`Europe/London`, `America/New_York`, `America/Los_Angeles`, `Asia/Tokyo`) — never a bare offset like `GMT+1`, which doesn't track daylight saving. Use `as <label>` to name the person or role behind a zone (`New York America/New_York as Dani (NY)`); the label becomes the caption. The single-clock case is common and encouraged — one title, one entry (`clock Dani` / `New York America/New_York`). Global directives are flat, no colon: `analog` for analog dials (digital is the default face), `time-24` for a 24-hour readout (12h am/pm is the default), and optional context bands `hours 9-17` + `days mon-fri` (the window accepts `HH:MM` and am/pm, e.g. `hours 8:30-17:15`) to shade each zone's working window so out-of-hours people read at a glance. `no-sun` hides the sunrise/sundown indicator (on by default). Add `hours`/`days` only when the point is scheduling overlap; drop them for a plain "current time" widget. Zones are **colorized by default** (`color-by`, default `place` — a distinct palette accent per place); reach for a semantic mode when color should *mean* something: `color-by time` or `color-by daylight` make an at-a-glance world board read as day-vs-night (order the zones west→east so the daylight sweeps across), and `color-by work` turns a standup/team board green/amber/grey by availability — it needs `hours` set. A hand-set per-zone color (`London Europe/London as UK team purple`) is a **defined** shade that always wins over the dimension, so you can pin one zone and let the rest follow. `color-by none` goes neutral. On image surfaces (PNG, `.svg` via `<img>`, GitHub camo) it can't tick and bakes the time at export — the correct graceful fallback.
+<!-- TIPS end -->
+
+The second *dynamic* dgmo chart (with `countdown`): a live board of world clocks recomputed against the viewer's clock every second. Flat syntax — the first line is `clock <Title>`; every other non-blank line is either a board-level directive (its first token is an option keyword) or a place row. Order-independent; no colons anywhere.
+
+### Declaration
+
+```
+clock [Title]
+
+analog                      // analog dials; digital is the default face
+hours <start>-<end>         // optional working window (24h, HH:MM or am/pm)
+days <mon-fri | mon,wed,fri> // optional working days (default mon-fri)
+no-sun                      // hide the sundown/sunrise line (on by default)
+time-24                     // 24-hour readout (12h am/pm is the default)
+no-title                    // suppress the board title
+direction lr                // lay the panels out in a row
+color-by <place|work|daylight|time|none> // zone coloring; default place
+
+<place tokens…> <IANA/Zone> [as <label…>]
+```
+
+### Example
+
+```
+clock Crew standups
+hours 9-17
+days mon-fri
+
+London        Europe/London        as UK team
+New York      America/New_York     as Dani (NY)
+Los Angeles   America/Los_Angeles  as West coast
+```
+
+### Directives
+
+| Directive              | Effect                                                                 |
+| ---------------------- | ---------------------------------------------------------------------- |
+| `analog`               | Analog dials for the WHOLE board. Digital is the default face. |
+| `hours <start>-<end>`  | Working window (e.g. `9-17`, `8:30-17:15`, or am/pm); drives the status chip, evaluated in each row's own zone. |
+| `days <range\|list>`   | Working days: `mon-fri` or `mon,wed,fri`. Default Mon–Fri. No effect without `hours`. |
+| `no-sun`               | Hide the sundown/sunrise line (on by default when the zone's city coordinates are known). |
+| `time-24`              | 24-hour readout (12-hour am/pm is the default).                        |
+| `no-title`             | Suppress the board title.                                              |
+| `direction lr`         | Lay the panels out in a row (columns) instead of stacked.             |
+| `color-by <place\|work\|daylight\|time\|none>` | Which dimension colors the zones. Default `place`; `color-by none` goes neutral. `place` = identity accent per place; `work` = green/amber/grey by the `hours` window; `daylight` = warm sun-up / cool sun-down; `time` = local-hour dawn→night ramp (order zones west→east). A hand-set (**defined**) per-zone trailing color always wins over the dimension. |
+
+### Entry grammar
+
+Each place row is `<place tokens…> <IANA/Zone> [as <label…>]`. The zone is the token containing `/` (a full IANA name like `America/New_York`); text before it is the place, and `as <label>` sets the display alias (default = place). A row that is just a zone (`Asia/Tokyo`) uses the zone's city as the place.
+
+### Semantics
+
+Each row's time comes from `Intl.DateTimeFormat` with that row's zone, so DST is always correct. The renderer bakes the time, hands, offset, status, and sundown line at render (the no-JS floor); a tiny page-level ticker recomputes them from the baked zone/coords every second — no persisted state, no drift. Image surfaces (PNG, `.svg`-as-image, GitHub camo) show the time baked at export.
+
+---
+
+## 24F. Bracket
+
+<!-- TYPE:bracket -->
+
+<!-- TIPS start -->
+**Styling tips:** A single-elimination tournament bracket: winners auto-advance rightward toward a championship. Reach for it for playoff trees, knockout draws, and seeded fields. Two ways to author: seed the field for a **day-0 skeleton** (`seed 1 Team A`, `seed 2 Team B` …) and let matches fill in, or list results casually as `A beats B` / `A vs B` lines and let winners flow forward. Name the columns with `rounds` (comma-separated, e.g. `rounds Quarterfinals, Semifinals, Final`) or an indented `rounds` block with per-round colors. The two sides mirror inward to the final. Color a competitor's box outline with a `tag` group; `accent` overrides the winner highlight (default blue). `single-elim` is the default; opt-outs are `no-round` (hide column labels) and `no-legend`.
+<!-- TIPS end -->
+
+A single-elimination tournament bracket. Winners auto-advance up a tree that builds itself from the results — a one-sided ladder for a simple pool, or two `[Side]` columns that mirror inward and meet at a championship (MLB / NBA / NCAA-style). Any `seed` line switches on **seeded mode** (day-0 skeleton); otherwise the bracket is **casual** (structure inferred from `beats` / `vs` lines).
+
+### Declaration
+
+```
+bracket [Title]
+rounds [Col1, Col2, ...]         // optional column names, entry round → inner
+
+[Side] [color]                   // optional — two sides mirror to a center final
+  seed N [Competitor]            // seeded mode: declare the field (day-0 skeleton)
+  [Winner] beats [Loser] [score] // decided match — WINNER on the left, score cosmetic
+  [A] vs [B]                     // pending match — no winner yet
+```
+
+### Example
+
+```
+bracket Grog Cup
+
+Black Pearl beats Sea Serpent 5-3
+Salty Dog beats Kraken 4-2
+Black Pearl beats Salty Dog 6-5
+```
+
+### Directives
+
+| Directive                      | Effect                                                                       |
+| ------------------------------ | ---------------------------------------------------------------------------- |
+| `rounds A, B, C`               | Name the columns entry-round → inner (or an indented block with per-round `Name color`); absent → generic `Round N` / `Final`. |
+| `seed N [Name] [k: v]`         | Declare a seeded entrant → seeded mode + day-0 skeleton (top seeds get byes); trailing `k: v` tags the team. |
+| `tag Group [as g]`             | Tag group (block/kanban idiom) — a competitor's tag value colors its box outline; a legend renders. |
+| `[Side] [color]`               | A bracket column (kanban idiom); two sides mirror to a center championship.   |
+| `[Winner] beats [Loser] [score] [@ Home]` | A decided match — the left name advances; score is cosmetic; `@ Home` marks the host. Indent prose under it for commentary. |
+| `[A] vs [B]`                   | A pending, undecided match (both boxes drawn, no winner emphasis).            |
+| `accent <color>`               | Winner accent color override (default blue). Tags/sides still win per-box.    |
+| `no-round`                     | Suppress the round/column labels.                                            |
+| `no-legend`                    | Hide the tag legend (outlines still colored).                               |
+| `single-elim` / `double-elim` / `seeded` | Format flags. `double-elim` reserved — not yet supported; `seeded` forces seeded mode. |
+
+### Semantics
+
+The winner is always the left operand of `beats`, regardless of the score; a score that shows the winner lower emits a warning but keeps the declared winner. Reusing a name advances that competitor (same string = same entrant); a competitor whose first appearance is a later round simply never played round 1 (a bye). In seeded mode the field builds the standard single-elim skeleton (recursive 1-vs-N seeding: `3v6` / `4v5` for a six-team side, top seeds bye), every slot renders on day 0, and `beats` lines overwrite the `TBD` slots as games are played. Duplicate competitor names error (names are identifiers); `double-elim` parses but emits a "not yet supported" diagnostic.
+
+---
+
 ## 24A. RACI Matrices (RACI / RASCI / DACI)
 
 <!-- TYPE:raci -->

package/gallery/fixtures/body.dgmo

@@ -0,0 +1,17 @@
+body Powder Monkey Push Day
+muscle
+front
+
+tag Effort as e
+  Primary red
+  Secondary orange
+  Warm-up yellow
+
+chest        e: Primary
+  Barbell bench press — 4×8
+deltoids     e: Primary
+  Overhead press — 3×10
+triceps      e: Secondary
+  Rope pushdowns — 3×12
+abs          e: Warm-up
+  Plank — 3×45s