canvas

1# Canvas
2 
3Treat a canvas as a vault-scoped JSON Canvas document. Keep reads read-only and
4route every requested mutation through one recoverable transaction.
5 
6Resolve the installed product root from this skill's own location, not from the
7vault or current working directory:
8 
9```bash
10PRODUCT_ROOT=/absolute/path/to/installed/claude-obsidian
11CORE="$PRODUCT_ROOT/scripts/claude-obsidian.py"
12test -f "$CORE"
13```
14 
15Every `../wiki/references/` link in this file resolves the same way, relative
16to this skill's own directory under `$PRODUCT_ROOT`, never relative to the
17selected vault's `wiki/` directory.
18 
19## Choose the syntax source
20 
21Prefer a separately installed `kepano/obsidian-skills` `json-canvas` skill for
22format details. Otherwise read [references/canvas-spec.md](references/canvas-spec.md).
23The open standard is [JSON Canvas 1.0](https://jsoncanvas.org/spec/1.0/).
24 
25Use this skill for vault workflow and transaction safety even when an upstream
26syntax skill is available.
27 
28## Scope
29 
30- Resolve the user vault before reading. Never derive it from plugin files.
31- Store boards under `wiki/canvases/`; use `wiki/canvases/main.canvas` only as
32  the default when the user did not name a board.
33- Treat `wiki/canvases/_index.md` as an optional catalog. Add a new board to it
34  in the same transaction when a catalog exists. Node or edge edits inside an
35  existing board do not require a catalog change.
36- The transaction engine supports file creation and replacement only. A board
37…