Published: March 23, 2026
Tiago Forte just validated something I've been building for the last two months.
He sent out an email this week announcing "Personal Context Management" as the evolution of PKM. He coined "Context Architect" as the new identity. He's launching a cohort around it on Thursday.
I read the whole thing nodding.
Not because I'm early to an idea. Because I've been running the production version of what he's describing since January 22.
Let me walk through his claims and show you what they look like when you actually build them.
"Pick up where you left off."
I named this problem months ago: the Stranger Loop.
Every time you open a new AI conversation, you're talking to a stranger. You explain who you are. What you do. What your brand sounds like. What your constraints are. What you tried last time.
Every. Single. Time.
Nobody quits AI because the output was bad. They quit because re-establishing context every session costs more than the value they're getting. Death by a thousand onboardings.
I wrote about this in February. The term "Stranger Loop" came out of watching this pattern kill adoption in every person I worked with. "Picking up where you left off" is the goal. But you don't get there by wishing. You get there by engineering persistent context that loads before every session, automatically.
I have 325+ sessions across two months. My AI reads a context file before every single one. It knows my values, my current projects, my 90-day goals, my communication style, my personality type, my neurodivergent working constraints, and the names of the 20 specialized agents it coordinates with.
It doesn't "pick up where I left off." It was never gone.
"Context Architect" as the new identity.
I call what I built a cognitive architecture. Not because it sounds cooler. Because the term has 40+ years of academic backing in cognitive science — Soar, ACT-R, LIDA. These are frameworks for how systems process information, maintain context, and make decisions.
"Context Architect" is a great identity for the person. "Cognitive architecture" is the accurate term for the system.
The distinction matters because architecture implies structure. It implies persistence. It implies that the system gets better over time because the relationships between components compound. An architect designs something that outlasts any single session.
Information expires. Systems compound.
"Curate, organize, and update your context modularly."
This is where it gets specific.
My system loads context modularly — each agent gets the identity, instructions, and working memory it needs for the current session. Components can be updated independently. When I update my values, every agent inherits the change on its next session. When a client project shifts, only that project's context file changes. Nothing else breaks.
I have a governance process that reviews patterns across sessions, decides what's worth codifying into permanent templates, and manages version control. The system learns from itself.
This isn't "organize your notes." This is systems engineering for personal context.
"From doer to architect."
The doing isn't the work anymore. The thinking is the work.
This is the sentence I keep coming back to. A marketing director I work with was looking to update his Google Ads standards across his team. He fed an optimization book to his AI CLI tool. It produced a 12-page analysis with account-specific action items mapped to his actual campaigns. In one morning, he went from reference material to a complete operational playbook.
The book was content. The analysis was context. But the part where he decided what mattered, what to ignore, what to act on — that was thinking. That was the actual work.
5 videos I produced turned into 50 cross-platform content pieces through my agent system. All 50 were uploaded and optimized without my full attention. Not because I worked harder. Because the architecture knew how to think about each piece differently for each platform — and then executed it. That's the force multiplier.
Think better so you can do more. It's not a trade-off. It's a multiplier.
"Values, personality, temperament, operating principles."
My system tracks my Enneagram type, my Kolbe scores, my MBTI, my neurodivergent working constraints, my business values, and my personal values — patience, sincerity, open-mindedness, accountability, commitment.
It doesn't just know them. It holds me accountable to them.
When I'm about to take on too much work, the system flags what I call the overextension pattern. When I'm drafting a message that doesn't match my communication values, it catches it before send. When a decision doesn't align with my 90-day goals, it names the specific value being violated.
This isn't personality quiz decoration. It's a governance layer. The AI doesn't just help me work faster. It helps me work like myself — even when I'm tired, distracted, or defaulting to old patterns.
So what does this mean?
Tiago is right. Context management is the next layer. The shift from information to architecture is real.
But I'd push it one step further: the bottleneck isn't technical anymore. It's contextual range.
The tools are available. Claude Code, persistent context, modular loading — all of this exists right now. The gap isn't access. The gap is knowing what context to capture, how to structure it, and how to make it compound across hundreds of sessions.
That's not a course you take once. It's not a cohort you go through and move on from. It's an architecture you build and maintain.
I've been writing about this journey publicly since February. The Stranger Loop. The AI Chief of Staff. The full cognitive architecture. All of it documented, all of it in production.
If Tiago's email resonated with you, go deeper. The rabbit hole is worth it.
This is part of the AI Executives series. Want to build your own cognitive architecture? Connected Intelligence teaches the full system.
