azcomputerguru/claudetools
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(harness): demote GrepAI below the wiki in recall hierarchy

Browse Source 
Resolves the contradiction between CORE (wiki-first) and EXTENDED (which said
'use GrepAI first for any context lookup'). New order: wiki for known entities ->
GrepAI for code call-graphs / discovery / un-compiled detail -> raw reads. Keeps
GrepAI's irreplaceable code-search value; removes the redundant wiki overlap.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
Mike Swanson
2026-06-08 08:14:20 -07:00
parent 68ad1dbd40
commit e8a689b03e
1 changed files with 16 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

19
.claude/CLAUDE_EXTENDED.md
View File

@@ -323,11 +323,24 @@ Tier 0 — **Ollama is the documentation and classification engine.** Route pros
### GrepAI (Semantic Code Search)
**Use GrepAI first for any context lookup before reading files directly.** It indexes all session logs, skill files, and project docs with boosted relevance for `.claude/` and `session-logs/`.
**Recall hierarchy — wiki first, GrepAI second.** GrepAI is NOT the first stop for context.
The synthesized **wiki** (`wiki/`, 57 curated client/project/system articles) is the truth layer
for a *known entity* — check it first (it is cheaper and already distilled). Go to GrepAI when the
wiki can't answer:
1. **Code** — `grepai_search` / `grepai_trace_callers` / `grepai_trace_callees` over the Rust+TS
corpus (~8k files). The wiki has zero code awareness; this is GrepAI's irreplaceable value for
GuruRMM/GuruConnect dev (call-graph tracing, "where is Z implemented").
2. **Discovery** — you don't know the entity name, or no wiki article exists yet (a new
client/system not yet compiled).
3. **Sub-synthesis detail** — a fact that was in a raw session log but didn't make the wiki's
summary cut.
Order of recall: **wiki (known entity) -> GrepAI (code / discovery / un-compiled detail) -> raw
file reads.** Do NOT GrepAI something the wiki already answers — that's the redundant overlap.
- **When to use:** "what did we do with X", "how does Y work", "find where Z is configured", context recovery, exploring unfamiliar code
- **MCP tools:** `grepai_search` (primary), `grepai_trace_callers`, `grepai_trace_callees`
- **Agent:** `deep-explore` (for multi-hop exploration)
- **Agent:** `deep-explore` (for multi-hop CODE exploration)
- **CLI:** `$CLAUDETOOLS_ROOT/grepai search "query" --json -c -n 5`
- **Watcher:** runs as scheduled task "GrepAI Watcher - claudetools" (auto-starts on login, keeps index current)