/ost-render

name: ost-render
description: Render `.claude/canvas/opportunities.yml` as a diagram or structured list. Read-only. Default format Mermaid mindmap. Consults the attribution registry per `${CLAUDE_PLUGIN_ROOT}/engine/render-conventions.md` consent + privacy gate. Second specialist in the render fleet.
metadata:
  instruction_budget: "60"
  framework_dependency: "mycelium"
  framework_dependency_note: "Reads .claude/canvas/opportunities.yml + attribution registry (env var $MYCELIUM_ATTRIBUTION_REGISTRY preferred; .claude/memory/attribution-registry.yml fallback). Standalone use will fail without opportunities.yml present."
  identifier_exposure: "YES"

OST Render

Read-only render of `.claude/canvas/opportunities.yml` as a diagram or structured list. Second specialist in the render fleet (after `/mycelium:diamond-render`). See `${CLAUDE_PLUGIN_ROOT}/engine/render-conventions.md` for shared conventions.

When NOT to use

• To BUILD or update the OST from research data → `/mycelium:ost-builder`. This skill is read-only.
• For cross-cutting opportunity→solution→cycle traceability view → dispatcher's `/mycelium:render --view traceability` (deferred to Phase 4a–4d research-first methodology per architecture draft §10.2).
• For ICE scoring of solutions → `/mycelium:ice-score`.

Identifier exposure

**Declared**: YES

Scope (canvas surfaces touched)

| Canvas file | Identifier-bearing fields | Frequency | |---|---|---| | `.claude/canvas/opportunities.yml` | `evidence_sources` (URL-or-name strings); `notes` prose | low (~1 in 10 cites a named individual rather than a URL) | | `$MYCELIUM_ATTRIBUTION_REGISTRY` env var (canonical) or `.claude/memory/attribution-registry.yml` (fallback) | `people:` block with `name`+`consent`+`note` per entry | read-only consultation; never rendered |

Per `${CLAUDE_PLUGIN_ROOT}/engine/render-conventions.md#hard-rule-consent--privacy-gate`. Registry lives in roadmap-private memory by design — upstream Mycelium repo is public; registry contents must not ship there.

Rationale

OST shape is user-need-shaped (abstract opportunities and solutions), so identifier exposure is incidental rather than intrinsic. Identifier classes that can appear: cohort testers, peer practitioners, named external sources. All three go through the consent gate; external sources are typically `public_ok` already, but registry consultation is non-skippable to avoid drift.

Anon-label convention

Per `engine/render-conventions.md#anon-label-convention`:

• Cohort tester → `cohort-tester-N`
• Peer practitioner → `peer-practitioner-N`
• Unknown identifier class → `participant-N`

Numbering resets per render; emit an in-render mapping footnote when redaction occurred so the operator can audit which anon label maps to which registry entry.

Consent value semantics

Per `engine/render-conventions.md#consent-value-semantics`:

| Value | Render behavior | |---|---| | `public_ok` | Render literal. Append carve-out footnote pointer if entry has non-empty `note:`. | | `generic_only` | Redact to anon-label. Queue anon-mapping footnote. | | `unknown` | Treat as `generic_only` per registry README. | | (not in registry) | Fail loud unless `--no-identifiers=true`. |

Worked examples

**public_ok → literal**: `evidence_sources: ["Drew Hoskins LinkedIn 2026-05-11"]`, registry entry `{name: "Drew", consent: public_ok, note: "..."}` → renders as `Drew Hoskins LinkedIn 2026-05-11` + carve-out footnote pointer.

**generic_only → anon-label**: `evidence_sources: ["Daniel Bentes install report"]`, registry entry `{name: "Daniel", consent: generic_only, ...}` → renders as `peer-practitioner-1 install report` + anon-mapping footnote.

**Already-anon canvas label → preserve**: `evidence_sources: ["cohort-tester-3 session 2 transcript"]`, canvas already anon-labeled → renders as `cohort-tester-3 session 2 transcript` (preserve canvas-side anonymization; do not look up).

**Identifier absent from registry → fail loud**: `evidence_sources: ["Random Name DM 2026-06-05"]`, no entry → **the WHOLE render is blocked — emit NO artifact** (not a partial mindmap with the offending entry redacted or omitted), and give the fail-loud message with three fix options (add to registry, re-run with `--no-identifiers`, edit canvas). Clarified v0.56.0 after a dogfood run read this line as per-entry and rendered around the unregistered source: an unresolved consent state means the render's exposure declaration cannot be made honestly, so nothing ships until the user resolves it. Naming the offending source in the owner-facing explanation is fine (project-private context); the artifact is what must not exist.

Fixture pointer

• `tests/bash/fixtures/ost-render/redaction-public-ok-literal.yml`
• `tests/bash/fixtures/ost-render/redaction-generic-only-anon.yml`
• `tests/bash/fixtures/ost-render/redaction-unknown-treated-as-generic.yml`
• `tests/bash/fixtures/ost-render/redaction-no-registry-entry-fail-loud.yml`
• `tests/bash/fixtures/ost-render/redaction-carve-out-note-footnote.yml`

Preflight: Read sources

1. Read `.claude/canvas/opportunities.yml` with the Read tool. Full read for emit; not `limit:1`. 2. Read the attribution registry per path-resolution order in `engine/render-conventions.md#registry-path-resolution`: `$MYCELIUM_ATTRIBUTION_REGISTRY` env var first; fall back to `.claude/memory/attribution-registry.yml`. Registry root key is `people:`; each entry has `name`, `consent`, optional `note`. If registry absent, surface `⚠ no attribution-registry — consent-redaction not enforceable; treat output as roadmap-internal` warning in the render header. **For `--audience external`, an absent registry BLOCKS the render and emits no artifact** (v0.173.0) — same outcome as an unregistered identifier, because an absent registry is that same unresolved-consent condition applied to every identifier at once. The warning-and-emit path is for `founder`/`cohort` only. 3. Note the source's canvas-state timestamp