rekallisted
Install: claude install-skill rekal-dev/rekal-cli
# Rekal — which substrate answers this?
Most wasted effort is the wrong substrate. Decide before you grep or recall.
| Substrate | Holds | Tense | Reach it with | Answers |
|---|---|---|---|---|
| Tree | current code | now | grep / read | what does X do, where is it |
| Knowledge | current prose | now | `rekal "<q>"` → Read HEAD | convention / what we know |
| Ledger | session intent | past | `rekal "<q>"`, drill `rekal query --session` | why, tried, rejected |
| Map | structure | — | `map.sh` + workflow | how is it built |
## Boundary
1. Is it true **now**, or something that **was**?
- **Was** — a reason, a rejected path, a past correction, or a fact whose only
record is a past conversation → **Ledger**. (On a pure-dialogue corpus only
the ledger has content — go there.)
2. If now — **code** or **prose**?
- **Code** (path/symbol, present tense) → **Tree**. Grep; do not recall.
- **Prose** → **Knowledge**. Never invent an episode when HEAD prose answers.
grep for code that is · knowledge for prose that is · ledger for the why that was.
## Commands — text by default, `--json` for machines
Rekal's read commands print compact agent-readable text; add `--json` only when
a program needs to parse it.
- `rekal "<q>"` — recall. Prints a **seed digest**: line 1 is the verdict
(`INJECT` / `KNOWLEDGE` / `SILENCE`), then per-seed `sid conf=… t<n> "snippet"`.
One call already **widens itself** — it fuses several deterministic
reformulations of your query (