Knowledge Base as Thinking Partner

A knowledge base used as a thinking partner does two jobs. It helps decide what to think about next, and it holds what has already been learned.

There is one test. Did this page make the next action clearer? If the answer is no, the system is turning into storage.

Core takeaways

• The test for every page and every session is the same: did this page make the next action clearer?
• Every interaction should leave at least one of five outputs: a sharper question, a better frame, a visible gap, a next action, or a reusable synthesis.
• The loop ends with a write-back. Without the updated page at the end, the session was browsing.
• The useful material is usually the tension between two pages rather than anything in a single page.
• Every result gets filed into the smallest useful destination: the Journal, the wiki, private Goals or Skills, a blog draft, or a system file.
• One session repairs a passive system. It costs one live question, three to six pages, and one write-back.

An archive and a thinking partner

An archive stores finished material. A thinking partner changes the next move. A page is a surface to think on. The work does not end when the page is written.

If the test fails, the system is turning into storage. The kinds of help a partner gives are pattern-finding, gap-finding, frame-testing, question-generation, and turning a vague interest into concrete work.

Every interaction leaves at least one of five outputs. A sharper question. A better frame. A visible gap. A next action. A reusable synthesis. A session that produces none of these retrieved well and still failed the test.

The mechanism has two steps. First, the current mental model is written down. Second, related pages are used to test it. A system that only retrieves is an archive with a better search function.

The loop is:

interest → question → relevant pages → pattern or contradiction → synthesis → next action → updated page

The last arrow is the required one. Without the write-back, the loop is browsing.

The knowledge base compounds when old pages start changing how new problems are approached. Adding sources alone does not compound it.

Archive asks	Partner asks
Where should this go	What does this change
What did this source say	What can I do differently now
What pages exist	What pages should talk to each other
What do I know	What am I missing

Archive mode is still useful. It keeps the system legible. Thinking-partner mode is the mode that changes the next move.

The five moves

1. Start from an active pressure, not a random topic

The system serves current judgment, not only future retrieval. The prompts that find that pressure: what is being decided; where the work is stuck; what keeps recurring; what feels important but under-formed; what would make this easier to act on.

2. Pull nearby pages, and do not start from scratch

The graph, the index, the backlinks, and the obvious links are enough. The starter packs below are entry points into this wiki. They are not summaries of the pages they name. The categories stay stable. The specific entries follow the live page names.

Learning: Prestudy, BHS, and SIR: Turning Information into Usable Structure is the encoding-and-retrieval synthesis. First Principles of Learning is the mechanism layer. Are You Learning, or Just Using Techniques is the diagnostic that asks whether the method is doing any work. Knowledge Mastery: From Recognition to Usable Knowledge is the ladder from recognition to use.

Execution: Attention Management: Preserving Flow is the entry page for preserving flow. Focus Management: How to Enter & Recover Inside a Work Block is entry and recovery inside a block. Procrastination: a System Problem treats delay as a system, not a character flaw. Decisional Delays is the stall that resembles thinking.

Judgment: Applied Critical Thinking: Testing Frames is how a frame gets tested. Decision Making is the decision page. How to Communicate Truth Into Someone Else’s Frame is the transfer problem. Suicidal Empathy is empathy that removes a necessary limit.

Building: Agentic Engineering is how agents get built here. Understanding Bottleneck is the comprehension stall. Interleaving for Complex Problem Solving is mixed practice on hard work.

3. Work the tension between pages

The useful material is usually the tension between pages rather than anything in a single page. Look for a concept with no operating model; two pages that imply different actions; a repeated failure mode; a missing link between theory and practice; a technique that does not change behavior; an interest with no next action.

Pages that came from that tension: Balancing Multiple Interests: Breadth v Focus is the collision between breadth and focus. The Shortcut Problem is the faster path that skips the encoding. The Technique Is Only as Good as the Thinking It Produces is method that looks right and changes nothing. How to Unlearn Old or Bad Habits Efficiently is the unlearning problem.

4. Convert the insight into a handle

A handle is a short name, question, or rule that can be used again later when the situation returns. It can be a title, a question, a checklist, a contrast, a next exercise, a decision rule, a page split, or a journal prompt. The handle is what makes the idea reusable. A good handle makes the idea easy to find again at the moment it matters.

Worked conversions:

• “better study habits” → Prestudy, Bear Hunter System, Spaced Interleaved Retrieval
• “too many interests” → Balancing Multiple Interests: Breadth v Focus, Priority 0+1
• “consuming without changing” → Are You Thinking, or Just Consuming?
• “method looks right but nothing improves” → The Technique Is Only as Good as the Thinking It Produces

5. File the result into the smallest useful destination

Write-back is one of the five moves and it is required.

Kind of result	Destination
Passing thought	Journal
Active question	Journal, What’s On My Mind
Current working area	Journal, Current Focus
Durable operating model	wiki
Personal plan	private Goals or Skills
Public argument	blog draft
System change	README, AGENTS, or a workflow page

A page is not created just because an idea exists. A page is created when it will be reused, linked, practiced, or argued with.

What it looks like when it is working

The important threads are already written down when the work is picked up again. Old pages are changing how new problems get approached. A session that produced no write-back failed the test, however much was read. A vault can also become a feed. The mechanism that does that is on Social Media - Curvilinear Design & the Theft of Time.

One session, when the system feels passive

One session is enough. The goal is not to process the whole vault. The goal is to make one part more usable.

1. One live question.
2. Read three to six related pages. The bound is a house limit, not a finding.
3. Write the current answer in plain language.
4. Name the tension.
5. Pick a destination.
6. Add one link, one next action, or one open question.

Failures and their repairs

Failure	Repair
Knowledge hoarding	Ask what the page changes
Index addiction	Start from a live problem
Link decoration	Link only when the relationship matters
Permanent synthesis	Use Journal for temporary thinking
Private/public confusion	Keep private Goals, Skills, and Kolbs local unless they are intentionally publishable
Agent overproduction	Ask for operating model, causal chain, failure modes, practical feel, and implications
Archive drift	End each session with a question or an action

Kolbs, in this vault: after an attempt, what happened, how it felt and why, what rule that suggests, what changes next time.

Good signs and warning signs

Good signs: the next question is obvious; old pages explain new problems; titles have become handles; interests are alive but bounded; the Journal reflects current attention; the index is stable enough; outputs are shorter because context is already held.

Warning signs: every session starts from zero; pages are polished but unused; the graph is interesting but not actionable; new sources do not update old pages; Journal questions sit unchanged for weeks; the system looks impressive and nothing changes because of it.

The weekly questions

Weekly questions, asked once: what page changed how the week was acted; what question kept returning; what thread is stale; what should be synthesized next; what belongs in a blog post. The weekly review is not a ritual done for its own sake.

What a session costs, and when to stop

A partner that never writes back is an archive. Starter packs go stale as pages are renamed; the categories stay and the specific entries follow the live page names. Artifact production without a live question is the agent-overproduction failure. A session costs three to six pages plus a write-back.

Quit signals: two sessions that start from zero, a week of Journal questions unchanged, or a weekly review that produces no next action.

One session leaves a destination, and the test can be answered yes or no. The same test applies after something has been filed: did this page make the next action clearer?

How to practice this

1. Pick one live question from work in progress. Ask what is being decided, where the work is stuck, or what keeps recurring. Notice whether a real pressure exists or the topic is random.
2. Read three to six related pages found through the graph, index, backlinks, and obvious links. Notice that three to six is a house limit, not a finding.
3. Write your current answer to the question in plain language. Notice which of the pages then contradict what you wrote.
4. Name the tension between the pages. It may be a concept with no operating model, or two pages that imply different actions. Notice that the tension is usually more useful than a single page.
5. Convert the result into a handle: a short name, a question, or a rule. Notice whether you could use it again when the situation returns.
6. Pick a destination and add one link, one next action, or one open question. Notice whether the next action is clearer than it was before.

Related pages

• Context Engineering: the three-layer pattern this workflow sits on.
• Metacognition: The Control Layer: the control layer the weekly review is a special case of.
• Agentic Engineering: the building entry page, and the questions the workflow starts from.
• Journal: temporary thinking, and the destination for a passing thought, an active question, and current focus.

Open questions

Starter packs will go stale during regen. How should a later pass refresh the entry pages without rewriting the moves?

When is archive mode the right mode for a stretch of work, rather than a drift to correct?

Sources

• LLM Knowledge Systems: vault pattern this workflow sits on.
• AGENTS: house operating rules for ingest, query, and write-back.
• Sönke Ahrens, How to Take Smart Notes (2017); Vannevar Bush, “As We May Think” (1945); Douglas Engelbart (1962): the popular “notes as thinking” lineage. Named here only. Not required reading. Nothing in them replaces the five moves or the archive/partner table.