Published a public-safe Mem0 Local design/setup guide and responsive interconnection architecture while preserving the accepted private runtime and unrelated site configuration.

Mem0 public architecture documentation — 2026-08-28

Scope

• Host: rdmsm4x only.
• Mem0 runtime, model, collection, persistent state, credentials, client registrations, and peer hosts: read-only validation; no changes.
• Website: page-only update to the existing /mem0/ route. Cloudflare policy, DNS, tunnel, nginx, Compose configuration, site-wide generators/exporter, and unrelated pages were not changed.
• Public boundary: the unauthenticated HTTP 200 route contains no Mem0 private hostnames, absolute or user-specific paths, internal collection/model/release identifiers, credentials, tokens, authentication mechanics, memory bodies, prompts, or agent transcripts.

Source state and files changed

Mem0 documentation branch codex/mem0-architecture-docs-20260828:

• /Users/richh/dev/_worktrees/codex-mem0-architecture-docs-20260828/README.md
• /Users/richh/dev/_worktrees/codex-mem0-architecture-docs-20260828/docs/architecture-and-setup.md
• /Users/richh/dev/_worktrees/codex-mem0-architecture-docs-20260828/SESSION-STATE.md
• /Users/richh/dev/_worktrees/codex-mem0-architecture-docs-20260828/ISSUES.md
• Content commit: 365098efd7fbbda6364b2f7c96e40d29acfd1acc.
• Publication-record commit before final closeout: 785d981aa5bb483513ceaaefc0178123b4235645.

Status-page branch codex/mem0-architecture-diagram-20260828:

• /Users/richh/dev/_worktrees/dev-dataroo-net/codex-mem0-architecture-diagram-20260828/sites/mem0-status/index.html
• /Users/richh/dev/_worktrees/dev-dataroo-net/codex-mem0-architecture-diagram-20260828/sites/mem0-status/README.md
• /Users/richh/dev/_worktrees/dev-dataroo-net/codex-mem0-architecture-diagram-20260828/sites/mem0-status/prepare_publish.py
• /Users/richh/dev/_worktrees/dev-dataroo-net/codex-mem0-architecture-diagram-20260828/sites/mem0-status/verify_origin.py
• /Users/richh/dev/_worktrees/dev-dataroo-net/codex-mem0-architecture-diagram-20260828/sites/mem0-status/publish_mem0_status.zsh
• /Users/richh/dev/_worktrees/dev-dataroo-net/codex-mem0-architecture-diagram-20260828/tests/test_mem0_status_dashboard.py
• Final source commit: e1efd059eb9aec0732514532c7c7afcf6b7b573a.

Other durable/local state:

• /Users/richh/dataroo.net/wiki/mem0/index.html — atomically replaced with the prepared page; managed navigation and Export blocks preserved.
• /Users/richh/Library/Mobile Documents/com~apple~CloudDocs/Codex/projects/AGENTS.md principles/PROJECTS.md — Mem0 and dev.dataroo.net milestone entries updated.
• /Users/richh/.agent-coordination/checkins/codex-rdmsm4x-mem0-architecture-docs-20260828.json — writer/lifecycle evidence.
• This changelog file and the verified Apple Notes projection at Notes / llmlog / rdmsm4x - changelog - mem0-public-architecture - claude - unspecified - general - 20260828-0134.

Commands and verification

• Revalidated host, canonical roots, all relevant worktrees/branches/full HEADs, dirty state, writer check-in, active services, and origin/public HTTP behavior before mutation.
• Ran /usr/bin/python3 -m unittest discover -s tests -v in the status-page source worktree: 43 tests passed.
• Ran uv run pytest -q in the Mem0 documentation worktree: 37 tests passed.
• Ran uv run ruff check .: all checks passed.
• Ran Python compilation, zsh -n, git diff --check, semantic/accessibility/redaction contracts, and publisher regression tests: passed.
• Ran zsh scripts/validate_mem0_local.zsh against the accepted runtime: all five validation stages passed; both owned containers remained healthy.
• Ran zsh sites/mem0-status/publish_mem0_status.zsh from clean site commit e1efd059eb9aec0732514532c7c7afcf6b7b573a: atomic publication succeeded and the loopback origin matched on verification attempt 1.
• Verified desktop, mobile, light, and dark browser presentations. Desktop rendered one accessible 12-node/13-edge SVG; mobile rendered a five-group stacked topology; the six setup stages, navigation, Export control, and zero-root-overflow contract passed.
• A warmed browser tab initially displayed its previous cached response. With browser cache disabled, the canonical URL immediately returned the new page; a unique-query fresh request produced the same architecture. Cached content was not treated as source or deployment evidence.

Hash and health evidence

• Static page source SHA-256: 6c32087866679bc7759f149032079ab2054275d7fe4ea71b01901ed980e9ae73.
• Prepared/deployed file SHA-256: 9944b5c1b303f43bca5d8d8c129863ebe90ab8931817803352730076aec2f433.
• Loopback origin response SHA-256: 9944b5c1b303f43bca5d8d8c129863ebe90ab8931817803352730076aec2f433, HTTP 200.
• Sample public edge response SHA-256 after publication: 34f9e9d0a8156d0e402d1e8bde78ad848d5d2c41f2ef71405c7ba3f4c0c63a3a, HTTP 200. Edge-added response markup makes this intentionally distinct from the origin artifact hash.
• Existing website Compose configuration SHA-256 remained 0f87dea1c9b8160935a73af08bd28a270b3366b713a7866273dc8b96e21e8652.
• Accepted Mem0 runtime release remained 7079ac107ff2f3c9a3cf187c2bec9f5656cf24e1; runtime validation passed after page publication.
• The site-wide managed Export utility contains pre-existing generic ~/dev/ output templates also present in the prior-page backup. They are not Mem0 deployment coordinates; the Mem0 source content contains no absolute or user-specific filesystem path.

Rollback and failure evidence

• First publication attempt backup: /Users/richh/dev/_backups/devsite-mem0-status/20260828-011450.
• That first attempt observed a brief HTTP 404 while the host-to-container bind mount propagated an inode replacement. The publisher automatically preserved the failed install and restored the previous page.
• The defect was reproduced as a short visibility race, protected by tests, and fixed with a bounded condition-based verifier that requires the exact deployed SHA from the loopback origin.
• Final pre-publication page backup and rollback instructions: /Users/richh/dev/_backups/devsite-mem0-status/20260828-012542/rollback.txt.
• Undo the page only by following that rollback record: install the retained prior page to a temporary file beside the live page, atomically rename it over the current page, and reverify the loopback/public response. No runtime rollback is required because the Mem0 runtime was not changed.
• Preserve both isolated branches/worktrees and rollback directories until canonical source integration is received and accepted.

Lifecycle state

• User directive: received and accepted by task 01a046a3-bf5d-70b1-ae1e-9999936faae2, sourced from task 01a046a5-081e-7452-8e4e-a0cbf56318d8.
• Source: prepared, committed, and verified on two isolated branches.
• Deployment: atomically applied and verified against the prepared SHA and loopback origin.
• Public receipt: confirmed with fresh HTTP and uncached browser clients.
• Client dispatch/receipt/acceptance: not applicable; no Mem0 client configuration changed.
• Canonical source dispatch: not performed.
• Canonical source receipt: not claimed.
• Canonical integration: pending and not implied by the live deployment.
• Requested documentation/publication work: complete after this changelog and its Apple Notes projection are verified.

Outstanding owner actions

• If canonical source integration is desired, explicitly dispatch both isolated branches to their canonical owners, record receipt, review/test the commits, and record acceptance/integration separately.
• Existing Mem0 client canary/reachability gates remain unchanged from the prior runtime milestone.