“My prime directive is, don’t transfer information — transfer intelligence.” — Lou
Session context: 2026-04-16_Mastermind — Lou articulated the design philosophy behind his cognitive twin: capturing not just what happened in a conversation, but the reasoning patterns, frameworks, and decision processes that drove it.
Core Idea
There is a fundamental difference between storing what you know and storing how you think. Most knowledge management captures information — facts, procedures, conclusions. A cognitive twin captures intelligence — the reasoning patterns, the frameworks you unconsciously apply, the questions you ask and why, the judgment calls you make at decision points.
Lou’s vault is designed to perform dual capture on every conversation: operational knowledge (the steps taken, the tools used, the outputs produced) and cognitive knowledge (the intentions behind questions, the frameworks that informed decisions, the patterns exhibited across interactions). The cognitive layer is what makes the system a twin rather than a database. It’s the difference between “Lou asked Claude to audit the plan” (operational) and “Lou asked for an audit because his experience shows plans always have undiscovered flaws, and he values critical self-evaluation over speed” (cognitive).
Don Back reinforced this by describing how Opus analyzed his 15-minute coaching interviews and surfaced moments where he unconsciously coached mid-interview — “exactly at the moment when you said this, you responded to that. I didn’t ask for it, but I asked for an analysis of it.” The cognitive capture revealed expertise he didn’t know he was demonstrating.
Practical Application
After your next productive AI conversation, add this to your capture prompt: “Beyond documenting what we did, analyze HOW I approached this. What questions did I ask and what do they reveal about my frameworks? Where did I push back, and what does that suggest about my decision criteria? What patterns do you see in how I think about problems like this?” Store the cognitive analysis alongside the operational summary. Over time, this builds a profile of your expertise that’s more useful than any collection of facts.
Related Insights
- Insight - EigenThinking — Turn Your Cognitive Fingerprint Into Intellectual Property — the theoretical framework for identifying what’s uniquely yours
- Insight - Codify Your Judgment Into Skills, Not Just Prompts — encoding judgment operationally
- Insight - Expose Your Hidden Judgment Through Observation, Not Introspection — AI watching you work reveals what you can’t articulate
- Insight - Let AI Watch You Work Then Ask It What It Noticed — the practical technique for cognitive capture
Evolution Across Sessions
This builds on Insight - EigenThinking — Turn Your Cognitive Fingerprint Into Intellectual Property (2026-02-19), which established the concept of cognitive fingerprints as IP, and Insight - Expose Your Hidden Judgment Through Observation, Not Introspection (2026-04-02), which showed how AI observation extracts tacit knowledge. The new development is the explicit design directive — “transfer intelligence, not information” — as an architectural principle for knowledge systems, and Don Back’s real-world evidence that AI can surface expertise the expert doesn’t know they’re demonstrating.