docs: name bin/brain/search.go; --hop is not a graph walk. (#10)
Tests / Test (push) Skipped
Tests / Release (semver) (push) Skipped

Published docs and skills still taught bin/kb/search --hop 1. Search lives
at bin/brain/search.go; --hop errors until File edges exist. A unittest
gates the SoT so the lie cannot return.
This commit is contained in:
2026-08-13 17:23:40 +01:00
committed by GitHub
co-authored by GitHub
parent 7e0f3c9e06
commit 46310f8773
8 changed files with 104 additions and 49 deletions
+4 -6
View File
@@ -30,12 +30,11 @@ related:
---
```
`bin/kb/index` reads this. `type` becomes a searchable column and `related`
becomes a graph edge:
`bin/kb/index` reads this. `type` becomes a searchable column. `related:` is
frontmatter for humans; graph hops from it are not implemented yet.
```bash
bin/kb/search "deploy" --type howto
bin/kb/search "Stecktafel" --hop 1 # follow links and related
bin/brain/search.go "deploy"
```
## Audit checklist
@@ -46,8 +45,7 @@ bin/kb/search "Stecktafel" --hop 1 # follow links and related
The indexer chunks on H2, so split files also search better.
3. Is `status: archive` set on anything superseded? Archived files stay indexed
but stop competing with current ones for a reader's attention.
4. Does every explanation link the reference it explains, and vice versa? That
link is what `--hop 1` walks.
4. Does every explanation link the reference it explains, and vice versa?
## Rule