Follow a question. Watch knowledge become useful.
Fictional people, pages, procedure, tool response and draft. The structure reflects our setup; the route is scripted, not a recording of an AI session.
brain
Fictional example · scripted route
What is holding up this project,
and what should I do next?
Company + standard department repo + own private notes. Their own task-tool login.
Rules · already included
Maps · points to
Index · describes
Knowledge + procedure
Tool · returns evidence
Other repositories: outside this person’s view.
Reading trail and exact counted text
Words split at whitespace; unique fragments counted separately. User question and technical messages excluded. No real documents or tools are loaded.
- Working rules
Read the map before answering. Cite evidence. Treat a copied page as a copy.
- My INDEX.md
My note — preferred format for project updates.
- Skill descriptions
Project check — use when a blocked task needs evidence and a proposed next action.
The assistant reads the index first.
The map points to a folder. Its index describes when each page is useful. The selected page supplies company knowledge; a skill supplies instructions; a tool supplies current records. A shared index excerpt can already be inside the map. This is an example route, not an obligatory sequence for every question.
Company knowledge is shared. Department knowledge lives in standard and strategic repositories with separate readers. Private notes belong to their person. Changing the example person changes the visible material, not the underlying permissions. 017 explains who sees what.
A good route can still reach an old source. Try the stale copy: its date changes the draft. Maps, descriptions and knowledge need maintenance; none guarantees a correct answer.
Next: retrieval across folders.
The next step we are planning: semantic retrieval across folders and explicit weights on documents and skills. Neither exists today, and the graph above does not pretend otherwise.
We would need to test whether they improve source selection while keeping access boundaries and dates intact.