knowledge-synthesize
A knowledge base is worth more than the sum of its notes only when something
traverses it and surfaces a link your memory missed. Left to itself, every
note is an island. knowledge-synthesize finds the connections that cross
nodes — the same blocker hitting two areas, a note that contradicts the decision
it cites, the old write-up that is suddenly relevant again.
What it solves
The cost of a siloed base is invisible: you only pay it when you didn’t connect two things and shipped the worse decision because of it. A cross-node pattern never surfaces unless you already suspect it and go looking — which means it mostly doesn’t surface at all. This skill makes the base do the looking.
How it works
The deterministic core (octopus synthesize) computes ranked candidate
connections over the octopus kr registry; the skill makes the judgment calls a
script cannot.
The core surfaces three signals:
- shared-target — two nodes that link the same third node (they relate through it);
- co-mention — an entity that recurs across several nodes but has no node of its own (a topic worth promoting);
- relevant — with
--node, other nodes ranked by shared-entity overlap with a focus node: the forgotten-but-relevant lookup.
Entity extraction is language-neutral — it reads [[wikilinks]] and
`code` spans, which work in any language, and leaves free-text proper-noun
detection to the skill rather than a hardcoded English heuristic.
The skill then judges which candidates are real, reads a node against the
authorities it links (an ADR, a spec) to flag contradictions, and — with
--fix — seeds a link only when a mention resolves to exactly one node, leaving
the ambiguous cases as report-only.
Usage & parameters
octopus synthesize [--root <id>] [--node <path>] [--fix]| Flag | What it does | Default |
|---|---|---|
--root <id> | Synthesize over one knowledge root. | every resolved root |
--node <path> | Forgotten-but-relevant lookup for one node (ranks others by shared entities). | whole-root scan |
--fix | Seed a link when a mention resolves to exactly one node (reversible). | report-only |