Local before remote
Keep durable context near the work. Expose network and authority boundaries instead of turning a hosted service into an invisible dependency.
05DOCTRINE + ORIGIN
Software that can
answer for itself.
The mythology gives Mnemes a name. The doctrine gives it constraints: one owner per truth, history that survives correction, authority that stays separate from relevance, and claims that stop where proof stops.
Memory is not authority
Retrieval may surface evidence. It does not decide whether an agent may assert, act, export, or rewrite durable state.
Truth has two clocks
Valid time records when a statement applies. Recorded time preserves when the system learned it. Historical questions require both.
Receipts, not theatre
Record what ran, which state was used, what degraded, and what was retained. A receipt is evidence—not factual correctness.
Append, then supersede
Corrections become new linked artifacts. Prior states remain inspectable instead of disappearing behind a confident overwrite.
Indexes accelerate truth
FTS, vectors, compressed candidates, caches, and summaries are rebuildable projections. SQLite remains authoritative.
Typed failure is product
Blocked, degraded, partial, stale, and failed must not collapse into a successful-looking response.
Claims stop at proof
Source, package, live runtime, benchmark, and receipt evidence are separate scopes. No layer inherits a stronger claim for free.
THE NAME
ΜΝΗΜΗMneme became
Mnemes.
Mneme is the ancient personification of memory. Mnemes—the plural—is the product idea: many device memories, many agent histories, many temporal perspectives, held together without erasing where each one came from.
Mneme
memoryCanonical state, lineage, retrieval, and continuity across time.
Melete
practiceIngestion, lifecycle, evaluation, compaction, and disciplined use.
Aoede
voiceMCP transport, recalled context, witnessed answers, and expression.
THE OPERATING PRINCIPLE