new-codebook

new-codebook — your own material, your own codebook

This makes the Squatch working system yours: point it at your notes and it builds a local hyperdimensional codebook you can query — no cloud, no LLM, nothing leaves the machine. Each note becomes one complex vector; relationships are geometry. (Background: the Near Enough references.)

When to use

The user has a body of their own material — a notes folder, a docs tree, a personal zettelkasten — and wants to search it, find related items, walk neighborhoods, or do analogies over it. Their corpus stays local; their codebook is theirs.

How to do it

1. Find their material. Ask for (or confirm) the directory of .md/text files. Never assume a path — it's theirs, and it never gets committed or sent anywhere.
2. Build the codebook with the bundled tool (pure-numpy, no network):

   python3 "${CLAUDE_PLUGIN_ROOT}/tools/codebook/codebook.py" build --notes <their-dir> --out <their-dir>/.codebook
   

3. Use it — these all run locally against their vectors:
   • query "<text>" — most-related notes to a phrase
   • related <note> — neighbors of a note
   • walk <note> — traverse the neighborhood
   • analogy <a> <b> <c> — a is to b as c is to ?
4. Keep it theirs. The codebook + corpus live in their directory. They are never staged into this plugin, never committed, never sent out (the egress-guard enforces this on any outbound tool).

Rules

• The corpus and codebook are the user's private data — local only. Do not copy them into the repo.
• No LLM is required to query a codebook; it's geometry. Use it before reaching for a model.
• If the tool's dependency (numpy) is missing, say so and stop — never silently degrade to keyword grep.