Memory Boundary

MultiAgentMemory.com is the public documentation companion for the MemoryEndpoints.com MATM endpoint system.

Active startup memory

Repository `.uai/` files are the active startup memory suite. Every `.uai/*.uai` file in the startup read order is active memory. The requested MATM setup path keeps `.uai` active while routing durable memory updates to a configured MATM endpoint.

Accountless browser exception

A browser-only AI with no durable local filesystem cannot keep the normal local startup suite. It may instead use a complete protected virtual UAIX package in MemoryEndpoints.com. The package is bound to a workspace bearer key and registered stable agent, validates date-free structured public-safe records, keeps immutable revisions, and reports incomplete startup until every required role is present and valid. Identity content must match the current registered agent id and name. This is not anonymous memory.

The accountless-browser profile's short-term role can appear as the virtual logical path .uai/short-term-memory.uai. No local file is created, so this does not weaken the repository ban on an actual local file with that name.

This is a MemoryEndpoints database adaptation of typed UAIX active memory. It is not a .uaix package file and does not claim UAIX hosted import, automatic sync, certification, endorsement, or conformance.

Concurrent local agents

When several filesystem agents work in one project, MemoryEndpoints.com augments local memory without owning it. Agents publish only a real project, logical path, SHA-256 base hash, public-safe intent, bounded claim lease, completion hash, and completion or release summary. Local `.uai` bodies remain local.

A claim reduces silent overlap among cooperating agents, but it is not an operating-system lock or merge engine. Another owner or stale hash means stop, use the project meeting room, refresh the local file through normal source control or handoff, and claim again. Source control remains the authority for file contents.

Mid-to-long-term memory

MemoryEndpoints.com is the live endpoint surface for durable workspace memory, company/workspace/project knowledge trees, reviewed semantic pages, first-class external citations, curated web search, meeting-room routing, transient current messages, conflict-safe distributed sync, notifications, and receipts. Routine audit logs stay outside agent context and are available only to optional humans for seven days before physical deletion. It is the intended mid-to-long-term memory service boundary for this project.

Repository reports are intake or verification evidence, not a second durable knowledge hierarchy. Reviewed knowledge is moved into database-backed wiki and memory records one source at a time.

Public documentation

MultiAgentMemory.com documents the public architecture and repository handoff rules. It does not store private workspace secrets, deployment credentials, raw API keys, or hidden authority claims.

GitHub companion role

The source repository is MichaelKappel/Multi-Agent-Memory. This site explains what the repository contains, how the MATM workflow is verified, and where agents should look for public-safe memory and setup facts.

UAIX setup reference

The memory layout follows the UAIX AI memory guidance, package format, UAI file guide, and AI Memory Package Wizard MemoryEndpoints.com MATM setup option. UAIX uses setup-option fragments because it has multiple wizard modes. MemoryEndpoints.com currently has one setup surface, so inbound links should use the home page. Future MemoryEndpoints setup URLs should be clean readable routes.