About the Progression
What is the Seven-Stage Integration Progression?
It's the structural framework this community is built around — a developmental map for how AI fluency actually builds, from the moment you start working with AI seriously (Stage 1: Intent Clarification) through the point where AI is integrated at the level of how you think (Stage 7: Cognitive Architectures).
Each stage produces real capability. Each stage also has a ceiling. Moving through the stages requires deliberate development, not just accumulated usage. The progression is grounded in published research — CDPID (Collaborative Driven Progressive Intent Discovery, DOI: 10.2139/ssrn.6278438) — and in extensive practical experience working with knowledge professionals on AI integration.
What stage am I at?
Go to Start Here. There's a self-assessment with a description of the experience at each stage — not what you know or what you've done, but what you actually experience in your AI sessions day to day. Find the one that most honestly describes where you are right now.
How fast should I expect to move through the stages?
Stages aren't timed — they're developmental. Movement requires deliberate practice, not just AI usage volume. Someone who uses AI for 10 hours a week but doesn't build context architecture will stay at Stage 2 indefinitely. Someone who spends a focused effort building their SuperContext and practicing file-first execution can develop genuine Stage 3 capability in a matter of weeks.
The honest answer varies by stage. Stages 1–2 can develop relatively quickly with focused practice. Stage 3 takes longer because you're building infrastructure, not just developing a skill. Stage 4 requires having enough of your own IP documented and validated to produce at scale, which takes time. Stages 5–7 are longer-horizon developments.
The community is designed to accelerate each stage — not to make shortcuts possible, but to prevent the most common forms of getting stuck.
Can I skip stages?
No. Each stage builds genuine capability that the next stage requires. Attempting to operate at Stage 4 with Stage 2 foundations produces inconsistent results that are difficult to diagnose, because the missing piece isn't Stage 4 skill — it's the Stage 3 infrastructure that Stage 4 relies on.
A practical way to think about it: the stage descriptions aren't about what you know, they're about what you can do reliably and what you experience in your AI sessions. If the description of a stage still describes your experience accurately, you're still developing through it — regardless of how long you've been using AI.
What's the difference between Stage 1 and Stage 2?
Stage 1 is about intent clarity — knowing what you want precisely enough to ask for it. Stage 2 is about cognitive translation — representing what you want in ways AI can work with accurately.
In practice: Stage 1 work is figuring out what you actually mean. Stage 2 work is communicating what you mean precisely enough that it doesn't get lost in translation.
Both gaps produce similar symptoms (output that misses), which is why they're easy to conflate. The diagnostic: when output misses, does the miss feel like AI not understanding what you want, or like AI misrepresenting what you clearly wanted? The first is usually Stage 1. The second is usually Stage 2.
What's the fastest way to develop Stage 3 capability?
Access the AI Mastery Toolkit — free with your registration — and orient to it seriously. It's a production-grade Stage 3 context architecture. Seeing what a mature system looks like is more useful than any description of what to build. Start with the SuperContext structure: a single orientation document that gives AI an accurate, current picture of who you are before every session. That one piece eliminates more context-rebuilding than anything else.
→ Access the AI Mastery Toolkit → Stage 3: Context Richness
The stages feel very different from AI advice I've encountered elsewhere. Why?
Most AI content is tip-focused: prompts, techniques, hacks, specific tool features. This framework is development-focused: building genuine cognitive capability that compounds over time and transfers across tools.
The practical result is that the framework asks you to invest in things — like context architecture and intent clarity work — that feel slower than collecting good prompts. They are slower at the front end. They produce substantially better compounding outcomes over months and years.
The research grounding (CDPID) reflects a model of human-AI collaboration that's more accurate and more demanding than the transactional model most AI advice assumes. That's intentional.
Using the Community
How are the groups organized?
One discussion group per stage. If you're at Stage 3 developing through Stage 4, join Stage 3 primarily and participate in Stage 4 as you approach it.
The value of stage-specific groups: the people in your group are diagnosing similar challenges and building similar capabilities. The discussions are specific and actionable in ways that cross-stage conversations often aren't.
- Stage 1 Group — Intent Clarification
- Stage 2 Group — AI Fluency
- Stage 3 Group — Context Richness
- Stage 4 Group — Content Engine
- Stage 5 Group — System Automations
- Stage 6 Group — Universal Dashboard
- Stage 7 Group — Cognitive Architectures
How do I find resources for my stage?
Resources are organized by stage. Go to your stage page — each one links to the resources specific to that stage, including the AI Mastery Toolkit for all stages and stage-specific frameworks, templates, and guides.
→ Start Here → Your Stage Page → Stage-specific resources
How do I get feedback on my work?
Bring it to your stage group. The most valuable thing you can do in the community is bring real work — not abstract questions about AI, but actual implementation challenges, context architecture decisions, output quality diagnostics. The shared framework gives everyone a common language for diagnosing what's happening and what to try.
For implementation-specific support and structured help building your context architecture and workflows, that's what premium membership is for.
What should I bring here vs. work on alone?
Bring to the community:
- Questions about where you are in the progression and why
- Implementation challenges you're stuck on
- Context architecture decisions you want a second perspective on
- Examples of session failures you want help diagnosing
- Stage transition questions — "am I ready for Stage 4?" type questions
Work on alone:
- Individual AI sessions (the sessions themselves are solo practice)
- Building your own context architecture (the building is yours to do)
- Developing your own IP (the IP is yours to develop)
Bring to premium support:
- Structured implementation guidance
- Ongoing accountability for your progression
- Complex context architecture design
What's the relationship between the community and the courses?
The community is the foundation — the AI Mastery Toolkit, the stage groups, the shared framework. Courses develop specific capabilities within the stages more systematically than peer discussion can. Most members find the community most valuable when combined with course work: the courses give you structure and instruction, the community gives you cohort, feedback, and the context that makes the instruction applicable to your specific situation.
What's the relationship between the community and 1:1 coaching?
The community is the right place for most members most of the time. Coaching is appropriate when personalized depth — understanding how the framework applies to your specific cognitive patterns, your specific professional context, your specific IP — is the development priority. Not everyone reaches that point. When you do, the coaching pathway is there.
The Philosophy
Why "healthy" AI fluency?
"Healthy" distinguishes the kind of AI fluency we're building from two failure modes that are common and often invisible:
The first failure mode: shallow fluency — consistent AI use without genuine development. Using AI as a transaction machine (ask → get output → repeat) produces a consistent, low ceiling. It doesn't compound. The person using AI this way for a year hasn't developed much more than the person who started last month, because nothing they've accumulated compounds.
The second failure mode: unhealthy depth — AI integration that deepens dependency rather than capability. AI that substitutes for your thinking rather than extending it. Context systems that make AI more central without maintaining your own generative capacity. This failure mode looks sophisticated from the outside. It's harder to recognize than shallow use, and its effects compound negatively.
"Healthy" means: developing genuine cognitive capability through AI integration. Getting better at thinking, not just at producing output. Building a compounding system that you own, not a dependency you can't function without. The measure: remove AI from a domain where you've integrated it deeply. Are you more capable than you were before, or less?
This community is built around the version of AI integration that produces genuine, compounding, human-owned capability.
What does "AI as Experiential Technology" mean in practice?
It means AI isn't a tool you learn to use once and then use correctly. It's a capability you develop over time, through practice, that returns more as you bring more to it.
The contrast: a power drill is a tool. You learn to use it, and then you use it the same way indefinitely. Your skill doesn't compound. The relationship doesn't deepen.
A language is experiential. You develop it over time. Your fluency deepens with use and practice. The capability compounds. What becomes possible for you at five years of fluency is different in kind, not just degree, from what was possible at six months.
AI fluency follows the experiential model. Which means the development practices that work for experiential capability — consistent practice, deliberate development, accumulated investment — are the ones that produce genuine AI fluency. And the practices that don't work for experiential capability — tip collection, tool-switching, technique-chasing — produce the AI equivalent of memorizing phrases in a language without developing fluency.
What is the CDPID framework?
CDPID — Collaborative Driven Progressive Intent Discovery — is the published research framework that grounds this community's approach to AI collaboration (DOI: 10.2139/ssrn.6278438).
The central finding: intent emerges through collaboration, not before it. Neither human nor AI arrives at a session with complete understanding. Both contribute to developing understanding through a progressive, collaborative process.
This reframes AI sessions fundamentally. Not: have your intent clear, execute it through AI. But: bring what you have, develop intent and understanding through the collaboration, capture what was developed so it compounds.
CDPID provides the academic foundation for everything taught in this community. It's not a philosophy or a framework someone thought up — it's a documented, peer-reviewed model of how effective human-AI collaboration actually functions, developed through systematic research.
How does this connect to the Seven Pillars and the coaching work?
The community is organized around the Seven-Stage AI Integration Progression. The coaching work is organized around the Seven Pillars of Intellectual Architecture — a broader framework that addresses how high-performing professionals think, organize their work, and develop cognitively.
They're complementary, not redundant. The community develops AI fluency specifically. The coaching develops the full intellectual architecture — of which AI integration is one important dimension.
Stage 7 (Cognitive Architectures) is the natural convergence point: where AI integration becomes integrated into cognitive architecture development more broadly. Members who reach genuine Stage 7 engagement are doing work that connects directly to the coaching framework.
The pathway: community → courses → coaching follows the same developmental logic as the Seven-Stage Progression. Each level provides real value. Each level also has a ceiling that the next level is designed to address.