Bootstrap the garden vault from connected data sources. Surveys what's available, proposes a plan tailored to the user's context, asks for confirmation, then executes. Opt-in and user-invoked only — never runs unattended. Two modes, both interactive: init (first-time pull) and refresh (top-up since last run).
Capture a thought, decision, learning, or fact into the garden vault inbox. Use ONLY when the user explicitly asks: "capture X", "remember that X", "for the garden Y", "save this", etc. Do not capture proactively — the user wants to approve what lands in the vault. Writes to /garden/inbox/: the gardener will file it…
Search the garden vault for notes relevant to a query and surface them with citations. Use when the user asks about past decisions ("what did I decide about X"), past work ("what's the state of Y"), or anything where the vault might already hold the answer. Greps + reads files under /garden/.
Extract or refresh the user's writing voice profile from their actual Slack messages. Pulls sent messages, synthesizes style patterns, anchors with short redacted examples, writes meta/voice.md. Use when the user says "init voice", "refresh voice", "extract my voice", "build voice profile", or during initial vault…
Process the garden vault. Files inbox captures into atomic notes, adds wiki-links, dedupes, updates MOCs, and commits. Run on a schedule (cron or routine), not by hand. Reads /garden/meta/gardener-rules.md for heuristics.