TerramindYour 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.
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.
Every new conversation already has the context that took ten minutes to load last time.
Say it once and it stays said. Say it again and it gets louder.
Last week's deadline doesn't leak into next month. Stable facts do.
Memories are scoped to you and your org. Nothing crosses a tenant line.
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
Every Terramind surface reads from and writes to the same store — Agents and Nucleus today, Studio and Mac next.
Background agents inherit your defaults: language, framework, tone, taste.
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.
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.
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.
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
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
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
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
Owned all GTM at a Series A startup.
Now heads marketing at a dev-tools startup.
Voice: precise, no hype, no emojis.
Reviewed Friday launch copy with the founder.
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.
Vector search alone returns whatever's similar. We multiply by three signals so the most relevant, most recent, most reinforced memories rise.
A stated preference outweighs a passing observation. The score knows the difference.
Episodes fade with a 30-day half-life. Stable facts don't. Decay matches the type, not a global default.
Memories you repeat across sessions get amplified — what you actually care about gets louder.
effectiveScore = vectorSimilarity × typeWeight × temporalDecay × reinforcementBoostMemory is on in Agents and Nucleus today — Studio and Mac join next. Open one, and the next reply already knows you.