Durable Sessions AI UX vs Skool About Page VSL: Which?
// TL;DR
These two frameworks solve completely unrelated problems, so there is no either/or decision. If you are building or fixing an AI chat product with streaming, disconnections, or multi-agent issues, use the Durable Sessions AI UX Framework. If you are writing or auditing a Skool community About page to convert cold traffic into paying members, use the School About Page VSL Framework. The only scenario where both apply is if you run an AI-focused paid community on Skool and also ship an AI product—in which case you need both.
// HOW DO THEY COMPARE?
| Dimension | Christensen Durable Sessions AI UX Framework | School About Page VSL Framework |
|---|---|---|
| Best for | AI product teams building or auditing streaming chat/agent experiences | Community builders writing a Skool About page to convert cold traffic into members |
| Domain | AI UX / real-time streaming infrastructure | Copywriting / membership sales conversion |
| Complexity | High — requires understanding of SSE, WebSockets, pub/sub, multi-agent architectures | Moderate — requires copywriting skill, Canva, and basic video production |
| Time to apply | Days to weeks — involves architectural redesign and infrastructure changes | Hours to a few days — writing, graphic design, and one short video |
| Prerequisites | An existing or planned AI product with a streaming response layer (SSE, WebSocket, etc.) | A Skool community (existing or planned), a target niche, and founder proof points |
| Output type | Architectural design: a Durable Sessions layer between agents and clients | Marketing asset: a four-layer About page (copy, graphics carousel, video) |
| Creator / source background | Mike Christensen (Ably) — real-time infrastructure and AI engineering | Analysis of the top 45 Skool Games leaderboard communities |
| Key principle | Decouple agents from clients via a persistent shared session; never tie streams to a single connection | Treat the About page as a Video Sales Letter, not a description; sell the destination, not the flight |
| Primary failure it prevents | Streams breaking on disconnect, no multi-device continuity, no live agent control | Low conversion because the page describes features instead of selling the transformation outcome |
| Audience technical level | Software engineers and product architects | Non-technical creators, coaches, and community operators |
What does the Christensen Durable Sessions AI UX Framework do?
The Durable Sessions AI UX Framework, created by Mike Christensen of Ably, diagnoses why AI chat and agent-driven product experiences break under real-world conditions—network drops, multi-device usage, concurrent agents—and prescribes an architectural fix.
The core idea is that the default pattern of streaming AI responses directly from an agent to a client over a single HTTP connection (typically SSE) is fundamentally fragile. When that connection drops, the stream is lost. A second device cannot see the conversation. The user cannot send a stop or steering signal without ambiguity.
The fix is a Durable Sessions layer: a persistent, shared, independently addressable channel that sits between the agent layer and the client layer. Agents publish events to the session; clients subscribe to the session. Neither holds a direct connection to the other. This single architectural change unlocks three foundational capabilities simultaneously: Resilient Delivery (streams survive disconnections), Continuity Across Surfaces (sessions follow users across tabs and devices), and Live Control (clients can steer, interrupt, or cancel agents mid-generation).
The framework includes a 10-step workflow that starts with auditing your current streaming model, scoring it against the three capabilities, identifying specific failure modes (like the SSE Resume-Cancel Conflict or the Orchestrator Dual-Purpose Problem), and then systematically redesigning the architecture around a pub/sub-based Durable Sessions substrate.
What does the School About Page VSL Framework do?
The School About Page VSL Framework is a conversion copywriting system specifically designed for Skool community About pages. It is derived from an analysis of the top 45 all-time Skool Games leaderboard communities and distills what makes those pages convert cold traffic into paying members.
The framework's central insight is that top-earning Skool communities treat their About page not as a description of what is inside, but as a Video Sales Letter. Every element—copy, graphics, video—exists to sell the offer.
The page is built in four sequential layers: Layer 1 (Gateway) is the short description under 150 characters, optimized for Skool's search discovery. Layer 2 (Sales Page) is the long-form copy structured around the STEP Framework (Hook → Problem Agitation → Value Stack → Proof Stack → Price Anchor → Risk Reversal → Urgency → CTA). Layer 3 (Proof Stack) is a 4–7 image graphics carousel that builds credibility visually. Layer 4 (Closer) is a 2.5–5 minute informal video that names specific member results and closes with a human CTA.
The framework also includes systems for selecting one of 10 Winning Business Models, matching to one of six Price Point Clusters, applying 12 Top Copy Patterns, and auditing against a tiered VSL Elements Checklist.
How do they compare?
They don't compete. These frameworks operate in entirely different domains and solve entirely different problems for entirely different audiences.
The Durable Sessions framework is an engineering architecture framework for AI product teams. It requires knowledge of SSE, WebSockets, pub/sub systems, and agent orchestration patterns. Its output is an infrastructure design. It takes days or weeks to implement.
The School About Page VSL Framework is a marketing and copywriting framework for community builders on Skool. It requires copywriting ability, basic design skills (Canva), and willingness to record a short video. Its output is a complete About page. It takes hours to a few days to execute.
The Durable Sessions framework is clearly better if your problem is AI streaming reliability, multi-device session continuity, or agent control. The VSL framework is clearly better if your problem is converting cold traffic into paid Skool community members. There is no scenario where one substitutes for the other.
Which should you choose?
Choose the Durable Sessions AI UX Framework if you are a software engineer, product architect, or AI product lead and your AI chat or agent experience suffers from any of these symptoms: streams die on disconnect, users cannot see conversations across devices, the stop button is unreliable, or your orchestrator is bogged down relaying sub-agent updates. This is the framework that will fix your real-time AI product infrastructure.
Choose the School About Page VSL Framework if you are a coach, creator, or community operator building or optimizing a Skool community and your About page is not converting. This framework gives you the exact structure, copy patterns, and visual strategy used by the highest-earning communities on the platform.
Choose both if you run an AI-focused Skool community and ship an AI product. Use the VSL framework for your community's About page and the Durable Sessions framework for your product's streaming architecture. They are complementary, not competitive.
// FREQUENTLY ASKED QUESTIONS
Can I use the Durable Sessions framework for a Skool community page?
No. The Durable Sessions framework is an engineering architecture for AI streaming products. It has nothing to do with marketing copy or community pages. For a Skool About page, use the School About Page VSL Framework, which is purpose-built for that exact use case.
Do I need to be a developer to use the School About Page VSL Framework?
No. The VSL framework is designed for non-technical creators, coaches, and community operators. You need copywriting ability, basic Canva skills for the graphics carousel, and the willingness to record a short informal video. No coding, infrastructure, or engineering knowledge is required.
What problem does the Durable Sessions AI UX Framework solve?
It solves the fragility of AI chat streaming experiences. Specifically, it fixes streams that break on network disconnect, sessions that don't carry across devices or tabs, and the inability for users to steer or stop an AI agent mid-response. It replaces the default single-connection model with a persistent shared session layer.
What is the main insight of the School About Page VSL Framework?
The top-earning Skool communities treat their About page as a Video Sales Letter, not a description of what is inside. Every element—copy, graphics, video—is structured to sell the transformation outcome. The framework provides a four-layer system (Gateway, Sales Page, Proof Stack, Closer) modeled on the top 45 Skool communities.
How long does it take to implement the Durable Sessions framework?
Days to weeks, depending on the complexity of your existing architecture. It involves auditing your current streaming model, redesigning the infrastructure to route all agent output through a persistent session layer, replacing SSE with bidirectional transport if live control is needed, and validating three foundational capabilities.
How long does it take to apply the School About Page VSL Framework?
Hours to a few days. The main work is writing the short description (under 150 characters), drafting the long-form sales copy using the STEP Framework, designing 4–7 graphics in Canva, and recording a 2.5–5 minute informal video. Most creators can complete all four layers in a single focused day.
Are there any situations where both frameworks apply to the same project?
Yes, but only if you both ship an AI product and run a Skool community. For example, an AI tool founder who also runs a paid Skool community for their users would use the Durable Sessions framework for the product's streaming architecture and the VSL framework for the community's About page. They solve different problems in different domains.
Which framework is more complex to learn and apply?
The Durable Sessions AI UX Framework is significantly more complex. It requires understanding of SSE, WebSockets, pub/sub patterns, agent orchestration, and real-time infrastructure. The School About Page VSL Framework is more accessible—it requires copywriting skill and basic design ability but no engineering knowledge.