Unclassified
21 · Memory & Continuity
Three domains: Organizational Memory (THE memory) → Personal Contextual → AI Continuity. Ownership, privacy, durability, retrieval, promotion, rehydration, and G-10.
Three Domains, One Invariant
Organizational Memory THE memory (Business Context Spine)
│
│ shared business reality
│
┌──────┴──────┐
▼ ▼
Personal AI
Contextual Continuity
Memory Memory
(serves BC) (serves BC)
Organizational Memory is THE memory. Personal Contextual Memory and AI Continuity Memory are working continuities that serve Business Context — they are not equal peers.
User thought ≠ AI inference ≠ Organizational truth
Ownership & Boundaries
| Domain | Owner | Durable? | Becomes Organizational truth when… | Privacy |
|---|---|---|---|---|
| Organizational Memory | Organization / tenant | ✅ | Governed promotion → verify → reconcile → Spine | Tenant-isolated, projection-governed |
| Personal Contextual Memory | Human | Per-user working continuity | Deliberately shared and governed — not silent promotion | Private to user unless shared |
| AI Continuity Memory | AI Workbench / Twin / agent | Working continuity (see G-10) | Promotion via Triage / Governance / governed write — never by inference alone | Tenant- and Work-scoped, auditable |
Lifecycle
- Retrieval — rehydration from Spine + working memory scoped to Work.
- Promotion — working items (personal notes, AI inferences) become organizational memory only through explicit governed path; see Ingestion & Normalization and Verification & Reconciliation.
- Rehydration — after Spine update, projections invalidate and both Human Workbench and AI Workbench refresh from new truth.
- Durability — organizational memory is durable across sessions, devices, and agents; working memories are scoped to continuity needs, not indefinite lakes.
G-10: AI Continuity Persistence
G-10: AI Continuity Memory has a defined semantic scope but its persistent backing substrate remains an architecture decision.
This is the explicit gap register entry: what AI Continuity means is canonical; where/how it is persisted (store, cache vs substrate, lifecycle) is still a decision. The invariant is: whatever the substrate, it serves Organizational Memory, never replaces it.
Where to Go Next
<CardGroup cols={2}>How memory updates are tied to verified execution, not to AI output.
How working memory contributes to the Active Context Bundle.
Shared context, separate continuity — in the human experience.