From Hydration to Resumability
Learn how the concept of "resumability" from web frameworks like Qwik can revolutionize how AI systems manage cognitive state.
The Problem with Traditional AI
Hydration (Current)
Replay-based approach
Resumability (Future)
Restore-based approach
The Continuation Record (CR)
The CR is the fundamental artifact that enables cross-agent resumability—capturing not just state, but the full context needed for any thinking agent to continue work seamlessly.
CR Structure
ContinuationRecord {
// Identity & Audit Trail
id, version, contentHash
parentCRHash, merkleRoot
// Task Definition
task { goal, successCriteria, status }
// Execution Summary
executionSummary {
stepsCompleted, tokensConsumed
}
// Decisions & Learnings
decisions: CRDecision[]
learnings: CRLearning[]
// Human Interaction
questionsForUser: CRQuestion[]
blockers: CRBlocker[]
resumePoints: CRResumePoint[]
// Tool Effects (idempotency)
toolEffects: CRToolEffect[]
}Key Properties
CR Components
The building blocks that make up a Continuation Record
Resume Points
Explicit continuation gates with preconditions, authority requirements, and approval tracking. Define when and how work can continue.
CRResumePointDecisions
Tracked choices with status (tentative/accepted/rejected/contested), rationale, and the ability to be overridden by humans.
CRDecisionQuestions
Human intervention requests: questions for clarification, approvals needed, override requests, or scope changes.
CRQuestionLearnings
Insights, constraints, patterns, and warnings captured during execution. Can come from observation, failure, success, or feedback.
CRLearningTool Effects
Record of tool invocations with inputs, outputs, idempotency keys, and whether they're replayable. Prevents duplicate side effects.
CRToolEffectBlockers
Obstacles preventing progress: missing info, permissions needed, dependencies, errors, or human-required decisions.
CRBlockerTwo-Layer Architecture
How internal reasoning state relates to the external handoff artifact
Internal State
How AI thinks
CognitiveNodeIndividual reasoning steps
EpistemicStateFacts, beliefs, questions
IntentGraphGoals hierarchy
External Artifact
What gets shared
ContinuationRecordComplete handoff package
CognitiveNode (Internal)
- • Fine-grained reasoning steps
- • Ephemeral processing state
- • Graph of thoughts with dependencies
- • Used during active execution
ContinuationRecord (External)
- • Structured handoff artifact
- • Persistent, serializable, portable
- • Hash-linked audit trail
- • Agent-agnostic: any AI or human can resume
"The future isn't better prompts. It's persistent, resumable cognition."
Benefits of the CR System
90%+ Token Savings
Restore from a CR instead of replaying conversation history. A 45,000 token context rebuild becomes ~1,200 tokens to load.
Near-Instant Resume
The CR contains everything needed: decisions made, questions answered, tool effects recorded. No re-derivation needed.
Multi-Agent Handoff
Pass a CR between GPT-4, Claude, human reviewers, or deterministic systems. The CR is agent-agnostic.
Hash-Linked Audit Trail
Each CR links to its parent via contentHash. Fork, branch, and merge reasoning paths with full provenance.
Human-in-the-Loop Built In
CRQuestion for clarification, CRResumePoint for approvals, CRDecision overrides—all first-class citizens.
Idempotent Tool Execution
CRToolEffect tracks what ran, with idempotency keys. Safe to resume without re-executing side effects.
Dive Deeper
Explore the full CR type system, real examples, and hands-on code
Playground
Interactive CR viewer—create, modify, and explore Continuation Records
Implementation
Full TypeScript types, CRStore interface, and integration patterns
Examples
Real-world scenarios: OAuth implementation, research synthesis, support agent
Research
Academic foundations: CPS, process checkpointing, KV-cache
Challenges
What can't be serialized, staleness, security, versioning
Compare
Side-by-side hydration vs resumability with token/cost analysis
Try It Yourself
Explore the interactive demo to see resumability in action