Authoritative architecture and public boundary: server composition, execution lifecycle, subsystem nodes, and managed cloud boundary.
Simplified Architecture: The 7-Stage Memory Pipeline
XMemo processes agent memories through a 7-stage pipeline (Capture → Scope → Retrieve → Rerank → Assemble → Govern → Consolidate). Each stage performs a dedicated responsibility to ensure memory operations remain fast, accurate, boundary-isolated, and verifiable:
- Capture: Receives memory write and update requests from your AI clients over standard Model Context Protocol (MCP) or REST APIs, and sanitizes sensitive data before anything is stored. What this means for you: Your agents can save notes, decisions, and preferences automatically through standard tools without exposing secrets or personal data.
- Scope: Resolves caller identity context and enforces strict multi-tenant boundaries across user, session, agent, and workspace tiers. What this means for you: Each agent only accesses memory within its authorized boundary, keeping personal and team data securely separated.
- Retrieve: Searches stored memories using a hybrid retrieval engine that combines vector semantic embeddings with exact keyword matching. What this means for you: Your agent recalls the right facts whether searching by topic meaning or looking up an exact phrase or identifier.
- Rerank: Evaluates and scores candidate memories by balancing semantic relevance, recency, and importance weights. What this means for you: Your agent receives the most relevant and up-to-date context rather than stale or low-priority conversation fragments.
- Assemble: Packages recalled memories into prompt-ready context while strictly enforcing caller token and byte budgets. What this means for you: Injected memory never overflows your model's context window or runs up unexpected prompt token costs.
- Govern: Records operational audit logs, tracks version history (memory_versions), and applies encryption envelopes when keyguard/vault mode is active. What this means for you: Every memory update is traceable, verifiable, and recoverable with complete audit accountability.
- Consolidate: Runs background reflection (Dream) to synthesize episodic interactions into durable semantic knowledge, governed by workspace plan and schedule presets. What this means for you: High-value patterns and long-term knowledge evolve automatically over time without slowing down interactive agent chats.
Architecture internals / Evidence
Authoritative architectural implementation details, execution traces, and empirical contracts verified directly against the XMemo codebase. The following sections document concrete runtime composition, isolated subsystem boundaries, and formal verification matrices.
Architectural Invariants & Core Principles
XMemo enforces non-negotiable architectural invariants separating public client surfaces from internal subsystem execution. Operational capabilities are bound to real source evidence, while confidential topology, database credentials, and cluster keys remain strictly protected under zero plaintext secret exposure.
- Zero Plaintext Secret Exposure: Client configuration files, logs, and public diagnostic responses never contain unencrypted bearer tokens, database connection strings, or master keys.
- Verified Source Provenance: Every persisted memory, version revision, and retrieval citation carries immutable identity metadata and audit trails bound to source code contracts.
- Deterministic Token & Byte Budgets: Recall context injection strictly respects caller-specified limits, preventing LLM context window overflow.
- Plan & Feature-Gate Boundaries: Multi-tenant BYODB, distributed sync, and background Dream scheduling are gated behind explicit workspace configurations, feature flags, and plan boundaries.
Server Composition & Lifecycle Topology
Server initialization decouples deployment-time composition and tool registration from per-request runtime execution traces. External clients do not mount the host server; rather, the host server mounts the FastMCP ASGI application, adapts it via MemoryOSMcpMountAdapter, and registers authenticated tool handlers with FastMCP before any request is received.
- Step 1 [HOST_COMPOSITION]: Host Starlette/FastAPI server mounts the FastMCP ASGI app at /mcp — Relation: SERVER_MOUNTS_APP — Subsystem: ASGI Server Mount — Boundary: Public HTTP Ingress.
- Step 2 [MOUNT_ADAPTER]: mount_streamable_mcp wraps streamable_http_app in MemoryOSMcpMountAdapter to handle CORS, SSE probes, and scope rewriting — Relation: ADAPTS_ASGI_APP — Subsystem: Streamable Protocol Adapter — Boundary: Protocol Bridge.
- Step 3 [AUTH_REGISTRATION]: install_mcp_tool_surface registers _call_tool_with_oauth_errors as the mcp._mcp_server.call_tool handler on the FastMCP low-level server — Relation: REGISTERS_TOOL_WRAPPER — Subsystem: Identity & Tool Dispatch Gate — Boundary: Authenticated Tool Surface.
+---------------------------------------------------------------------------------------------------+
| [DEPLOYMENT-TIME SERVER COMPOSITION & TOPOLOGY: 2 INDEPENDENT BRANCHES] |
| |
| [BRANCH 1: SERVER ASGI MOUNT BRANCH] |
| +-------------------------------------------------------+ |
| | Host ASGI Server (Starlette / FastAPI) | [PUBLIC_BOUNDARY] |
| | Role: FastMCP Host Ingress Gateway | [PUBLIC_BOUNDARY] |
| +-------------------------------------------------------+ |
| | |
| | Relation: SERVER_MOUNTS_APP |
| | Status: [PUBLIC_BOUNDARY (VERIFIED)] |
| v |
| +-------------------------------------------------------+ |
| | mount_streamable_mcp | [INTERNAL_SUBSYSTEM] |
| | Role: Streamable HTTP Application Adapter | [INTERNAL_SUBSYSTEM] |
| +-------------------------------------------------------+ |
| | |
| | Relation: ADAPTS_ASGI_APP |
| | Status: [INTERNAL_SUBSYSTEM (VERIFIED)] |
| v |
| +-------------------------------------------------------+ |
| | MemoryOSMcpMountAdapter | [PUBLIC_BOUNDARY] |
| | Role: ASGI Protocol Bridge & Connection Handler | [PUBLIC_BOUNDARY] |
| +-------------------------------------------------------+ |
| |
| [BRANCH 2: TOOL SURFACE REGISTRATION BRANCH] |
| +-------------------------------------------------------+ |
| | install_mcp_tool_surface | [INTERNAL_SUBSYSTEM] |
| | Role: MCP Tool Surface Registration Pipeline | [INTERNAL_SUBSYSTEM] |
| +-------------------------------------------------------+ |
| | |
| | Relation: REGISTERS_TOOL_WRAPPER |
| | Status: [INTERNAL_SUBSYSTEM (VERIFIED)] |
| v |
| +-------------------------------------------------------+ |
| | FastMCP Tool Ingress Wrapper (_call_tool_with_oauth) | [PUBLIC_BOUNDARY] |
| | Role: Authenticated Tool Invocation & Error Handler | [PUBLIC_BOUNDARY] |
| +-------------------------------------------------------+ |
+---------------------------------------------------------------------------------------------------+
Runtime Execution Traces
At runtime, client requests execute across four isolated, deterministic operation flows. Every step is governed by strict caller-callee relations and explicit architectural boundary classifications:
- OP_REMEMBER_WRITE [Remember / Write Trace: 13 steps]: External Client [PUBLIC_INGRESS] -> MemoryOSMcpMountAdapter [TRANSPORT_ADAPTER] -> FastMCP ASGI Dispatch -> Tool Surface Auth Gate -> remember Tool Surface -> Setup Verification Gate -> PII Sanitization Envelope -> Security Envelope (encryption when keyguard/vault mode is active) -> Persistence Engine. Relations: 13 verified steps across protocol ingress, authorization, redaction, security envelope, and persistence.
- OP_RECALL_READ [Recall / Read Trace: 12 steps]: External Client [PUBLIC_INGRESS] -> MemoryOSMcpMountAdapter [TRANSPORT_ADAPTER] -> FastMCP ASGI Dispatch -> Tool Surface Auth Gate -> recall Tool Surface -> BoundSpace Multi-Tenant Isolation -> Hybrid Retrieval Engine -> Semantic Candidate Reranker -> Context Budget Assembler -> Public Citation Formatter. Relations: 12 verified steps across retrieval, isolation, ranking, budget, and citation.
- OP_UPDATE_VERSION [Update / Versioning Trace: 13 steps]: External Client [PUBLIC_INGRESS] -> MemoryOSMcpMountAdapter [TRANSPORT_ADAPTER] -> FastMCP ASGI Dispatch -> Tool Surface Auth Gate -> update_memory Tool Surface -> Setup Verification Gate -> PII Sanitization Envelope -> Security Envelope (encryption when keyguard/vault mode is active) -> Persistence Engine -> Version History Controller (Immutable DAG Supersession). Relations: 13 verified steps across validation, redaction, update, and DAG supersession.
- OP_FORGET_LIFECYCLE [Forget / Lifecycle Trace: 11 steps]: External Client [PUBLIC_INGRESS] -> MemoryOSMcpMountAdapter [TRANSPORT_ADAPTER] -> FastMCP ASGI Dispatch -> Tool Surface Auth Gate -> forget Tool Surface -> Setup Verification Gate -> Soft Tombstone Persistence -> Background Retention Daemon -> Search Engine Query Exclusion. Relations: 11 verified steps across deletion, tombstone, and retention.
+------------------------------------------------------------------------------------------------------------------------+
| [RUNTIME EXECUTION TRACES: 4 CANONICAL OPERATION FLOW DIAGRAMS] |
| |
| 1. OP_REMEMBER_WRITE [WRITE INGRESS FLOW: 13 STEPS] |
| Step 1: External Client --[CLIENT_REQUESTS_ENDPOINT]--> MemoryOSMcpMountAdapter |
| Boundary: Public Ingress Gateway [PUBLIC_BOUNDARY] |
| Step 2: MemoryOSMcpMountAdapter --[DELEGATES_ASGI_REQUEST]--> FastMCP.streamable_http_app |
| Boundary: ASGI Streamable Mount Adapter [INTERNAL_SUBSYSTEM] |
| Step 3: FastMCP --[DISPATCHES_TOOL_INVOCATION]--> _call_tool_with_oauth_errors |
| Boundary: Tool Surface Ingress Gate [INTERNAL_SUBSYSTEM] |
| Step 4: _call_tool_with_oauth_errors --[DISPATCHES_TOOL]--> remember tool |
| Boundary: MCP Tool Dispatch Handler [PUBLIC_BOUNDARY] |
| Step 5: remember tool --[CALLS]--> Identity Context Resolver |
| Boundary: Identity & Authentication Context [INTERNAL_SUBSYSTEM] |
| Step 6: remember tool --[CALLS]--> Workspace Setup Gate |
| Boundary: Workspace Initialization Gate [INTERNAL_SUBSYSTEM] |
| Step 7: Workspace Setup Gate --[CALLS]--> Initialization Validator |
| Boundary: Setup Verification Gate [INTERNAL_SUBSYSTEM] |
| Step 8: remember tool --[CALLS]--> Write Preparation Pipeline |
| Boundary: Memory Write Preparation [INTERNAL_SUBSYSTEM] |
| Step 9: Write Preparation Pipeline --[CALLS]--> PII Sanitization Envelope |
| Boundary: Sensitive Data Redaction [INTERNAL_SUBSYSTEM] |
| Step 10: Write Preparation Pipeline --[CALLS]--> Security Envelope (encryption when keyguard/vault mode is active)|
| Boundary: Cryptographic Security Envelope [INTERNAL_SUBSYSTEM] |
| Step 11: remember tool --[CALLS]--> Tenant Isolation Envelope |
| Boundary: Multi-Tenant Workspace Binding [INTERNAL_SUBSYSTEM] |
| Step 12: remember tool --[CALLS]--> Memory Manager Core Engine |
| Boundary: Core Memory Management [INTERNAL_SUBSYSTEM] |
| Step 13: Memory Manager Core Engine --[CALLS]--> Persistence Storage Engine |
| Boundary: Persistent Storage Engine [INTERNAL_SUBSYSTEM] |
| |
| 2. OP_RECALL_READ [READ RETRIEVAL FLOW: 12 STEPS] |
| Step 1: External Client --[CLIENT_REQUESTS_ENDPOINT]--> MemoryOSMcpMountAdapter |
| Boundary: Public Ingress Gateway [PUBLIC_BOUNDARY] |
| Step 2: MemoryOSMcpMountAdapter --[DELEGATES_ASGI_REQUEST]--> FastMCP.streamable_http_app |
| Boundary: ASGI Streamable Mount Adapter [INTERNAL_SUBSYSTEM] |
| Step 3: FastMCP --[DISPATCHES_TOOL_INVOCATION]--> _call_tool_with_oauth_errors |
| Boundary: Tool Surface Ingress Gate [INTERNAL_SUBSYSTEM] |
| Step 4: _call_tool_with_oauth_errors --[DISPATCHES_TOOL]--> recall tool |
| Boundary: MCP Tool Dispatch Handler [PUBLIC_BOUNDARY] |
| Step 5: recall tool --[CALLS]--> Search Memory Implementation |
| Boundary: Search Query Coordinator [INTERNAL_SUBSYSTEM] |
| Step 6: Search Memory Implementation --[CALLS]--> Identity Context Resolver |
| Boundary: Identity & Authentication Context [INTERNAL_SUBSYSTEM] |
| Step 7: Search Memory Implementation --[CALLS]--> BoundSpace Multi-Tenant Isolation |
| Boundary: Scope Isolation Boundary [INTERNAL_SUBSYSTEM] |
| Step 8: Search Memory Implementation --[CALLS]--> Memory Manager Search Service |
| Boundary: Core Search Controller [INTERNAL_SUBSYSTEM] |
| Step 9: Memory Manager Search Service --[CALLS]--> Hybrid Retrieval Engine |
| Boundary: Hybrid Vector & Text Retrieval [INTERNAL_SUBSYSTEM] |
| Step 10: Hybrid Retrieval Engine --[CALLS]--> Semantic Relevance Reranker |
| Boundary: Candidate Scorer & Reranker [INTERNAL_SUBSYSTEM] |
| Step 11: Hybrid Retrieval Engine --[CALLS]--> Response Budget Assembler |
| Boundary: Token & Byte Budget Manager [INTERNAL_SUBSYSTEM] |
| Step 12: Response Budget Assembler --[CALLS]--> Public Citation & Receipt Formatter |
| Boundary: Provenance Citation Formatter [PUBLIC_BOUNDARY] |
| |
| 3. OP_UPDATE_VERSION [VERSIONING & CORRECTION FLOW: 13 STEPS] |
| Step 1: External Client --[CLIENT_REQUESTS_ENDPOINT]--> MemoryOSMcpMountAdapter |
| Boundary: Public Ingress Gateway [PUBLIC_BOUNDARY] |
| Step 2: MemoryOSMcpMountAdapter --[DELEGATES_ASGI_REQUEST]--> FastMCP.streamable_http_app |
| Boundary: ASGI Streamable Mount Adapter [INTERNAL_SUBSYSTEM] |
| Step 3: FastMCP --[DISPATCHES_TOOL_INVOCATION]--> _call_tool_with_oauth_errors |
| Boundary: Tool Surface Ingress Gate [INTERNAL_SUBSYSTEM] |
| Step 4: _call_tool_with_oauth_errors --[DISPATCHES_TOOL]--> update_memory tool |
| Boundary: MCP Tool Dispatch Handler [PUBLIC_BOUNDARY] |
| Step 5: update_memory tool --[CALLS]--> Identity Context Resolver |
| Boundary: Identity & Authentication Context [INTERNAL_SUBSYSTEM] |
| Step 6: update_memory tool --[CALLS]--> Workspace Setup Gate |
| Boundary: Workspace Initialization Gate [INTERNAL_SUBSYSTEM] |
| Step 7: update_memory tool --[CALLS]--> Scope Validation Gate |
| Boundary: Workspace Scope Boundary [INTERNAL_SUBSYSTEM] |
| Step 8: update_memory tool --[CALLS]--> Write Preparation Pipeline |
| Boundary: Memory Write Preparation [INTERNAL_SUBSYSTEM] |
| Step 9: Write Preparation Pipeline --[CALLS]--> PII Sanitization Envelope |
| Boundary: Sensitive Data Redaction [INTERNAL_SUBSYSTEM] |
| Step 10: update_memory tool --[CALLS]--> Tenant Isolation Envelope |
| Boundary: Multi-Tenant Workspace Binding [INTERNAL_SUBSYSTEM] |
| Step 11: update_memory tool --[CALLS]--> Memory Manager Core Engine |
| Boundary: Core Memory Management [INTERNAL_SUBSYSTEM] |
| Step 12: Memory Manager Core Engine --[CALLS]--> Persistence Storage Engine |
| Boundary: Persistent Storage Engine [INTERNAL_SUBSYSTEM] |
| Step 13: Persistence Storage Engine --[CALLS]--> Immutable Version DAG Controller |
| Boundary: Version DAG Supersession Engine [INTERNAL_SUBSYSTEM] |
| |
| 4. OP_FORGET_LIFECYCLE [RETENTION & LIFECYCLE FLOW: 11 STEPS] |
| Step 1: External Client --[CLIENT_REQUESTS_ENDPOINT]--> MemoryOSMcpMountAdapter |
| Boundary: Public Ingress Gateway [PUBLIC_BOUNDARY] |
| Step 2: MemoryOSMcpMountAdapter --[DELEGATES_ASGI_REQUEST]--> FastMCP.streamable_http_app |
| Boundary: ASGI Streamable Mount Adapter [INTERNAL_SUBSYSTEM] |
| Step 3: FastMCP --[DISPATCHES_TOOL_INVOCATION]--> _call_tool_with_oauth_errors |
| Boundary: Tool Surface Ingress Gate [INTERNAL_SUBSYSTEM] |
| Step 4: _call_tool_with_oauth_errors --[DISPATCHES_TOOL]--> forget tool |
| Boundary: MCP Tool Dispatch Handler [PUBLIC_BOUNDARY] |
| Step 5: forget tool --[CALLS]--> Identity Context Resolver |
| Boundary: Identity & Authentication Context [INTERNAL_SUBSYSTEM] |
| Step 6: forget tool --[CALLS]--> Workspace Setup Gate |
| Boundary: Workspace Initialization Gate [INTERNAL_SUBSYSTEM] |
| Step 7: forget tool --[CALLS]--> Memory Manager Core Engine |
| Boundary: Core Memory Management [INTERNAL_SUBSYSTEM] |
| Step 8: Memory Manager Core Engine --[CALLS]--> Persistence Storage Engine |
| Boundary: Persistence Tombstone Engine [INTERNAL_SUBSYSTEM] |
| Step 9: Background Lifecycle Daemon --[BATCH_POLICY_EVALUATION]--> Retention Policy Evaluator |
| Boundary: Archive Policy Evaluation [INTERNAL_SUBSYSTEM] |
| Step 10: Background Lifecycle Daemon --[BATCH_POLICY_EVALUATION]--> Importance Decay Evaluator |
| Boundary: Importance Decay Engine [INTERNAL_SUBSYSTEM] |
| Step 11: Hybrid Retrieval Engine --[EXCLUDES_AT_QUERY]--> Database Storage Engine |
| Boundary: Query-Time Tombstone Filter [INTERNAL_SUBSYSTEM] |
+------------------------------------------------------------------------------------------------------------------------+
Subsystem Decomposition & Boundary Classification
The system decomposes into ten verified subsystem nodes. Each node carries a strict boundary classification (PUBLIC_BOUNDARY or INTERNAL_SUBSYSTEM) and an empirical evidence status (SOURCE_BACKED_PUBLIC_CONTRACT / VERIFIED, CONCEPTUAL_DELEGATED, or NOT_VERIFIED):
- NODE_1_CLIENT_AGENT_LAYER: Client & Agent Ecosystem (@xmemo/client, Claude Desktop, Cursor, Codex) — Classification: [PUBLIC_BOUNDARY] — Evidence Status: [SOURCE_BACKED_PUBLIC_CONTRACT (VERIFIED)].
- NODE_2_TRANSPORT_ADAPTER: MCP Transport & Protocol Adapter (MemoryOSMcpMountAdapter, mount_streamable_mcp) — Classification: [PUBLIC_BOUNDARY] — Evidence Status: [SOURCE_BACKED_PUBLIC_CONTRACT (VERIFIED)].
- NODE_3_IDENTITY_AUTH_GATE: Identity & Authorization Gate (_call_tool_with_oauth_errors, install_mcp_tool_surface) — Classification: [PUBLIC_BOUNDARY] — Evidence Status: [SOURCE_BACKED_PUBLIC_CONTRACT (VERIFIED)].
- NODE_4_SANITIZATION_ENVELOPE: PII Sanitization & Vault Envelope (sanitize_server_write, enforce_memory_write_envelope) — Classification: [INTERNAL_SUBSYSTEM] — Evidence Status: [SOURCE_BACKED_PUBLIC_CONTRACT (VERIFIED)].
- NODE_5_SCOPE_ISOLATION_GUARD: Scope & Multi-Tenant Isolation Guard (BoundSpace, assert_requested_team_matches_bound_space) — Classification: [INTERNAL_SUBSYSTEM] — Evidence Status: [SOURCE_BACKED_PUBLIC_CONTRACT (VERIFIED)].
- NODE_6_SEARCH_TEMPORAL_PARSER: Search & Temporal Query Parser (TemporalQuerySpec, extract_temporal_context) — Classification: [INTERNAL_SUBSYSTEM] — Evidence Status: [SOURCE_BACKED_PUBLIC_CONTRACT (VERIFIED)].
- NODE_7_CANDIDATE_SCORER: Candidate Scorer & Reranker (SearchEngine.rerank_recall_results) — Classification: [INTERNAL_SUBSYSTEM] — Evidence Status: [SOURCE_BACKED_PUBLIC_CONTRACT (VERIFIED)].
- NODE_8_VERSION_LIFECYCLE_ENGINE: Version & Lifecycle Controller (VersionController.superseded_snapshot) — Classification: [INTERNAL_SUBSYSTEM] — Evidence Status: [SOURCE_BACKED_PUBLIC_CONTRACT (VERIFIED)].
- NODE_9_CONTEXT_BUDGET_ASSEMBLER: Context Budget Assembler (_apply_recall_response_budget) — Classification: [INTERNAL_SUBSYSTEM] — Evidence Status: [SOURCE_BACKED_PUBLIC_CONTRACT (VERIFIED)].
- NODE_10_PUBLIC_RECEIPT_CITATION: Public Receipt & Citation Formatter (_public_recall_meta) — Classification: [PUBLIC_BOUNDARY] — Evidence Status: [SOURCE_BACKED_PUBLIC_CONTRACT (VERIFIED)].
Open-Source vs Managed Cloud Service Boundary
Public architectural assertions and ecosystem claims are evaluated against the empirical code contract. Claims are strictly classified as VERIFIED (supported by executable tests and code symbols) or NOT_VERIFIED (refuted, unverified, or restricted to proprietary hosted environments):
- STMT_01_PROVENANCE_ATTRIBUTION [VERIFIED]: XMemo records operational audit logs, preserves version history (memory_versions), and applies encryption envelopes when keyguard/vault mode is enabled. Architecture: Cryptographic Security Envelope.
- STMT_02_CROSS_CLIENT_CONTINUITY [VERIFIED]: Memories captured across Claude Desktop, Cursor, or CLI are instantly accessible across any MCP-compliant client via standard JSON-RPC. Architecture: Streamable FastMCP ASGI Adapter.
- STMT_03_REALTIME_CORRECTION [VERIFIED]: Fact updates maintain immutable version history while superseding prior conflicting memories via parent pointers. Architecture: Immutable Version DAG Controller.
- STMT_04_TOKEN_BUDGET_GUARANTEE [VERIFIED]: Recall context injection strictly respects caller-specified token and byte budgets. Architecture: Deterministic Token Budget Assembler.
- STMT_05_ZERO_TOKEN_EXPOSURE [VERIFIED]: Unauthenticated requests and unauthorized scopes are denied at the gateway without executing storage queries or exposing tokens. Architecture: Ingress Authentication & Scope Isolation Gate.
- STMT_06_BACKEND_OPEN_SOURCE_CLAIM [NOT_VERIFIED]: Claim of 100% open-source backend is REFUTED. Only client packages (@xmemo/client, MIT license) and local MCP server adapters are open source. Multi-tenant cloud infrastructure, billing, and fleet orchestration remain proprietary managed services.
- STMT_07_AUTONOMOUS_CONSENSUS_CLAIM [NOT_VERIFIED]: Autonomous cross-organization consensus is REFUTED. Tenant isolation is strictly enforced by BoundSpace and tenant_id partitioning; cross-tenant automatic merging is not implemented.
- STMT_08_ZERO_LATENCY_REPLICATION_CLAIM [NOT_VERIFIED]: Zero-latency global replication claim is REFUTED. Search uses embedded/local vector indices (Qdrant/SQLite); zero-latency global consistency is unverified and not claimed.
Reproducible Architecture Lifecycle Walkthrough (Synthetic A/B Example)
A step-by-step verifiable lifecycle walkthrough demonstrating cross-agent memory sharing, multi-tenant isolation, realtime user correction, and immutable provenance tracking using strictly synthetic demo data. Every step maps directly to verified system capabilities and approved claim IDs under the public contract:
- Step 1 [AGENT_A_WRITE]: Agent A (ide-assistant-alpha) writes synthetic preference via remember tool to scope project:synthetic-demo — Payload: {'formatting': 'tabs', 'indent': 4} — Claim: [STMT_01_PROVENANCE_ATTRIBUTION] & [STMT_02_CROSS_CLIENT_CONTINUITY] — Receipt: mem-synth-pref-001@v1, digest sha256:7f83b165 — Status: [SOURCE_BACKED_PUBLIC_CONTRACT (VERIFIED)] — Boundary: [DEMO_DATA: SYNTHETIC].
- Step 2 [AGENT_B_RECALL]: Agent B (terminal-assistant-beta) recalls preference within authorized scope project:synthetic-demo via recall tool — Query: 'code formatting indent' — Claim: [STMT_02_CROSS_CLIENT_CONTINUITY] & [STMT_04_TOKEN_BUDGET_GUARANTEE] — Receipt: mem-synth-pref-001@v1 cited, score 0.94, bounded budget — Status: [SOURCE_BACKED_PUBLIC_CONTRACT (VERIFIED)] — Boundary: [DEMO_DATA: SYNTHETIC].
- Step 3 [UNAUTHORIZED_DENIAL]: Unauthorized Agent (rogue-guest-gamma) attempts cross-tenant access to project:synthetic-demo without valid credentials — Gate: Scope Isolation & Auth Gateway — Claim: [STMT_05_ZERO_TOKEN_EXPOSURE] — Outcome: AUTH_SCOPE_DENIED (HTTP 403), zero data leakage, zero storage mutation verified by database snapshot byte equality — Status: [SOURCE_BACKED_PUBLIC_CONTRACT (VERIFIED)] — Boundary: [DEMO_DATA: SYNTHETIC].
- Step 4 [USER_CORRECTION]: User corrects formatting standard via update_memory tool — Payload: {'formatting': 'spaces', 'indent': 2}, reason: 'team style guide update' — Controller: Version DAG Controller — Claim: [STMT_03_REALTIME_CORRECTION] — Receipt: mem-synth-pref-001@v2, supersedes v1, parent_digest sha256:7f83b165 — Status: [SOURCE_BACKED_PUBLIC_CONTRACT (VERIFIED)] — Boundary: [DEMO_DATA: SYNTHETIC].
- Step 5 [LATER_RECALL_V2]: Subsequent recall query selects updated version 2 while active candidate queries strictly exclude superseded version 1 via SearchEngine — Query: 'indentation preference' — Claim: [STMT_03_REALTIME_CORRECTION] & [STMT_04_TOKEN_BUDGET_GUARANTEE] — Outcome: Active recall context injects only v2 (spaces, 2) — Status: [SOURCE_BACKED_PUBLIC_CONTRACT (VERIFIED)] — Boundary: [DEMO_DATA: SYNTHETIC].
- Step 6 [PROVENANCE_DAG]: Audit inspection of version history via Version Controller — Chain: v1 (initial write by ide-assistant-alpha) -> v2 (superseded_by user correction) — Claim: [STMT_01_PROVENANCE_ATTRIBUTION] — Verification: Version history and parent pointers fully inspectable — Status: [SOURCE_BACKED_PUBLIC_CONTRACT (VERIFIED)] — Boundary: [DEMO_DATA: SYNTHETIC].
- Step 7 [STATE_RESET]: Resettable sandbox controls restore synthetic workspace scope project:synthetic-demo to clean baseline — Action: Deterministic teardown and state purge — Claim: [STMT_05_ZERO_TOKEN_EXPOSURE] — Receipt: reset_status CLEARED, 0 residual rows, zero persistent side effects — Status: [SOURCE_BACKED_PUBLIC_CONTRACT (VERIFIED)] — Boundary: [DEMO_DATA: SYNTHETIC].
- Boundary Notice [NOT_VERIFIED]: Cloud multi-tenant billing pipelines [STMT_06_BACKEND_OPEN_SOURCE_CLAIM], autonomous cross-organization consensus [STMT_07_AUTONOMOUS_CONSENSUS_CLAIM], and zero-latency cross-region replication [STMT_08_ZERO_LATENCY_REPLICATION_CLAIM] are [NOT_VERIFIED] and excluded from this local open-source runtime walkthrough.
+------------------------------------------------------------------------------------------------------------------------+
| [REPRODUCIBLE ARCHITECTURE LIFECYCLE WALKTHROUGH: SYNTHETIC A/B PREFERENCE SHARING & CORRECTION] |
| |
| Agent A (IDE) XMemo Gateway & Engines Agent B (CLI) Unauthorized Agent (Guest) |
| [ide-assistant-alpha] [FastMCP / Storage / Scope] [terminal-assistant-beta] [rogue-guest-gamma] |
| | | | | |
| (1) remember(pref: tabs, 4) | | | |
| -------------------------------------> | | | |
| | [Write v1, Hash: 7f83b1] | | |
| <------------------------------------- | | | |
| Receipt: mem-001@v1 | | | |
| | | (2) recall(pref) | | |
| | | <--------------------------- | | |
| | | [Scope Match: synth-demo] | | |
| | | ---------------------------> | | |
| | | Citation: mem-001@v1 | | |
| | | | (3) recall(foreign tenant) | |
| | | <---------------------------------------------------------- | |
| | | [BoundSpace Check: MISMATCH] | |
| | | ----------------------------------------------------------> | |
| | | DENIED: AUTH_SCOPE_DENIED (Zero Mutation) |
| | | | | |
| (4) update_memory(pref: spaces, 2) | | | |
| -------------------------------------> | | | |
| | [Write v2, parent: v1] | | |
| <------------------------------------- | | | |
| Receipt: mem-001@v2 (supersedes v1) | | | |
| | | (5) recall(pref) | | |
| | | <--------------------------- | | |
| | | [Exclude v1, Select v2] | | |
| | | ---------------------------> | | |
| | | Citation: mem-001@v2 | | |
| | | | | |
| (6) inspect_provenance(mem-001) | | | |
| -------------------------------------> | | | |
| <------------------------------------- | | | |
| DAG: v1 (Hash: 7f83) -> v2 (Hash: 4d82) | | |
| | | | | |
| (7) reset_synthetic_state() | | | |
| -------------------------------------> | [Purge demo scope] | | |
| <------------------------------------- | 0 residual rows | | |
+------------------------------------------------------------------------------------------------------------------------+
Deep Concept & Security Navigation
Explore specific architectural domains through our deep-dive concept and security documentation:
- Memory Data Model (/docs/concepts/memory-model): Entity structures, semantic categories, importance scores, and representation layers.
- Provenance & Attribution (/docs/concepts/provenance-attribution): Audit trails and caller attribution.
- Project Memory Spaces (/docs/concepts/projects): Project boundary isolation, path routing conventions, and team sharing.
- Dream & Memory Consolidation (/docs/concepts/dream-reflection): Background consolidation, graph linkage, association extraction, and dream jobs.
- External Knowledge Bases (/docs/concepts/knowledge-bases): Document indexing, chunking strategies, and reference citations.
- Data Boundary & Security (/docs/security/data-boundary): Comprehensive delineation between local self-hosted capabilities and cloud SaaS services.
Persona flows
ChatGPT user
Give ChatGPT durable access to your XMemo preferences, project facts, decisions, and TODOs without pasting bearer tokens into a chat.
Save a synthetic preference or project note, start a new chat, then ask ChatGPT to recall it through XMemo before continuing work.
Copilot / Codex developer
Carry repo decisions, coding conventions, bug-fix notes, and task history between IDE and CLI agents.
Record a codebase decision or bug fix, then ask the next IDE or CLI agent to recall the relevant XMemo context before editing.
Team / enterprise pilot owner
Evaluate shared memory with account controls, source attribution, export/delete workflows, and reviewer-safe setup evidence.
Have a pilot member save a synthetic team memory, confirm source attribution in XMemo, then review delete/export and support paths.