wiki

1# Wiki orchestration
2 
3Treat the installed product as code and the selected user vault as data. Never use
4the plugin/product root as a vault, even when the current directory happens to be
5the product checkout.
6 
7Resolve the portable core from this skill's installation and invoke it by absolute
8path:
9 
10```bash
11CORE=/absolute/product/root/scripts/claude-obsidian.py
12python3 "$CORE" --help
13```
14 
15Resolve a vault in this order: explicit `--vault`,
16`CLAUDE_OBSIDIAN_VAULT`, the nearest `.claude-obsidian.json`, then an
17unambiguous initialized vault at or above the current directory. Fail closed when
18selection is missing or ambiguous.
19 
20Baseline setup requires no network egress. Do not fetch templates, plugins, or
21remote content unless the user separately approves the destinations and budget.
22 
23## Set up a vault
24 
25Use the deterministic setup commands. Both are dry-run by default.
26 
27For a new, separate vault:
28 
29```bash
30python3 "$CORE" init /absolute/path/to/vault \
31  --generated-at <ISO-UTC> --operation-id init-reviewed
32python3 "$CORE" init /absolute/path/to/vault \
33  --generated-at <ISO-UTC> --operation-id init-reviewed \
34  --approved-plan-sha256 <reviewed-sha256> --apply
35```
36 
37For an existing Obsidian vault:
38 
39```bash
40python3 "$CORE" adopt /absolute/path/to/vault \
41  --generated-at <ISO-UTC> --operation-id adopt-reviewed
42python3 "$CORE" adopt /absolute/path/to/vault \
43  --generated-at <ISO-UTC> --operation-id adopt-reviewed \
44  --approved-plan-sha256 <reviewed-sha256> --apply
45```
46…