What it does
Keeps a team's written knowledge usable instead of merely large. It turns a raw note, a decision or a post-mortem into a structured page, works out where it belongs, and plans the links back to it — because a page nothing links to is a page nobody finds again. It is built on a few rules that sound fussy until the collection is two years old. Links are bidirectional, or half the collection becomes unreachable from the other half. Pages are archived rather than deleted, because a deletion breaks inbound links nobody knew existed. Two pages that contradict each other are flagged as a contradiction and both kept, rather than silently resolved by whoever noticed last — the disagreement is usually the most valuable thing in the pair. Its health check finds what actually rots: pages with no inbound links, links pointing at pages that were never written, duplicate pages covering one topic under two names, and pages whose claims have quietly gone stale. It writes plans and structured content; it does not decide on your behalf. Merges and contradiction resolutions are proposed for a person to approve, because both destroy information when done wrong. Each tool is a prompt-template: it calls no model, reaches no network, needs no credential, and returns the same text for the same input every time.
Keeps a team's written knowledge findable instead of merely large.
Example prompts
- Turn these meeting notes into a decision record.
- Where does a post-mortem about the release-blocking crash belong, and what should link to it?
- Two of our pages disagree about how sessions expire. What do we do?
