Lore Recall

Use this workflow when past session memory matters. It sits above the low-level skills/lore CLI skill: use skills/lore for command mechanics and setup/indexing, use this skill for evidence planning, trust, freshness, and final packet shape.

Quick Start

1. Run lore status --json with the narrowest useful scope (--project, --source, --since, --until) before retrieval.
2. Build a recall plan: 2-4 query variants, likely filters, and why each query exists.
3. Search narrowly first: lore search "<terms>" --json, then --relevant when recency matters.
4. Drill down only from real ids returned by Lore: lore get <id> --full, lore context <id> --json, or lore session <session> --around <id> --json.
5. Emit a bounded evidence packet using references/evidence-packet.md.
6. If retrieval fails, report the gap and next queries tried. Do not invent memory.

Trust Rules