Name the Huginn organ, not voidbot, as the semantic search path
The skill's own changelog already carried the 2026-09-16 ruling that the organ depends on Qdrant directly. The overview line still promised voidbot, which is steering text an agent would read at the next cut. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
parent
96c98d5ceb
commit
54b05c3884
1 changed files with 3 additions and 2 deletions
5
SKILL.md
5
SKILL.md
|
|
@ -9,8 +9,9 @@ Eureka is the pipeline used by Claude Code agents. It sits next to **Epiphany**,
|
|||
the running organism in `F:\Projects\Epiphany`, and shares its faculty
|
||||
vocabulary. The difference is substrate:
|
||||
- **Epiphany** keeps its findings in typed, admitted state that can be queried
|
||||
by exact filter. Semantic search over that state is planned through voidbot;
|
||||
Epiphany removed her own vector stack in `856648de`.
|
||||
by exact filter. Epiphany removed her own vector stack in `856648de`;
|
||||
semantic search is planned through the Huginn memory organ, which depends on
|
||||
Qdrant directly.
|
||||
- **Eureka** currently keeps them in committed docs (the target and the cut
|
||||
map), subagent reports and memory files.
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue