ost-render

# 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 rathe...