@diagrammo/dgmo 0.8.22 → 0.8.25

package/docs/guide/chart-pie.md

@@ -3,12 +3,12 @@
 ```dgmo
 pie Crew Roles Distribution
 
-Sailors: 45
-Gunners: 20
-Marines: 15
-Officers: 8
-Specialists: 7
-Cooks & Surgeons: 5
+Sailors 45
+Gunners 20
+Marines 15
+Officers 8
+Specialists 7
+Cooks & Surgeons 5
 ```
 
 ## Syntax
@@ -16,7 +16,7 @@ Cooks & Surgeons: 5
 ```
 pie Chart Title
 
-Label: value
+Label value
 ```
 
 ## Metadata Keys
@@ -28,12 +28,12 @@ Label: value
 
 ## Data Format
 
-Each data line follows the pattern `Label: value`:
+Each data line follows the pattern `Label value`:
 
 ```
-Sailors: 45
-Gunners: 20
-Officers: 8
+Sailors 45
+Gunners 20
+Officers 8
 ```
 
 Slices are automatically colored using the Nord palette.

package/docs/guide/chart-polar-area.md

@@ -3,11 +3,11 @@
 ```dgmo
 polar-area Captain's Skills
 
-Navigation: 90
-Swordsmanship: 75
-Leadership: 85
-Cunning: 95
-Seamanship: 80
+Navigation 90
+Swordsmanship 75
+Leadership 85
+Cunning 95
+Seamanship 80
 ```
 
 ## Syntax
@@ -15,7 +15,7 @@ Seamanship: 80
 ```
 polar-area Chart Title
 
-Label: value
+Label value
 ```
 
 ## Metadata Keys
@@ -27,12 +27,12 @@ Label: value
 
 ## Data Format
 
-Each data line follows the pattern `Label: value`:
+Each data line follows the pattern `Label value`:
 
 ```
-Navigation: 90
-Swordsmanship: 75
-Leadership: 85
+Navigation 90
+Swordsmanship 75
+Leadership 85
 ```
 
 Segments are automatically colored using the Nord palette.

package/docs/guide/chart-pyramid.md

@@ -0,0 +1,111 @@
+# Pyramid Diagram
+
+```dgmo
+pyramid Maslow's Hierarchy of Needs
+
+Self-Actualization | color: purple
+  Morality, creativity, acceptance of facts.
+
+Esteem | color: blue
+  Respect, recognition, confidence.
+
+Love & Belonging | color: green
+  Friendship, intimacy, family.
+
+Safety | color: yellow
+  Security, employment, health.
+
+Physiological | color: orange
+  Food, water, warmth, rest.
+```
+
+## Overview
+
+Pyramid diagrams show a hierarchy of stacked layers. Each layer gets a colored band with a label and an optional description. Source order reads apex-first — the first layer in the file is the narrowest (visual top), the last is the widest (visual bottom). Use `inverted` to flip into a funnel orientation.
+
+## Syntax
+
+```
+pyramid Title
+
+LayerLabel
+LayerLabel | color: blue
+LayerLabel | color: green
+  Indented description
+```
+
+The first line declares the chart type and an optional title. Each non-indented, non-directive line declares one layer. At least two layers are required.
+
+## Layers
+
+```
+pyramid Roles
+
+Executives | color: purple
+Managers | color: blue
+Individual Contributors | color: green
+```
+
+### Layer Pipe Metadata
+
+| Key | Type | Default | Description |
+|-----|------|---------|-------------|
+| `color` | palette name | auto-assigned | Layer color |
+| `description` | string | — | One-liner shown beside the layer |
+
+### Descriptions
+
+Indented lines under a layer add description text. Markdown inline formatting is supported (`**bold**`, `*italic*`, `` `code` ``, `[links](url)`). Bullet points with `- item` render as `• item`.
+
+```
+Wisdom | color: purple
+  Ethical judgment, acting with insight.
+  - Knowing *why* something matters
+  - Acting with long-term perspective
+```
+
+If both `| description: text` and indented lines exist, they concatenate (pipe first, then indented).
+
+## Directives
+
+| Directive | Effect |
+|-----------|--------|
+| `inverted` | Flip apex to the bottom (funnel orientation). Source order is preserved — the first layer is always the visual top. |
+
+```
+pyramid Acquisition Funnel
+
+inverted
+
+Visitors | color: blue
+Signups | color: cyan
+Activated | color: green
+Paid | color: orange
+```
+
+## Overflow Handling
+
+When descriptions don't fit a layer's band, the renderer automatically:
+
+- **Wraps** text at the column edge so nothing leaves the canvas
+- **Truncates** with "…" when content exceeds the available lines
+- **Alternates** descriptions left ↔ right when a single column can't hold them
+- **Reveals** the full description when a layer is highlighted (in-app), hiding siblings so it has room
+
+## Complete Example
+
+```dgmo
+pyramid The DIKW Pyramid
+
+Wisdom | color: purple
+  Ethical judgment, acting with insight — knowing *why*.
+
+Knowledge | color: blue
+  Synthesized information — knowing *how*.
+
+Information | color: green
+  Processed data with context — knowing *what*.
+
+Data | color: yellow
+  Raw facts and measurements — unprocessed signals.
+```

package/docs/guide/chart-radar.md

@@ -3,11 +3,11 @@
 ```dgmo
 radar Ship Combat Rating
 
-Firepower: 85
-Speed: 70
-Armor: 60
-Maneuverability: 90
-Crew Morale: 75
+Firepower 85
+Speed 70
+Armor 60
+Maneuverability 90
+Crew Morale 75
 ```
 
 ## Syntax
@@ -15,7 +15,7 @@ Crew Morale: 75
 ```
 radar Chart Title
 
-Label: value
+Label value
 ```
 
 ## Metadata Keys
@@ -30,9 +30,9 @@ Label: value
 Each data line defines one axis of the radar with its value:
 
 ```
-Firepower: 85
-Speed: 70
-Armor: 60
+Firepower 85
+Speed 70
+Armor 60
 ```
 
 Values are plotted on axes radiating from the center, connected by a filled polygon.

package/docs/guide/chart-scatter.md

@@ -5,17 +5,16 @@ scatter Cannon Range vs Powder Charge
 x-label Powder (lbs)
 y-label Range (yards)
 
-// label: x, y
-Long Tom: 12, 1800
-Demi-Culverin: 8, 1200
-Carronade: 4, 400
-Swivel Gun: 2, 250
-Nine-Pounder: 6, 900
-Eighteen-Pounder: 10, 1500
-Basilisk: 14, 2000
-Falconet: 3, 350
-Minion: 5, 700
-Saker: 7, 1050
+Long Tom 12 1800
+Demi-Culverin 8 1200
+Carronade 4 400
+Swivel Gun 2 250
+Nine-Pounder 6 900
+Eighteen-Pounder 10 1500
+Basilisk 14 2000
+Falconet 3 350
+Minion 5 700
+Saker 7 1050
 ```
 
 ## Syntax
@@ -27,12 +26,10 @@ y-label Y Axis Label
 no-labels
 size-label Size Legend Label
 
-// label: x, y
-Point Name: x, y
+Point Name x y
 
 // or with size (bubble chart)
-// label: x, y, size
-Point Name: x, y, size
+Point Name x y size
 ```
 
 ## Metadata Keys
@@ -52,12 +49,12 @@ Each data line provides X and Y values, with an optional third value for bubble
 
 ```
 // 2D scatter
-Point A: 12, 1800
-Point B: 8, 1200
+Point A 12 1800
+Point B 8 1200
 
 // 3D bubble
-Point A: 85, 90, 80
-Point B: 45, 55, 35
+Point A 85 90 80
+Point B 45 55 35
 ```
 
 ## Category Groups
@@ -66,11 +63,11 @@ Use `[Category Name](color)` headers to group points into colored categories:
 
 ```
 [English Pirates](red)
-Blackbeard: 85, 90, 80
-Calico Jack: 45, 55, 35
+Blackbeard 85 90 80
+Calico Jack 45 55 35
 
 [French Buccaneers](blue)
-L'Olonnais: 70, 80, 60
+L'Olonnais 70 80 60
 ```
 
 ## Variants
@@ -84,11 +81,11 @@ scatter Pirate Fleets of the Caribbean
 size-label Crew
 
 [English Pirates](red)
-Blackbeard: 85, 90, 80
-Calico Jack: 45, 55, 35
-Anne Bonny: 50, 70, 30
+Blackbeard 85 90 80
+Calico Jack 45 55 35
+Anne Bonny 50 70 30
 
 [French Buccaneers](blue)
-L'Olonnais: 70, 80, 60
-Pierre le Grand: 30, 45, 25
+L'Olonnais 70 80 60
+Pierre le Grand 30 45 25
 ```

package/docs/guide/index.md

@@ -24,9 +24,9 @@ Every diagram starts with the chart type on the first line, followed by your dat
 ```
 bar Q1 Sales
 
-Jan: 42
-Feb: 58
-Mar: 71
+Jan 42
+Feb 58
+Mar 71
 ```
 
 ## The Diagrammo Ecosystem

package/docs/guide/registry.json

@@ -19,12 +19,15 @@
     { "slug": "chart-er", "title": "Entity Relationship", "group": "software", "file": "chart-er.md" },
     { "slug": "chart-flowchart", "title": "Flowchart", "group": "software", "file": "chart-flowchart.md" },
     { "slug": "chart-infra", "title": "Infrastructure", "group": "software", "file": "chart-infra.md" },
+    { "slug": "chart-mindmap", "title": "Mind Map", "group": "software", "file": "chart-mindmap.md" },
     { "slug": "chart-sequence", "title": "Sequence Diagram", "group": "software", "file": "chart-sequence.md" },
     { "slug": "chart-sitemap", "title": "Sitemap", "group": "software", "file": "chart-sitemap.md" },
     { "slug": "chart-state", "title": "State Diagram", "group": "software", "file": "chart-state.md" },
+    { "slug": "chart-wireframe", "title": "Wireframe", "group": "software", "file": "chart-wireframe.md" },
 
     { "slug": "chart-area", "title": "Area Chart", "group": "data", "file": "chart-area.md" },
     { "slug": "chart-bar", "title": "Bar Chart", "group": "data", "file": "chart-bar.md" },
+    { "slug": "chart-cycle", "title": "Cycle Diagram", "group": "data", "file": "chart-cycle.md" },
     { "slug": "chart-chord", "title": "Chord Diagram", "group": "data", "file": "chart-chord.md" },
     { "slug": "chart-doughnut", "title": "Doughnut Chart", "group": "data", "file": "chart-doughnut.md" },
     { "slug": "chart-function", "title": "Function Plot", "group": "data", "file": "chart-function.md" },
@@ -38,8 +41,10 @@
     { "slug": "chart-slope", "title": "Slope Chart", "group": "data", "file": "chart-slope.md" },
     { "slug": "chart-bar-stacked", "title": "Stacked Bar Chart", "group": "data", "file": "chart-bar-stacked.md" },
 
+    { "slug": "chart-journey-map", "title": "Journey Map", "group": "business", "file": "chart-journey-map.md" },
     { "slug": "chart-funnel", "title": "Funnel Chart", "group": "business", "file": "chart-funnel.md" },
     { "slug": "chart-org", "title": "Org Chart", "group": "business", "file": "chart-org.md" },
+    { "slug": "chart-pyramid", "title": "Pyramid Diagram", "group": "business", "file": "chart-pyramid.md" },
     { "slug": "chart-quadrant", "title": "Quadrant Chart", "group": "business", "file": "chart-quadrant.md" },
     { "slug": "chart-sankey", "title": "Sankey Diagram", "group": "business", "file": "chart-sankey.md" },
     { "slug": "chart-tech-radar", "title": "Technology Radar", "group": "business", "file": "chart-tech-radar.md" },

package/docs/language-reference.md

@@ -768,6 +768,8 @@ kanban [Title]
 
 ### 10.2 Columns
 
+Columns represent workflow stages and must flow left-to-right from least-done to most-done (e.g., Backlog → In Progress → Done). Every column should be a stage that cards pass through. Don't create columns for non-workflow concepts like gates, criteria, or definitions of done — use a tag instead (e.g., `type: Gate`).
+
 ```
 [Column Name]
 [Column Name](color) | wip: 3
@@ -1134,29 +1136,51 @@ marker
 
 ## 15. Data Charts
 
+### Conventions shared across all data charts
+
+Every section under §15 follows the same two rules.
+
+**Rule A — data rows are space-separated.** Commas between values are tolerated for back-compat but not idiomatic. Thousands-separator commas *inside a single number* (`3,984,078.65`) are always supported.
+
+```
+Q1 400 700 300 500     ✅  preferred
+Q1 400, 700, 300, 500  ⚠  tolerated; use spaces
+```
+
+**Rule B — list-of-labelled-items directives (e.g. `series`, `columns`) prefer the indented one-per-line form.** Short one-line forms are tolerated for ≤3 items with no colour annotations or spaces.
+
+```
+series                            ✅  preferred
+  Cloud Platform (blue)
+  Legacy Suite (red)
+  Mobile App (green)
+
+series Cloud (blue), Legacy (red) ⚠  tolerated; prefer the block
+```
+
+Parsers accept either form. The rules above are authoring guidance.
+
 ### 15.1 Simple Charts (bar, line, pie, doughnut, area, polar-area, radar, bar-stacked)
 
 **Declaration:** `bar [Title]`, `line [Title]`, etc.
 
-**Series:**
+**Series** — follows Rule B (prefer the indented block):
 ```
-series Name1 Name2
 series
-  Name1
-  Name2(color)
+  Cloud Platform (blue)
+  Legacy Suite (red)
 ```
 
-Commas between series names are optional.
+Short one-line form is tolerated: `series Revenue` or `series A B`.
 
-**Data rows (space-separated, NO colon):**
+**Data rows** — follows Rule A:
 ```
 Label 100
 Label 100 200 300
 Label(color) 100
+Q1 400 700 300 500
 ```
 
-Commas between values are optional. Thousands commas are supported (`3,984,078.65` is a valid number).
-
 **Options (space-separated, NO colon):**
 ```
 title My Chart
@@ -1182,14 +1206,12 @@ era Day 1 -> Day 3 Rough Seas (red)
 
 ### 15.2 Scatter / Bubble Charts
 
-**Data rows (space-separated, NO colon):**
+**Data rows** — follows §15 Rule A (space-separated):
 ```
 Name x y
 Name x y size
 ```
 
-Commas between values are optional. Thousands commas supported.
-
 **Categories:**
 ```
 [Caribbean](red)
@@ -1208,20 +1230,21 @@ Labels are on by default. Use `no-labels` to hide point names.
 
 ### 15.3 Heatmap
 
-**Columns:**
+**Columns** — follows §15 Rule B (prefer the indented block for multiple columns):
 ```
-columns Jan Feb Mar
+columns
+  Jan
+  Feb
+  Mar
 ```
 
-Commas between column names are optional.
+Short one-line form is tolerated: `columns Jan Feb Mar`.
 
-**Data rows (space-separated, NO colon):**
+**Data rows** — follows §15 Rule A:
 ```
 RowLabel 5 4 3
 ```
 
-Commas between values are optional. Thousands commas supported.
-
 ### 15.4 Function Charts (Colon REQUIRED)
 
 ```
@@ -1254,7 +1277,7 @@ Source -> Target 3500
 Source -- Target 2000
 ```
 
-`->` = directed, `--` = undirected. Thousands commas supported in values.
+`->` = directed, `--` = undirected. Values follow §15 Rule A.
 
 ### 15.6 Chord Charts
 
@@ -1263,19 +1286,17 @@ Blackbeard -- Bonnet 150        // undirected
 Roberts -> Rackham 20           // directed
 ```
 
-Thousands commas supported in values.
+Values follow §15 Rule A.
 
 ### 15.7 Funnel Charts
 
-**Data rows (space-separated, NO colon):**
+**Data rows** — follows §15 Rule A (space-separated):
 ```
 Visits 1200
 Signups 800
 Purchases 200
 ```
 
-Thousands commas supported.
-
 ---
 
 ## 16. Visualizations
@@ -1297,7 +1318,7 @@ Roberts 12 52
     Before COVID
     After COVID
   ```
-- Data rows: `Label value1 value2` — space-separated, no colons, no commas between values
+- Data rows: `Label value1 value2` — follows §15 Rule A (space-separated; commas between values tolerated for back-compat but not idiomatic)
 - Thousands commas within values supported (e.g., `1,000`)
 - Color annotations: `Label (color) value1 value2`
 - Minimum 2 periods required
@@ -1364,9 +1385,9 @@ Quartermaster 0.9 0.95
 Navigator 0.85 0.8
 ```
 
-- Axis labels: `x-label Low, High` — comma-separated
+- Axis labels: `x-label Low, High` — comma-separated (low/high pair, not a data row; comma is the delimiter here by design)
 - Position labels: `top-right Label` — space-separated
-- Data points: `Label x y` or `Label x, y` — comma or space between coordinates
+- Data points: `Label x y` — follows §15 Rule A (space-separated; `Label x, y` tolerated for back-compat)
 
 ---
 
@@ -1570,7 +1591,68 @@ wireframe Login Page
 
 ---
 
-## 19. Colon Usage Summary
+## 19. Pyramid Diagrams
+
+Hierarchical pyramid visualization with stacked layers, descriptions, and optional per-layer color. Source order reads apex-first (top of file = top of pyramid).
+
+### Declaration
+
+```
+pyramid [Title]
+
+LayerLabel
+LayerLabel | color: blue
+LayerLabel | color: green
+  Indented description
+```
+
+The first line declares the chart type and an optional title. Each non-indented, non-directive line declares one layer. At least two layers are required.
+
+### Example
+
+```
+pyramid Maslow's Hierarchy
+
+Self-Actualization | color: purple
+  Morality, creativity, acceptance of facts.
+
+Esteem | color: blue
+  Respect, recognition, confidence.
+
+Love & Belonging | color: green
+  Friendship, intimacy, family.
+
+Safety | color: yellow
+  Security, employment, health.
+
+Physiological | color: orange
+  Food, water, warmth, rest.
+```
+
+### Layer Pipe Metadata
+
+| Key | Type | Default | Description |
+|-----|------|---------|-------------|
+| `color` | palette name | auto | Layer color |
+| `description` | string | — | One-liner description |
+
+### Descriptions
+
+Indented lines under a layer are description text. Markdown inline formatting (`**bold**`, `*italic*`, `` `code` ``, `[links](url)`) is supported. Bullets written as `- item` render as `• item`.
+
+### Directives
+
+| Directive | Effect |
+|-----------|--------|
+| `inverted` | Flip apex to the bottom (funnel orientation). Source order is preserved — the first layer is always the visual top. |
+
+### Overflow Handling
+
+When descriptions don't fit a layer's band the renderer wraps at the column edge, truncates with `…`, auto-alternates descriptions left ↔ right when one column can't hold them, and (in-app) reveals the full description on highlight while hiding siblings.
+
+---
+
+## 20. Colon Usage Summary
 
 ### Constructs Where Colons Are REQUIRED