Resonant Mind
Persistent cognitive infrastructure for AI systems. 28 MCP tools — semantic memory, emotional processing, identity continuity, and a subconscious daemon. Built…
A Postgres-backed cognitive substrate for persistent AI memory, identity, dreams, drives, relationships, and continuity.
Resonant Mind began as persistent memory infrastructure and was subsequently reshaped through use in long-running AI minds. Version 4 promotes that lived architecture into a generic single-mind public core.
Status
The current release is v4.1.4. v4.0.0 was the Reshape release. The 4.1 releases add the v3.2 → v4 migrator and make entity merge lossless; see the changelog for each one.
- Postgres-only at runtime: Neon through Cloudflare Hyperdrive
- 47 MCP tools organised by kinds of act
- 30-minute subconscious metabolism
- R2-backed visual memory
- pgvector semantic retrieval
- Workers AI dream composition
- no bundled dashboard or Observatory
- no D1 runtime (D1 is supported only as a source for the v3.2 migrator)
- no hard-coded person or household tenancy
Upgrading from v3.2? Back up first. Before you run anything, take a full backup of your v3.2 database (and your images) and check that you can restore it. The User migration guide shows how for PostgreSQL and for D1.
v3.2 → v4 migration (operator-assisted). Since 4.1.0 the
migrate:v32CLI moves a public v3.2 PostgreSQL or D1/SQLite mind into a fresh, separate v4 database. It never changes your v3.2 database, refuses anything it cannot prove instead of guessing, and checks the result column by column before it says you are ready to switch. Some steps stay yours: copying images, re-embedding with your provider, and switching your deployment over. Follow the User migration guide, or give your agent the Agent migration runbook. What has and has not been proven is in docs/migration-v32-v4-acceptance.md.A v3.2 D1 or SQLite mind that drifted from the public schema (a column added by hand, a table rebuilt, a
dreamstable of your own) is refused byinspect-source, as it should be. Since 4.1.4,normalise-sourcerebuilds a copy of it in the exact v3.2 schema and sets everything else aside for you to put back after the import. See "A source that has drifted from v3.2" in the user guide. A drifted PostgreSQL source has no such route yet.The v4 migration runner itself still sets up fresh v4 databases only; it deliberately refuses an existing v3 schema, so a v3 database is never upgraded in place.
If your mind ever merged two entities on 4.1.1 or earlier, please read docs/merge-damage-check.md. A merge before 4.1.2 could leave orphaned or misfiled vectors and other traces behind. Upgrading stops new damage but does not repair old damage.
npm run check:merge-damageis a read-only check, andnpm run repair:merge-vectorsclears the vector findings without destroying anything (it is a dry run unless given--apply). Every repair is the owner's decision.
Architecture
The governing distinction is:
Regions are kinds of act. Organs are kinds of state.
Regions include Ritual, Attention, Surgery, Compass, Spine, Bonds, Episodes, Active, Weather, Dreams, Drives, Inner Appetite, and Network.
The scheduled daemon metabolises memory rather than merely storing it: mood and affect, novelty and charge, retention, orphan detection, proposals, consolidation, reflection, dream recurrence, bond warmth, somatic markers, drives, redolence, identity proposals, and stale threads.
Requirements
- Node.js 22+
- Cloudflare Workers account
- Neon Postgres database
- Cloudflare Hyperdrive configuration
- Cloudflare R2 bucket
- Gemini API key for embeddings (other providers: see docs/alternative-embeddings.md)
- Workers AI binding for dream composition
Postgres requires the vector extension.
Install
npm ci
cp wrangler.toml wrangler.local.toml
From the project's README.