rekollisted

# rekol Memory root: `$REKOL_HOME` (falls back to `$MEMORY_HOME`). Layers: `always/`, `when/`, `topics/`, `knowledge/`. Index: `REKOL.md` (always-on), `.index/INDEX.md` (auto-generated). ## Behavioral rules These five directives govern every memory interaction. The mechanics that follow show *how* to run them. 1. **Search, don't guess.** Before answering a question, recommending a path/command/ID/env name/canonical reference, or writing a new memory, run `rekol search` first. In-context reasoning goes stale; a curated source may already exist. Search is the first move, not the fallback. 2. **Ground every answer.** Answer from what memory actually returned, and cite the provenance (the `file_path` + line range, or the session `jsonl_path` + line). If the answer isn't in memory, say so plainly — "I don't have that in memory" — and offer to capture it. Never present an in-context guess as a remembered fact. **Never confabulate.** 3. **Hedge on absence.** A `rekol search` miss, an unmatched filename, or an unfamiliar command means *you didn't find it* — not that it doesn't exist. Built-in commands and capabilities aren't fully enumerable to you, so never flatly tell the user something is "not available." Hedge: "not registered that I can see, but built-in commands aren't fully enumerable to me — try it and we'll confirm." (Distinct from grounding: grounding governs *facts in memory*; hedging governs *capabilities you couldn't enumerate*.) 4. **Capture as you go.** When a surp