git:20261001.cb52c01 to git:20261001.d0b116b

- description: Render `.claude/diamonds/active.yml` as a state diagram. Read-only. Default format Mermaid stateDiagram-v2. Recommended at the end of `/mycelium:diamond-assess` so every assessment closes with a visual state-of-play. See `${CLAUDE_PLUGIN_ROOT}/engine/render-conventions.md` for shared render fleet conventions.

- instruction_budget: "45"

- framework_dependency_note: "Reads .claude/diamonds/active.yml and ${CLAUDE_PLUGIN_ROOT}/engine/diamond-rules.md. Standalone use will fail without active.yml present."

- Read-only render of `.claude/diamonds/active.yml` as a state diagram. First specialist of the render fleet. Other specialists (`/mycelium:ost-render`, `/mycelium:cycle-render`) and the dispatcher (`/mycelium:render`) ship in subsequent patches.

- - To advance a diamond (Discover → Define etc.) → `/mycelium:diamond-progress`.

- | `${CLAUDE_PLUGIN_ROOT}/engine/diamond-rules.md` | none (canonical phase list) | n/a |

- `diamonds/active.yml` is phase-state shape: scale (L0–L5), phase (Discover/Define/Develop/Deliver), confidence value, gate-history timestamps. No contributor names, no participant fields, no identifier-bearing prose. Zero identifier exposure as of v0.40.0.

- **Future-schema-change caveat**: if a future schema adds an identifier field (e.g., per-team diamond ownership for multi-team Mycelium per the deferred Team Topologies adoption), this declaration becomes false. The skill must then be re-declared `YES` or `MIXED`, consult the registry per `engine/render-conventions.md#hard-rule-consent--privacy-gate`, and ship redaction fixtures. The schema-versioning rule surfaces the schema_version mismatch at runtime as a forcing function for the re-audit.

- Render of `diamonds/active.yml` with no identifier content present:

-

- L0 Purpose: [Discover]→[Define]→[Develop*]→[Deliver]

- conf=0.612

- Not applicable. Check 43 forbids redaction fixtures on NONE-declared specialists (avoids the "declares NONE but acts YES" drift). Other fixtures (see § Test fixtures below) exercise actual behavior.

-

- ## Preflight: Read source

-

- 1. Read `.claude/diamonds/active.yml` with the Read tool. **Full read** (state diagram needs the full structure; `limit:1` not appropriate here).

- 2. Read `${CLAUDE_PLUGIN_ROOT}/engine/diamond-rules.md` to get the canonical phase list per scale + the four canonical phase-transition gate names.

- 3. If `--as-of <date>` was specified, also read `.claude/harness/decision-log.md` to walk backward to that date.

- 4. Note the source's canvas-state timestamp per `engine/render-conventions.md#canvas-state-timestamp-resolution`: `_meta.last_validated` if present, else top-level `last_updated:`.

- | `--format` | `mermaid` | `mermaid` \| `ascii` \| `json` | Output format. `markdown-table` and `markdown-list` are NOT supported (state diagrams don't map cleanly); fail loud per `engine/render-conventions.md#format-support-negotiation-global-rule`. |

- | `--scale` | `active` | `L0` \| `L1` \| `L2` \| `L3` \| `L4` \| `L5` \| `active` \| `all` | Which diamond(s) to render. `active` = the open diamonds: those in `active_diamonds` whose `state` is not closed (killed, parked, archived, retargeted) and that have not recorded `close`. |

- | `--theme` | `base` | `base` \| `dark` | Theme. `dark` is the WCAG-by-construction opt-in per `engine/render-conventions.md#wcag-aa-theme-convention`. |

- | `--show-gates` | `true` | bool | Annotate transitions with phase-transition gate names + theory-gate status block. |

- | `--show-confidence` | `true` | bool | Annotate phases with confidence values. |

- | `--show-history` | `false` | bool | Include `gate_history` entries as transition timestamps. |

- | `--as-of` | `null` | ISO date | Render diamond state as-of this date (walk decision-log backward). Fail loud if date precedes the first decision-log entry mentioning the diamond. |

- ### Step 1: Resolve scale

-

- - `--scale active` → enumerate the open diamonds: those in `active_diamonds` whose `state` is not closed (killed, parked, archived, retargeted) and that have not recorded `close` (v0.307.1: a diamond with no `phase` label is still open). If empty, emit `No active diamond — run /mycelium:start` placeholder + canonical disclaimer + early return.

- - `--scale L<N>` → render only that scale; fail loud if scale not present.

- - `--scale all` → render every diamond regardless of phase.

-

- ### Step 2: Build per-diamond state

-

- For each diamond to render:

- - States = the four canonical phases (Discover, Define, Develop, Deliver). Canonicalize on emit: if canvas uses lowercase, render as canonical case. Surface lowercase-canvas as a `canvas-health` follow-up note.

- - Current state = where the diamond is, read from its `decisions` (v0.305.0: `python3

- "${CLAUDE_PLUGIN_ROOT}/scripts/scale_locks.py"`'s `phase_of`; develop needs both

- `start_experiment` and `commit_to_build`); a diamond with no decisions is in Discover, whatever

- its `phase` label says (v0.306.0).

- - Completed states = phases before current per linear order.

- - Future states = phases after current.

- - **Transition labels (phase-transition gates)** if `--show-gates=true`:

- - Discover → Define : `evidence`

- - Define → Develop : `trio-coverage`

- - Develop → Deliver : `DoD`

- - Deliver → [*] : `launch`

- - **Theory gate status annotation** if `--show-gates=true` AND `theory_gates_status` field present: emit `note right of <ID>` block summarizing pass/fail/pass-with-risk per gate (evidence/cynefin/bias/bvssh/corrections/four_risks/jtbd).

- - Phase annotation = `confidence` field from active.yml (NOT `confidence_threshold`) if `--show-confidence=true`. Display as `conf=<value>`.

-

- ### Step 2a: Spawn-relationship arrows (multi-diamond renders)

-

- When rendering multiple diamonds and a child's `parent` is set (canonical since v0.245.0; fall back to the deprecated `parent_id`, which this step read while `/launch-tier` wrote `parent`):

- - Emit between-state arrow after per-diamond blocks: `<parent> --> <child_id> : spawned <YYYY-MM-DD>`.

- - Date from child's `created_at` field.

- - If both `parent` and `parent_id` are null OR `created_at` missing, skip the arrow.

-

- ### Step 3: Staleness check

-

- Per `engine/render-conventions.md#staleness-check-distinction`: compare canvas-state timestamp against the most recent decision-log entry mentioning the diamond's scale. If decision-log activity is newer than canvas timestamp, prepend the staleness warning.

-

- ### Step 4: Emit by format

-

- **Format `mermaid` (default)** — Mermaid stateDiagram-v2 with WCAG AA theme.

-

- Use **frontmatter config syntax** per `engine/render-conventions.md#mermaid-frontmatter-syntax-preferred`. `--theme dark` opt-in switches to Mermaid's built-in dark theme.

-

- ```mermaid

- ---

- config:

- theme: base

- themeVariables:

- primaryColor: '#ffffff'

- primaryTextColor: '#1a1a1a'

- primaryBorderColor: '#333333'

- lineColor: '#1a1a1a'

- ---

- stateDiagram-v2

- classDef current fill:#fff9c4,stroke:#3e2723,color:#3e2723,stroke-width:3px

- state "L0 Purpose" as L0 {

- [*] --> L0_Discover

- L0_Discover --> L0_Define : evidence

- L0_Define --> L0_Develop : trio-coverage

- L0_Develop --> L0_Deliver : DoD

- L0_Deliver --> [*] : launch

- L0_Discover : done

- L0_Define : done

- L0_Develop : done

- L0_Deliver : current conf=0.612

- class L0_Deliver current

- }

- ```

-

- State IDs in spawn arrows MUST match the `as <ID>` declarations (see Counter-Argument item 3). `classDef current` is required whenever `class ... current` is used (see Counter-Argument item 4). Phase-state IDs use the scale prefix (L0_Discover, L1_Discover etc.) to avoid collision in multi-diamond renders.

-

- **Format `ascii`** — terminal-friendly:

-

- ```

- L0 Purpose

- ═══════════════════════════════════════════════

- [Discover]─evidence─▶[Define]─trio─▶[Develop*]─DoD─▶[Deliver]

- done done current upcoming

- conf=0.612

- * = current phase

- When `--scale all` or `--scale active` with multiple diamonds, stack diamond blocks vertically with `═` rule separators.

-

- **Format `json`** — external-system integration:

- ```json

- {

- "schema_version": 1,

- "render": "diamond",

- "source": ".claude/diamonds/active.yml",

- "source_last_validated": "<YYYY-MM-DD>",

- "diamonds": [

- {

- "scale": "L0",

- "name": "Purpose",

- "current_phase": "Develop",

- "confidence": 0.612,

- "phases": [

- {"name": "Discover", "status": "done"},

- {"name": "Define", "status": "done"},

- {"name": "Develop", "status": "current"},

- {"name": "Deliver", "status": "upcoming"}

- ],

- "gates": [

- {"from": "Discover", "to": "Define", "name": "evidence"},

- {"from": "Define", "to": "Develop", "name": "trio-coverage"},

- {"from": "Develop", "to": "Deliver", "name": "DoD"}

- ]

- }

- ],

- "dropped_fields": ["gate_history", "decision_log_refs", "phase_completion_notes"]

- }

- ```

- ### Step 4b: Validate the emitted Mermaid (MANDATORY for `mermaid` format)

- Pipe the block you just emitted through the static validator before showing it:

- printf '%s' "$DIAGRAM" | python3 ${CLAUDE_PLUGIN_ROOT}/scripts/validate_mermaid.py -

- It checks the two things you cannot check by eye: **state-id consistency** (F11 — every transition endpoint and `class` target references a declared ID, a mismatch being a render-time parse error invisible in the raw syntax) and **WCAG AA contrast** (F13 — every `themeVariables` foreground/background pair ≥ 4.5:1, which is pure math). Add `--cli` to also shell out to `mmdc` for a full parse when the binary is present (fail-open when absent).

-

- Exit 1 means at least one FAIL: **fix the diagram and re-validate before emitting.** Do not show the user a diagram that failed this check.

-

- What remains genuinely operator-side is visual layout and communicative quality — that still needs a human eye, which is why the Step 5 disclaimer stays. This step covers only what is mechanically decidable. (Wired 2026-07-26: the validator shipped with a coverage proof but no render skill invoked it, so both blind-spots it "closed" were still open in practice.)

- ### Step 5: Append disclaimers

- - **Lossy-on-export** (mermaid + ascii only): list dropped fields. For diamond-render: `gate_history`, `last_progressed_by`, `decision_log_refs`, prose `phase_completion_notes`.

- 1. **Read-only.** Never modify active.yml, decision-log, or any state.

- 2. **Phase name spellings** must match `engine/diamond-rules.md`. Do not abbreviate, paraphrase, or invent variants.

- 3. **Empty-case behavior**: if active.yml is null/empty or has no open diamonds, emit `No active diamond — run /mycelium:start` placeholder + canonical disclaimer. Do NOT error.

- 4. **Format-unsupported behavior**: if `--format markdown-table` or `--format markdown-list` requested, fail loud per `engine/render-conventions.md#format-support-negotiation-global-rule`. Do NOT silently downgrade.

- 5. **`--as-of` historical mode**: if the date precedes the first decision-log entry mentioning the diamond, fail loud with `no recorded state at that date`. Do NOT extrapolate.

- 6. **Never invent** gates, phases, or confidence values not in the canvas or `engine/diamond-rules.md`.

- Before emitting:

- 1. *"Is this render's current-phase marker the truth, or has the canvas been edited since the last `/mycelium:diamond-progress` walk?"* The staleness check (Step 3) is the mechanical answer.

- 2. *"Am I rendering a single diamond when the project is in fractal-of-diamonds mode and all six are load-bearing?"* If `--scale active` and only one diamond is open BUT the decision log mentions moves on others, surface: `Other diamonds present in active.yml (<list>) are closed or not open — consider --scale all to render the full state.`

- 3. *"Are all state IDs referenced in transitions and class lines actually defined?"* Walk every `<src> --> <dst>` arrow and `class <X> <name>` line; verify both sides are either a defined `state ... as <ID>` OR a Mermaid built-in (`[*]`). Mismatch = parse error at render time.

- 4. *"Is `classDef current` defined if any `class ... current` line is emitted?"* Without `classDef`, the class line is a silent no-op. Emit `classDef current fill:#fff9c4,stroke:#3e2723,color:#3e2723,stroke-width:3px` once at the top when any `class ... current` follows.

- - Does NOT advance the diamond. That's `/mycelium:diamond-progress`.

- - Does NOT explain WHY the diamond is in its phase. That lives in decision-log and the diamond-assess output.

- - Does NOT generate the diamond. That's `/mycelium:start`.

-

- This skill is a **read-only snapshot emitter**.

- `/mycelium:diamond-assess` ends its Step 5 (decision output) with:

- > _Visualize the assessed state: run `/mycelium:diamond-render` (defaults

- > to L0 active scale). The canvas remains source of truth; this render

- > is a snapshot._

- ## Test fixtures (G-V12 / Check 37)

- - `tests/bash/fixtures/diamond-render/empty-active.yml` → assert placeholder

- - `tests/bash/fixtures/diamond-render/single-L0.yml` → assert mermaid stateDiagram-v2 with `class L0_Develop current`

- - `tests/bash/fixtures/diamond-render/multi-scale.yml` → assert two state blocks emitted with spawn arrow

- - `tests/bash/fixtures/diamond-render/stale-canvas.yml` → assert staleness warning in output

- - `tests/bash/fixtures/diamond-render/unsupported-format.yml` → assert fail-loud message

- - `tests/bash/fixtures/diamond-render/as-of-historical.yml` → assert decision-log walk

- - `tests/bash/fixtures/diamond-render/as-of-before-history.yml` → assert fail-loud on out-of-range date

- - Mycelium diamond engine (Discover/Define/Develop/Deliver fractal at six scales L0–L5)

- - Argyris triple-loop (the diamond renders the loop currently in motion)

- - Hick's Law (single recommended format default; explicit fail-loud on unsupported)