{"slug":"platform/07-memory-system","title":"07 — Memory System","section":"platform","sectionLabel":"Platform","status":"unclassified","type":"document","path":"platform/07-memory-system.mdx","bytes":1999,"description":null,"updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"\n> **Extracted from:** IntegrateWise Platform Specification Suite\n> **Region:** first_pass\n> **Original line:** 893\n> **Lines:** 36 | **Chars:** 1,752\n> **Status:** Raw extraction — requires review and canonicalization\n\n07 — Memory System\n7.1 Responsibilities\nOwn the 8-layer memory pipeline (already defined in existing spec).\nBind three-axis separation: Spine (truth), Memory (meaning), Knowledge (docs).\nOperate the Promotion Queue as the human-in-the-loop gate.\n7.2 The eight layers (preserved and made deterministic)\nCopyL1 Twin Memory — conversational working memory (ephemeral, ≤10 turns)\nL2 Memory Intake — raw observations, immutable for 24h\nL3 Triage Bot — classification (fact | decision | observation | relationship | noise)\nL4 Memory Evolution — pattern detection (cluster, dedupe, propose promotion)\nL5 Promotion Queue — staging surface (single most important screen)\nL6 Human Approval — gating event (MemoryApproved | MemoryRejected)\nL7 Organizational Memory — durable, indexed, queryable\nL8 Knowledge — SOPs, playbooks, runbooks (curated from L7 + human authored)\n7.3 Inputs\nTwinMemoryIntake events (from 06).\nManual memory creation (Admin).\nKnowledge imports (Markdown, Docs).\n7.4 Outputs\nPromotion Queue items.\nL7 search hits (mem.search(“…”)).\nKnowledge article refs.\n7.5 Events\nProduced: MemoryTriaged, MemoryPromoted, MemoryApproved, MemoryRejected, MemoryDeprecated, KnowledgeArticlePublished.\nConsumed: TwinMemoryIntake, EntityUpdated (to evolve), AdminMemoryEdited.\n7.6 APIs\nPOST /memory/intake, GET /memory/promotion-queue, POST /memory/{mem_id}/approve, POST /memory/{mem_id}/reject, GET /memory/search.\n7.7 State transitions\nintake → triaged → cluster → queued_for_promotion → approved | rejected → deprecated.\n\n7.8 Failure handling\nTriage bot mis-classifies → user may re-tag (human-in-the-loop).\nStuck queue → admin SLA alert (16).\n7.9 Extension points\nCustom Triage Bot rules.\nCustom Evolution patterns.\n"}