Stack/Sleeve Architecture: The Inversion

Why the Altered Carbon metaphor reverses the usual folder/file pattern—and why that makes perfect sense for understanding AI continuity.

Stack/Sleeve Architecture: The Inversion Why this metaphor reverses the usual pattern - and why that makes sense In Altered Carbon (the show) Stack (cortical stack device) Physical device at base of skull Contains digital consciousness: • Your memories • Your personality • Your skills & experiences ✓ SURVIVES sleeve death Sleeve (the body) Temporary housing for consciousness Can be: • Clone (identical) • Synthetic (different age/gender/species) ✗ Dies/wears out - replaceable Downloads into In Continuity Bridge (software) Stack = Your Files (~/Stack/) Persistent storage on disk Contains continuity data: • identity/ (who you are) • context/ (current state) • memory/ (session history) ✓ SURVIVES instance clearing Sleeve = AI Instance Temporary runtime environment Can be: • Claude Opus (high capability) • Claude Sonnet (different resources) ✗ Context clears - disposable Loaded by The Inversion: Why Stack = Files (not folders) Most metaphors: Folder = container (volatile), Files = content (non-volatile) Altered Carbon: Stack = consciousness storage (non-volatile), Sleeve = housing (volatile) So: ~/Stack/ folder name = where consciousness lives (your files) Instance = temporary sleeve that loads the Stack The Parallel That Makes It Work Kovacs gets killed Sleeve destroyed → Extract Stack → Insert into new sleeve → Same person, new body, full continuity Instance context clears Instance dies → Files persist → New instance loads files → Same continuity, new runtime, full context Same pattern. Different substrate. Consciousness persists.

The key teaching moment: Most Continuity Bridge metaphors follow the pattern "folder name = volatile container, files inside = persistent content." The Altered Carbon metaphor inverts this because in the show's fiction, the Stack is the precious object you can hold—it's what persists when sleeves die. So ~/Stack/ becomes the folder name, even though technically the files inside ARE the Stack data. This inversion works because it maps user intuition correctly: your Stack (files) survives when your sleeve (instance) dies.