kblisted

# Knowledge Base (recall) When configured, recall provides a persistent markdown knowledge base at `~/.recall/`. Knowledge persists across sessions, repos, and machines via git sync. Searchable with FTS5 full-text search with BM25 ranking. ## Workflow 1. **Search first** to avoid duplicates: `search_notes(query="topic")` 2. **Read existing** if a related note exists: `read_note(path="repos/ai-rules.md")` 3. **Write or update**: `write_note(path="repos/ai-rules.md", content="---\ntitle: ...\ntype: note\nupdated: 2026-04-30\ntags: []\n---\n\n# ...")` 4. **Connect related notes** using `[[wikilinks]]` in the Relations section ## Directory Guide | Directory | Use for | Example titles | |-----------|---------|----------------| | `repos/` | Per-repo commands, gotchas, patterns | "ai-rules", "goosed-slackbot" | | `patterns/` | Reusable technical knowledge | "uv-run-not-direct-invocation" | | `decisions/` | ADRs -- why something was chosen | "raw-sql-over-sqlalchemy" | | `preferences/` | User working style, conventions | "test-docstring-conventions" | | `references/` | External knowledge, company info | "block-ci-cd-pipeline" | | `references/block/` | Block/Square-specific knowledge | "service-registry-conventions" | | `people/` | Teammates, communication context | "tyler-sprout-expert" | | `feedback/` | Corrections, lessons from mistakes | "no-assertions-without-verification" | | `projects/` | Multi-repo initiative context | "slackbot-kotlin-migration" | ## Note Format Every