diff options
| author | Pjotr <wrk@bosa.lan> | 2026-11-12 13:56:50 +0000 |
|---|---|---|
| committer | Pjotr <wrk@bosa.lan> | 2026-11-12 13:56:50 +0000 |
| commit | 051faf04d59bf45fde128df9d3c4b88c24f289f3 (patch) | |
| tree | b131223eb148c23f3d89b9c4bfa558c22a749644 /doc | |
| parent | 3fab7adf0ec147dceb150d861fdbd5f5b3693384 (diff) | |
| download | ai-memory-051faf04d59bf45fde128df9d3c4b88c24f289f3.tar.gz | |
index: a commit inherits the topics of the reasoning attached to it
topic:pve answered with nine reasoning entries and no commits, which is backwards for anyone following the story: the pve thread is carried by the commits (cd3e65b, 64e63bd, 3a42b5f, 8e11ec0) as much as by the notes. Commit documents now take the sessions of the reasoning attached to them (one GROUP_CONCAT query over reasoning, joined in memory) and gain the same S<session> and O<topic> terms, so the same query returns 13 documents instead of 9. Also documents the honest limit of session-derived topics in doc/SKILL.md: a session named gemma-wrapper-diagnostics about the same work does not answer topic:pve, while a plain-text pve search still finds it. topic: is the curated answer, free text is the recall answer -- name a session after the concept you want it found by.
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/SKILL.md | 9 |
1 files changed, 8 insertions, 1 deletions
diff --git a/doc/SKILL.md b/doc/SKILL.md index 570bde7..42f706e 100644 --- a/doc/SKILL.md +++ b/doc/SKILL.md @@ -95,7 +95,14 @@ text, stemmed. The default operator is AND; `--or` widens it. Topic terms come from the **session id**, split on hyphens: a session called `gemma-pve` answers `topic:gemma` and `topic:pve`. So the cheapest way to make -an entry findable by concept is to name the session after the concept. +an entry findable by concept is to **name the session after the concept** -- a +session called `gemma-wrapper-diagnostics` about the same work does not answer +`topic:pve`, while a plain-text `pve` search still finds it. That is the +difference between the two: `topic:` is the curated answer, free text is the +recall answer. + +A **commit inherits the topics of the reasoning attached to it**, so +`topic:pve` returns both the reasoning and the commits that carry it. Why a subprocess and a Guile script: `libxapian` is C++-only, so a foreign call from Odin needs a hand-written C shim. `guile-xapian` already has one, tested |
