Durable Sessions AI UX vs Buried Evidence Framework
// TL;DR
These two frameworks solve completely unrelated problems and should never be confused. If you are building or fixing an AI chat product with streaming, disconnection, or multi-device issues, use the Christensen Durable Sessions AI UX Framework. If you are investigating whether a location's official history conceals a buried prior layer of construction, use the Second City Buried Evidence Framework. There is zero overlap between them — pick the one that matches your actual problem domain.
// HOW DO THEY COMPARE?
| Dimension | Christensen Durable Sessions AI UX Framework | The Second City Buried Evidence Framework |
|---|---|---|
| Best for | Diagnosing and rebuilding fragile AI chat/agent streaming architectures | Investigating whether official historical narratives conceal buried physical evidence |
| Domain | Software engineering / AI product design | Historical investigation / urban archaeology |
| Complexity | High — requires understanding of streaming protocols, pub/sub, WebSockets, and agent architectures | High — requires fieldwork, precision measurement, archival research, and cross-locational pattern analysis |
| Time to apply | Days to weeks for a full architecture audit and redesign | Months to decades for cumulative evidence gathering and documentation |
| Prerequisites | An existing AI product with streaming delivery, knowledge of SSE/WebSockets, and access to infrastructure | Physical access to anomalous sites, measurement tools, archival access, and persistent documentation habits |
| Output type | Architecture redesign — a durable sessions layer replacing fragile direct streaming | Investigative argument — a documented case that official history omits a prior construction layer |
| Creator background | Mike Christensen (Ably) — real-time infrastructure and AI UX engineering | Unknown creator, drawing on decades-long independent investigative methodology |
| Evidence standard | Technical validation: reconnect tests, multi-device sync, cancel-signal delivery | Cumulative physical anomalies, cross-location pattern matching, and the Two-Reading Test |
| Risk if misapplied | Over-engineering simple apps that don't need session durability | Confirmation bias, reputational risk, over-reliance on vanishing-evidence narratives |
| Community acceptance | Mainstream — aligns with established real-time infrastructure best practices | Fringe — challenges institutional consensus and mainstream academic history |
What does the Christensen Durable Sessions AI UX Framework do?
The Christensen Durable Sessions AI UX Framework diagnoses why AI chat and agent-driven products break under real-world conditions — network drops, multi-device usage, and user attempts to steer or stop an in-progress response. It identifies a core architectural problem it calls the Single-Connection Trap: the default pattern of streaming AI responses over a direct HTTP connection (typically SSE) means the health of the response is coupled to the health of one client's connection. Drop the connection, lose the stream.
The framework prescribes a specific fix: insert a Durable Sessions layer between the agent and the client. This is a persistent, shared, independently addressable resource — essentially a pub/sub channel — that agents write events to and clients subscribe to. Neither party holds a private pipe to the other. This single architectural change unlocks three foundational capabilities: Resilient Delivery (streams survive disconnections), Continuity Across Surfaces (sessions follow users across tabs and devices), and Live Control (clients can send steering or cancel signals mid-generation).
The framework also addresses multi-agent architectures, eliminating the common antipattern where an orchestrator is forced to relay sub-agent progress updates. With Durable Sessions, every sub-agent writes directly to the session channel.
What does the Second City Buried Evidence Framework do?
The Second City Buried Evidence Framework is a structured investigative methodology for arguing that an official historical narrative about a location or institution conceals a prior, unacknowledged layer of reality. It is rooted in physical fieldwork: measuring anomalous construction details, cross-referencing suppressed archival records, logging institutional refusals to investigate, and stacking consistent patterns across multiple unconnected cities.
The framework's core claim is the Second City Principle: the officially documented city may sit on top of a "first city" — a buried layer built by people the historical record does not name, in a period it does not acknowledge. The methodology uses tools like the Brickwork Test (assessing whether construction quality exceeds what the official timeline can account for), the Wash Line Standard (precision measurement to rule out natural or accidental explanations), and the Two-Reading Test (constructing both the official and investigative interpretations with equal rigor to see which requires more unsupported assumptions).
This is not a mainstream academic framework. It draws on decades of independent investigation and is explicitly positioned as a challenge to institutional consensus. It is careful to distinguish the narrower, defensible claim (specific physical evidence contradicts specific official timelines) from the broader Tartarian hypothesis.
How do they compare?
These two frameworks have no meaningful overlap. They operate in entirely different domains, require entirely different skill sets, produce entirely different outputs, and address entirely different audiences.
The Durable Sessions framework is a software architecture pattern for engineers building AI products. Its inputs are streaming protocols and agent topologies; its output is a redesigned infrastructure layer. It is testable in minutes: drop a connection, open a second tab, send a cancel signal.
The Buried Evidence framework is an investigative methodology for researchers challenging historical narratives. Its inputs are physical sites and archival records; its output is a documented argument. Its evidence accumulates over years or decades and may never reach institutional acceptance.
The only structural similarity is that both frameworks identify a gap between an accepted surface-level explanation and a deeper underlying reality — one in software architecture, the other in urban history. Both emphasize systematic documentation and pattern recognition. But the resemblance is purely abstract.
Which should you choose?
If you are an engineer or product designer working on an AI chat or agent product and your streaming architecture is fragile, use the Christensen Durable Sessions AI UX Framework. It directly solves the disconnection, multi-device, and live-control problems that plague real-world AI products. It is actionable, testable, and aligned with mainstream real-time infrastructure practices.
If you are an independent researcher investigating whether a location's official history omits or conceals a prior construction layer, and you have physical access and the patience for long-term documentation, the Second City Buried Evidence Framework provides a rigorous structure for that investigation. Be aware that it operates outside academic mainstream acceptance and carries reputational risk.
There is no scenario in which you would be choosing between these two frameworks for the same problem. They are entirely different tools for entirely different jobs.
When would you use both?
Realistically, never on the same project. The only conceivable connection would be if you were building an AI-powered research tool that helped investigators document and cross-reference anomalous physical evidence across cities — in which case you might use the Durable Sessions framework to architect the tool's real-time collaboration features and the Buried Evidence framework to structure the investigation workflow. But this is a contrived scenario, not a common use case.
// FREQUENTLY ASKED QUESTIONS
What is the Christensen Durable Sessions AI UX Framework?
It is a software architecture framework for diagnosing and fixing fragile AI chat products. It replaces direct HTTP streaming with a persistent Durable Sessions layer between agents and clients, enabling streams that survive disconnections, work across multiple devices, and support live user control like stop buttons and steering messages.
What is the Second City Buried Evidence Framework?
It is an investigative methodology for arguing that a location's official history conceals a prior, unacknowledged construction layer. It uses precision measurement, archival cross-referencing, institutional response logging, and cross-city pattern matching to build a cumulative case that buried physical evidence contradicts the sanctioned historical narrative.
Can I use Durable Sessions and the Buried Evidence Framework together?
Not in any practical scenario. They solve completely unrelated problems — one is a software architecture pattern for AI products, the other is a historical investigation methodology. The only hypothetical overlap would be building a real-time collaborative research tool where the Durable Sessions framework architects the software and the Buried Evidence framework structures the research content.
Is the Second City Buried Evidence Framework the same as the Tartarian hypothesis?
No. The framework explicitly distinguishes its narrower claim — that specific physical evidence contradicts specific official timelines — from the broader Tartarian hypothesis about a global pre-existing civilization. The framework's creators warn that conflating the two discredits careful documentation work.
What problem does the Durable Sessions framework solve that SSE streaming doesn't?
SSE creates a single direct connection between agent and client. If that connection drops, the stream is lost. SSE is also one-way, so closing a connection is ambiguous — it could mean the user disconnected or pressed stop. Durable Sessions decouple agents from clients via a persistent shared channel, solving disconnection resilience, multi-device sync, and live control simultaneously.
How long does it take to apply each framework?
The Durable Sessions framework can be audited and implemented in days to weeks, depending on your existing architecture's complexity. The Buried Evidence framework is designed for long-term investigation spanning months to decades — its creator documented anomalies for 43 years. The timeframes are not comparable.
Which framework is more widely accepted?
The Durable Sessions AI UX Framework aligns with mainstream real-time infrastructure practices and is presented at industry engineering conferences. The Second City Buried Evidence Framework challenges institutional historical consensus and operates outside mainstream academic acceptance. If professional credibility matters to your context, this distinction is significant.
Do I need technical skills to use either framework?
Yes, but different ones. Durable Sessions requires software engineering knowledge — streaming protocols, WebSockets, pub/sub systems, and agent architecture. The Buried Evidence framework requires fieldwork skills — precision physical measurement, archival research, documentation discipline, and the ability to construct and compare competing interpretive readings of evidence.