firehose> #llmops

Retrieval Maturity Levels

A ladder for how a knowledge store retrieves, framed as five levels = five questions, each answering a distinct retrieval need:

  1. Route"Find it by an exact word or name?" Files + folders + a Context Routing file; native keyword/filename search. Most people never need to leave here.
  2. Topic wiki"Pull everything on a topic together?" Ingested notes cross-linked into indexed wiki pages; retrieval is "follow the trail and read the page."
  3. Semantic"I searched different words than I wrote?" Semantic Retrieval by embedding/meaning instead of exact match.
  4. Knowledge graph"Trace relationship chains across a cast (a CRM-like web)?" Knowledge Graph Retrieval with typed entities and relationships.
  5. Autonomous"Consolidate on its own while I'm away?" An always-on "Brain OS" that syncs and refreshes memory without you (e.g. Gbrain).

The load-bearing claim is not that higher is better. Complexity climbs with the level; capability does not automatically. The correct move is the lowest level that removes a pain you actually have — "most people land at 1–3," and moving up is only "better" when it fixes a felt pain point. This is Agentic Simplicity applied to retrieval architecture: no pain, no climb. A single store is also heterogeneous — one folder can be level 2 while another is level 4; you pick per folder based on the data and how it's queried (Query-Shaped Storage).

Claims


Linked from