A latent semantic index places every unit of a prose graph — a library section, a skill, a bean — in a space built from which words occur together, so units that discuss the same thing in different words sit close. It is a retrieval aid: every neighbour and finding it reports is a proposal, never a relation the graph asserts.
The method is Latent Semantic Indexing (node lsi), with
correspondence analysis (node correspondence-analysis) as its parallel track;
how to build, query and audit an index is the skill lsi-indexing.
Which graphs need an index
A graph needs one at 100 units and 20,000 words — a house threshold, with its
basis in scripts/lsi.ts. Below it a graph is not judged, which is not
the same as fine. The same verdict is kg:audit’s tool-downstream-fresh for the lsi-index Tool.
Whether an index is fresh is a question about the store, not about this tree, so it is not on this committed page — the published one carries it, drawn from the evidence that build fetched.
| graph | needs one |
|---|---|
aai-programme/beans |
state graph — indexed on demand, never committed |
aai-programme/docs |
below the need-an-index threshold — not judged |
aai-programme/library |
below the need-an-index threshold — not judged |
bootstrap-tools/bootstrap-tools-skills |
below the need-an-index threshold — not judged |
bootstrap/skills |
below the need-an-index threshold — not judged |
cat-harness-tools/beans |
state graph — indexed on demand, never committed |
cat-harness/docs |
yes |
cat-harness/folio |
below the need-an-index threshold — not judged |
cat-harness/library |
yes |
cat-harness/memory |
below the need-an-index threshold — not judged |
cat-harness/methodologies |
below the need-an-index threshold — not judged |
cat-harness/policies |
below the need-an-index threshold — not judged |
cat-harness/site-chrome |
below the need-an-index threshold — not judged |
cat-harness/skills |
yes |
folio-assistant-core/beans |
state graph — indexed on demand, never committed |
folio-assistant-core/core-library |
below the need-an-index threshold — not judged |
folio-assistant-core/core-methodologies |
below the need-an-index threshold — not judged |
folio-assistant-core/core-skills |
below the need-an-index threshold — not judged |
folio-assistant-core/folio-assistant-core-docs |
below the need-an-index threshold — not judged |
folio-assistant-core/folios |
below the need-an-index threshold — not judged |
folio-assistant-core/glossary |
below the need-an-index threshold — not judged |
folio-assistant-core/memory |
below the need-an-index threshold — not judged |
Generated by bun run cat lsi:viz, and this is the committed half: the front matter, the prose, and which graphs need an index — every part of it a function of the TREE. Each index’s freshness is a question about the store, and its size, retained share, dimension poles and findings are a function of the index’s CONTENT, which a one-sentence edit to any indexed graph moves. The docs-site build adds both with --detail, from the evidence it fetched for its own commit. Bean tqjj.