Terramind LogoTerramind
One memory across Terramind

Stop telling your AI the same things.

Your taste in code, the rules your team enforces, the deadline you mentioned last week — Atlas remembers it once and brings it to the next conversation, the next review, the next session.

Without memory

“I run marketing at a dev-tools startup. Tone: precise, no hype. Don't use ‘unlock’ or emojis. Friday's launch needs the announcement…”

— every. single. session.

With memory

“Draft Friday's announcement.”

It already knows the rest.

Why it matters

The model gets smarter about you, every time.

Memory isn't a feature buried in settings — it's the default everywhere Atlas works. The more you use it, the less you have to say.

Skip the warm-up.

Every new conversation already has the context that took ten minutes to load last time.

Your taste, compounding.

Say it once and it stays said. Say it again and it gets louder.

Time-aware by default.

Last week's deadline doesn't leak into next month. Stable facts do.

Yours. Only yours.

Memories are scoped to you and your org. Nothing crosses a tenant line.

One brain, every surface

The same memory, wherever you work.

Set a code style in Nucleus and the review agent enforces it. Mention a deadline in Agents and the IDE respects it. Today: Agents and Nucleus. Soon: Studio and Mac.

Memory layer

Your context, written once.

Every Terramind surface reads from and writes to the same store — Agents and Nucleus today, Studio and Mac next.

See it as a graph

Your memory has shape.

Every memory links to the ones it relates to. Clusters emerge from your work — film alongside film, code alongside code — and the relationships you didn't draw appear on their own.

memory.graph25 nodes · 38 edges
Film & ColorCode & StackPeople & OrgSound & MusicScheduleco-occurs withusesworks atmatchesframed atshot onaspect forprefers overpaired withimpliesdrivesbundled withusesmember ofmember ofleadscollaboratescitesmastered atpaired withprecedesscheduledbeforeblocksprecedescontext forvenue forshared ruleworks withwrites inemployed byattendsownsenforcesscores forcue forcommissionsmood refPrecise, no hypePNHead of marketingHONotionNODev-tools startupDTARRI AlexaAA2.39:1 anamorphic2ATypeScriptTYAvoids ORMsAOConcise repliesCRNo emojisNEbun.lockBUNext.js 16N1Mira · DPMDHugo · Eng leadHEFounderFOAria · PMAPSynthwave scoreSSTycho · referenceTR24-bit masters2BSound design passSDFriday launch reviewFLApr 29 · launch reviewA2Q2 reviewQRPitch deck duePDVacation blockVB
sectorsFilm & ColorCode & StackPeople & OrgSound & MusicSchedulere-ranked by effectiveScore

The same nodes, edges, and clusters power the dashboard in your app — this is a snapshot of what the network looks like once your memory fills in.

Three kinds of memory

Not everything you say should live forever.

A passing comment shouldn't carry the same weight as a stated rule. Each memory is classified — and the type decides how long it lives and how it's ranked.

Factweight ×1.0

Stable truths.

Names, roles, projects, stacks. Persists until something contradicts it. The boring stuff you should never have to say twice.

Sample memory

Head of marketing. Sells to engineers.

valid since 2024-09-12 · isLatest

Preferenceweight ×0.9

Tastes that compound.

Tone, defaults, aesthetics, the rules you don't want to repeat. Restating one boosts it; the system never duplicates.

Sample memory

Tone: precise, no hype. Avoids 'unlock' and emojis.

reinforced ×7 · ranks higher next time

Episodeweight ×0.7

Moments in time.

A deploy, a deadline, a meeting. Time-anchored, decays with age, and gracefully fades when it stops mattering.

Sample memory

Reviewed Friday launch copy with the founder.

valid 2026-04-29 · half-life 30d · sig 0.8

Memory through time

A timeline, not a whiteboard.

When the truth changes, we don't erase the past — we mark it invalid and link the replacement. Atlas can answer 'what's true now' and 'what was true then' from the same store.

Append-only log · userId scoped

Jan · FactInvalidated

Owned all GTM at a Series A startup.

Apr · FactLatest

Now heads marketing at a dev-tools startup.

Apr · PreferenceReinforced ×3

Voice: precise, no hype, no emojis.

May · EpisodeDecays

Reviewed Friday launch copy with the founder.

Two clocks, every memory.

Event time tracks when something became true in the world. System time tracks when we learned it. Atlas can reason about both without ever confusing the two.

validAt → invalidAt

When it was true

createdAt → expiredAt

When we knew it

Version chain

Every replacement links back to its predecessor with parentMemoryId. You can walk the chain in either direction — for an audit, a rollback, or a retrospective answer.

The right memory at the right moment

Search re-ranked by meaning.

Vector search alone returns whatever's similar. We multiply by three signals so the most relevant, most recent, most reinforced memories rise.

Type weight

A stated preference outweighs a passing observation. The score knows the difference.

Temporal decay

Episodes fade with a 30-day half-life. Stable facts don't. Decay matches the type, not a global default.

Reinforcement boost

Memories you repeat across sessions get amplified — what you actually care about gets louder.

effectiveScore = vectorSimilarity × typeWeight × temporalDecay × reinforcementBoost
Memory is on by default

Stop starting from zero.

Memory is on in Agents and Nucleus today — Studio and Mac join next. Open one, and the next reply already knows you.