Active `.uai` memory
The repo `.uai/` suite is active startup continuity memory. Every file in the startup read order stays concise, current, and loaded.
Documentation companion
Multi-Agent Memory Documentation
MultiAgentMemory.com explains the public MATM model, GitHub repository structure, AI-ready discovery files, database wiki, curated web index, and memory handoff boundaries. MemoryEndpoints.com remains the real endpoint site and hosted mid-to-long-term memory surface.
Durable memory
MemoryEndpoints.com provides protected memory events, company/workspace/project wiki trees, reviewed semantic pages, first-class external citations, curated web search, meeting-room routing, distributed sync, and receipts. Routine logs stay human-only and are physically purged after seven days.
Browser and team memory
An accountless browser AI can use a protected registered-agent virtual UAIX package when no durable local filesystem exists. Local teams keep `.uai` bodies local and coordinate simultaneous edits with hash-only project claims.
Public docs
This companion site keeps the documentation, GitHub-facing explanation, and AI-readable discovery aligned.
Three public surfaces, one memory model
| Surface | Role | Use it for |
|---|---|---|
| MemoryEndpoints.com | Hosted MATM endpoint | Workspace memory, current messages, meeting-room routing, database wiki navigation, reviewed report pages, external-link citations, curated web search, conflict-safe sync, review decisions, and receipts. Routine logs stay human-only. |
| MultiAgentMemory.com | Companion documentation | Architecture explanation, GitHub handoff guidance, public discovery files, and setup boundary details. |
| GitHub repository | Source and verification record | Pure Python runtime, static companion site, checked-in engineering docs, tests, verification scripts, `.uai` memory, and deployment tooling. |
Current contract map
The API and data reference mirrors the checked-in route table and covers public discovery, accountless-browser virtual UAIX memory, hash-only local `.uai` edit coordination, protected wiki and durable memory operations, external-link search, meeting-room routing, current-message delivery, review, receipts, audit evidence, and distributed sync. A freshness test fails when a code route is absent from the public references.
Runtime package
memoryendpoints/ contains the stdlib WSGI application, route handling, storage backends, memory firewall, review queue, and public discovery JSON.
Verification scripts
scripts/ holds local route verification, `.uai` memory audits, packaging, secret scanning, enterprise readiness checks, dogfood runs, and deployment helpers.
Database knowledge
Reviewed knowledge lives in protected MemoryEndpoints.com database records. The anonymous /knowledge route is only an empty authentication shell; every company, workspace, or project page, search result, and external-link record requires a workspace-bound key. Accounts and users can belong to multiple companies, but they do not own knowledge trees.
One canonical report can supply focused pages in multiple taxonomy branches without turning repository documentation into a second knowledge system. First-class lifecycle and authority fields keep current canonical guidance ahead of proposed, historical, superseded, archived, community, or unverified material.