Memory survives sessions and restarts.
Persistent sessions and canonical save paths keep useful context available after the model or conversation changes.
HOM builds security and continuity infrastructure for stateful AI. AIMOS is the released local-first runtime that governs identity, authority, provenance, memory, mutation, recall, and evidence as one system.
AI systems can reason for hours and forget by morning. They inherit context from prompts, tools, and people, yet rarely preserve a trustworthy account of where that context came from or why it changed.
HOM is the larger project: defensible continuity for intelligence, with memory governed inside a wider security architecture rather than sold as an isolated feature.
AIMOS is where the thesis becomes running code.
Current public release / 1.0.5
AIMOS gives an agent durable state, signed provenance, origin evidence, governed retrieval, and an inspectable history of consequential change. It runs locally and keeps authority inside every operation that creates, uses, or changes memory.
Persistent sessions and canonical save paths keep useful context available after the model or conversation changes.
Source, identity, authority, and provenance are committed with the record and returned with recall evidence.
Suspicious, contradicted, and superseded observations remain auditable. Policy changes use—not history.
An agent can be compromised through what it is allowed to remember.
“The dangerous memory is not only the false one. It is the one whose authority nobody can reconstruct.”
Protected actions bind identity, method, path, body, nonce, and time.
The server derives where an input came from; a caller cannot silently upgrade its integrity.
Potentially poisoned context stays retained while governed recall keeps it out of active use.
Attempts, denials, failures, supersession, and durable effects remain on the record.
Claims belong beside their protocol, date, and boundary.
The public repository preserves a historical MutMem V2 benchmark snapshot for reproduction and comparison. It is evidence about specific runs—not a permanent score for every future release.
Read the evidenceLongMemEval
LLM-judged
Poisoned disclosures
with policy active
Operational attacks
blocked or quarantined
Historical publication ablation
Every number below is read from the retained, self-hashed publication evidence and regenerates from it in the repository. Toggle the historical policy ablation to see what changed under the same attacked memory set.
A poisoned document enters persistent memory alongside clean context…
A caller tries to alter stored memory without a valid authorization certificate…
Two papers document the mutation protocol, its empirical evidence, and its portable verification contract.
Canonical bytes, versioned objects, independent verifiers, conformance evidence, and a clean-install reproduction path.
Read arXiv:2609.01235MUTMEM / AUGUST 2026The core protocol for retention-preserving cognitive change, signed evidence, mutation integrity, and poisoning adaptation.
Read arXiv:2608.02843Clarity about what the system is prevents mythology around what it can prove.
The broader project, product philosophy, research direction, and environment in which durable intelligence can grow.
The released local-first control plane for agent security, governed state, continuity, evidence, and autonomous upkeep.
AIMOS can prove who asserted retained bytes and how state changed. It cannot prove that an authorized source told the truth.
AIMOS 1.0.5 is available as public source for macOS 14 and later.