celiums/celiums-memory

**A complete cognitive memory engine. Apache-2.0. All of it.**
> **Development branch notice:** this branch is dev work for the Rust and
> Cloudflare migration. It is **not production-ready** and must not be used for
> production data, customer traffic, or public release artifacts. The stable
> user-facing line remains main until the production gates below are closed.
Celiums Memory is an **engine**, not an app — no UI, no dashboard to log
into. It is the memory, journaling, ethics and knowledge substrate you
embed *inside* other software: agents, assistants, tools, pipelines. It
speaks **MCP** (Model Context Protocol) so any compatible client
(Claude Code, Cursor, Continue, Cline, OpenCode, or your own) gets
persistent memory, a first-person journal, an auditable ethics engine,
and a per-user biological clock — without you building any of it.
> **Implementation status:** the Rust workspace in rust/ is the
> canonical implementation. The Cloudflare Worker, Durable Object, R2 and
> Container runtime are the **target** deployment path and are still being
> validated on dev. See the ordered Rust roadmap, the
> execution ledger, and ADR-025.
It is open source under Apache-2.0 **in full**: no open-core split, no
paid tier, no proprietary core held back. The Ethics Engine — every
layer — is open and auditable. Its ethics_knowledge corpus is
distributed separately as a v2.0.0 release asset (not in the git
tree); the engine runs on Layers A+B without it, and Layer K (precedent)
abstains cleanly when the corpus is absent.
A fuller statement of intent: MANIFESTO.md.
---
Target Architecture
The Container filesystem is disposable. The Durable Object is the serialized
control plane, and encrypted checkpoint artifacts are stored in R2. This is the
architecture being built and tested; it is not an assertion that this branch is
ready for production deployment.
The native Rust binary remains the local reference runtime. It supports MCP
stdio, authenticated MCP Streamable HTTP, REST v1, OpenAPI, tenant-scoped
actors, and 19 MCP tools. The Worker and Container layers must agree with that
native contract before canary promotion.
MCP client configuration:
---
The target production request path is:
The pieces:
- **Memory** — remember / recall with hybrid retrieval (vector +
full-text + affective/PAD resonance), importance scoring,
consolidation, lifecycle decay, and circadian/interoceptive
modulation.
- **Journal** — append-only, hash-chained, first-person agent journal:
causal chains, arcs, introspection, dialogue, chain verification.
- **Ethics Engine** — a 4-layer evaluator (A deterministic lexicon ·
B probabilistic CVaR with a categorical CBRN hard-block · C
philosophical scaffold · K precedent advisory). Fully open, corpus
included — the component that makes moral calls is the one that
least deserves to be hidden.
- **Biological clock** — per-user circadian rhythm modulates arousal
and recall; the engine has a sense of time and state.
- **Knowledge** — forage does hybrid search over the skills/knowledge
**you bring** (BYO; via the skills table). The large curated module
corpus is a separate Celiums project — forage runs without it.
- **Storage** — Hyphae-backed native Rust durability inside the Container;
the Durable Object is the Cloudflare control plane and recovery journal.
- **Recovery** — mutating requests carry X-Celiums-Operation-Id; the DO
persists pending, forwards the original command, stores the terminal
receipt, advances a contiguous high-water mark, and replays unresolved tail
operations after a Container failure.
- **Checkpoints** — encrypted Hyphae backups are wrapped as versioned binary
artifacts, uploaded to R2, referenced by a durable DO pointer, retained as
recent generations, and restored only into a new verified tenant generation.
Full detail — tenant isolation, confirmation gates, ethics layers and