memory-search

name

memory-search

description

Recall the right past decision, fact, or reason from the OKF memory bundle + git history BEFORE acting. Use when about to make a decision that may already be settled, when you need the reason behind an existing choice, when an error may have a known fix, or when starting work in an unfamiliar area. Triggers on "have we decided", "why is X this way", "did we hit this before", "what's our convention for".

memory-search - read the memory, don't re-derive it

Memory here is an OKF bundle (memory/*.md concept files + an index.md) plus git history (the episodic log; log.md is its generated view). Your job: retrieve the smallest correct slice and stop. Loading everything is the failure mode, not the goal - accuracy drops sharply past ~32K tokens of loaded context.

Read path (in order - stop as soon as you have the answer)

1. Index first. Read index.md - the cheap map (titles + one-line descriptions grouped by type). Pick the 1-3 concepts that match. NEVER walk the whole tree first.
2. Open only those concepts. Read the matched concept file(s) in full. Each is one fact/decision.
3. Ask git for the "why" and the history before re-deciding anything (recipes below).
4. Check freshness. If a concept's timestamp is old or the area changed since, treat it as a point-in-time observation, not live state - verify against current code before trusting.

Git retrieval recipes (the episodic read path)

• Why a decision/area is the way it is: git log --grep '<keyword>' --all-match
• Evolution of one subsystem, newest first, with the lesson inline: git log --grep '^skillsys(<owner>)' --pretty=format:'%h %ad %s%n - %(trailers:key=Lesson,valueonly=true)' --date=short