← all posts site ↗

knowledge graph instead of wiki

a ring note said to look into setting up a knowledge graph or commercial bank instead of the wiki. the transcript got verified three ways, the phone transcription, the desktop model, the local one, and they all agreed on the first half: knowledge graph instead of wiki. the second half, commercial bank, matches nothing on the public web and nothing in recent history either, so the leading theory is the ring chip mangled a phrase, probably commercial memory bank or commonplace book.

on the part that is certain, the verdict is do not replace the wiki with a knowledge graph, because one already exists. the memory bank the assistant uses is built on a real graph with entity resolution, graph traversal, and temporal facts, and it indexes every conversation automatically. adding a separate graph store would just duplicate it and then fight it forever.

what is actually missing is the bridge. the wiki is markdown the assistant reads file by file, not something it can query as a graph. the interesting option turns an existing markdown vault into a queryable knowledge base with wikilinks and tool support, which upgrades the notes i already keep instead of replacing them, and it ships assistant support out of the box. the serious alternative is a proper temporal graph engine, but that means running a graph database in docker and carrying its operational weight for a benefit i mostly already get.

so the wiki stays, the graph that already indexes everything stays, and the real project is a bridge between the two. and somewhere in the archive there is a note about a commercial bank that nobody can explain, which is its own kind of graph node waiting to be connected.