meta-collect-knowledgelisted

# meta-collect-knowledge Memory cascades DOWN one ancestor chain, so knowledge filed in a SIBLING project - or in a completely different knowledge TREE (a machine can carry several independent tree tops) - never reaches the current project on its own. This skill is the **inbound gather**: find knowledge elsewhere that is relevant here and bring it in safely. **REQUIRED BACKGROUND:** the storage spec (trees/anchors, slug store, engine fail-loud contract) is `bitranox:meta-self-improve` -> `references/memory-backend.md`. ## When to run - Manual: "collect knowledge", `/collect-knowledge`. - New-project init: seed a fresh project from the existing tree so it starts informed. - Opportunistic: a captured learning reveals a topic this project now touches - gather that topic. - As `bitranox:meta-dream-crosstree`'s inbound pass (the dream delegates here). ## Relevance needs a topic (descriptor-first) The query is the project's scope descriptor (the `bitranox:self-learning` block in its `CLAUDE.local.md`) or the topic of the triggering learning. At a brand-new project: first infer the descriptor (README, dir name, package metadata, the parent's descriptor); if scope is still unknown, defer - a blind gather pulls noise. ## Procedure (grep -> inspect -> import) 1. **Stage 1 - cheap grep (no model).** `python3 <this-skill-dir>/gather_scan.py --topic "<scope or topic>" --self "<cwd>"`. It greps other projects' curated slug-store bodies + native memory and prints candidates GR