Excalidraw — draw out the patterns

The spark

Can we add Excalidraw support to brain so that you could actually like draw out some diagrams for certain patterns and things.

What I think you're reaching for

A visual channel for the vault — somewhere a pattern can be drawn rather than prosed. Causal chains, system loops, and cross-domain analogies are spatial things; forcing them into linear markdown loses the shape. The deeper reach (worth naming): not just you sketching, but Claude generating an Excalidraw diagram from a mechanism or concept page, so a chain you've already written in prose gets a first-class visual companion automatically.

Connections (held loosely)

The Obsidian Excalidraw plugin is already installed in this vault (.obsidian/plugins/obsidian-excalidraw-plugin) — so hand-drawing is already one click away. That reframes the spark: the unmet need isn't "add Excalidraw," it's "make brain use it" — Claude drafting .excalidraw files, and the web explorer rendering them.
RESEARCH — causal chains (wiki/mechanisms/, the A → B → C schema) are the highest-yield thing to diagram; a mechanism page is practically a diagram written as text. The auto-generated mechanism graph in apps/web is the computed view; Excalidraw would be the freeform, hand-curated complement (annotate, cluster, draw the analogy the graph can't infer).
2026-06-07-brain-as-add-capture-layer — loosely: spatial/visual thinking is often more ADHD-native than linear text. A draw-it surface fits the cognitive-prosthetic framing of that spark.

Where this could go

Claude-drafted diagrams: a skill (or extract-mechanisms extension) that emits an .excalidraw alongside a mechanism page — the chain rendered as boxes + arrows, each step labeled with its evidence status. The graph you can read, not just traverse.
Pattern library: a vault/_meta/ or per-context home for recurring shapes (forcing-function → beneficiary, second-order supplier, reflexive loop) as reusable Excalidraw templates — the visual vocabulary behind the prose patterns.
Web explorer rendering: apps/web reads .excalidraw JSON and renders it read-only next to the page, so diagrams aren't trapped in Obsidian.

A possible next move

Marinate — but the sharpest first cut is small: try hand-drawing one existing mechanism chain in the already-installed plugin and see if the visual earns its keep before building any Claude-generates-it machinery. If it does, that's a clean /thread-create brain-visualization or a _meta/QUEUE.md build-task.