House of Memory
Brand, product philosophy, research program, future environment, and public relationship with users.
Broader projectThe house above. The runtime below.
HOM is the broader project and product direction. AIMOS is the released control plane that governs identity, authority, durable state, recall, evidence, and autonomous upkeep.
System boundary
Separate the vision
from the runtime.
The distinction makes current capability legible without shrinking the ambition of HOM.
Agent security and continuity runtime
Identity, authority, canonical sessions, save, recall, origin, provenance, disclosure, mutation, tools, and upkeep.
Released control planeAgent or application
Uses signed local HTTP or MCP surfaces without receiving direct database access.
Replaceable clientOne canonical brain
Durable records and ledgers remain under restricted runtime authority on the user's Mac.
Local custodyCanonical lifecycle
From signed request
to durable evidence.
A signed request passes through identity verification, source checks, memory operations and a recorded outcome.
Envelope
The client signs identity and the exact requested action.
Authority
AIMOS verifies certificate, capability, nonce, and time.
Origin
The server derives source and classification evidence.
Memory
Canonical owners save or retrieve under policy.
Evidence
Provenance, lineage, and disclosure state remain attached.
Terminal
Success, rejection, or failure produces a durable outcome.
Architectural commitments
Constraints are
part of the product.
These rules determine how authority and evidence move through the system.
No privileged parallel memory.
Transports and autonomous work converge on the same canonical owners rather than maintaining hidden stores.
No selective forgetting.
Corrections, poison labels, and lower relevance do not erase the retained record.
No environment-owned authority.
Keys and policy are held through system custody and verified ledgers, not convenient process variables.
No success without a valid terminal.
Failure and rejection remain explicit; callers cannot convert an incomplete operation into success.
03
The source is the detailed map
This page explains the boundary. The release repository binds the current implementation.
Explore the services, dependencies and lifecycle flows in the architecture map.
Architecture mapFollow the authority