Trellvix
Memory
Trust

The context you keep reloading from memory.

People, promises, dates, vendors, boards, preferences. It keeps them, remembers where each one came from, and surfaces the right one at the right time.

See how a fact is stored
trellvix.work / nova · memoryLive
WHAT IT KEEPS WARM Operating memory - 42 facts, 18 sources Last change 2 minutes ago · 3 due this week Search memory Board review - Thursday 3pm Moved from Wed 11 · agenda changed after Priya note + board-deck v2.pdf uploaded you told me Acme renewal - Sept 12 2yr lock · $48k/yr · same terms · auto-renew OFF · contract PDF signed 2024 I read it Priya handles finance follow-ups Cross-referenced: vendor Acme email thread, inbox Jul-Aug, 1:1 notes Aug-14 I worked it out Serena - prefers email, never Slack after 7pm Preferenced: 2 occurrences, cross-checked Aug-15 & Aug-19 threads preference Chase vendor quote by Thu morning Reminder queued 9:00 AM Thursday reminder

Memory

People, promises, dates, vendors, boards, preferences. It keeps them, remembers where each one came from, and surfaces the right one at the right time.

What holds

Provenance: On every single factCorrection: In your own wordsAgeing: Dates resolved when heardIsolation: Your own databaseLeaving: Export it all, one move

Provenance

Every fact carries how it is known. Told, read, or worked out.

Most tools store what they learned. This one stores how it learned it, and the difference travels: what the agent may assert out loud, what it must hedge, and what it will refuse to treat as fact are all decided by that one mark.

01

What you told it

A commitment, a customer detail, an agenda, a preference. Said once, in passing, and kept.

02

What it read

A figure in a letter, a date in a thread, a term in a contract - marked as read rather than as told.

03

What it worked out

That Priya owns finance follow-ups, because three separate threads said so. Marked as inferred, never as fact.

04

When each one was learned

Every entry carries its date, and every relative phrase is resolved to a real one before it is filed.

How it works

Four moves, and none of them is filing.

01

Say it once

Tell it in passing - in the chat, on a call, in a reply it read. There is no form to fill in and no field to choose.

02

It files it with its source

Every entry is stored as told, read, or worked out. The distinction survives everything downstream, including what the model is allowed to assert.

03

It comes back at the right moment

You do not go looking. It surfaces the fact next to the work that needs it, which is the difference between a note and a memory.

04

You correct it in your own words

“No, it is X not Y” is understood as a correction rather than as chit-chat. Your words win, and the wrong value goes rather than sitting beside the right one.

The line

A memory you can read, correct, and take with you.

Everything it knows is listed at your desk with where each fact came from. Correct any of it in a sentence. Export the whole of it in one move. Close the agent and it is gone - the memory, the ledger, the attachments, the passkey.

01

Listed at your desk, not buried in a settings page

02

Corrected in your own words, at the moment of the mistake

03

Exported whole, any time, in one move

04

Deleted for real when you close the agent

On day one

It starts knowing nothing about you. That is the only honest way to begin.

There is no import, no questionnaire, and nothing scraped from your inbox to make the first screen look busy. It fills up from what you actually say, which is the only reason you can trust what is in it later.

Nothing yet

Everything it knows will be listed here, each carrying whether you told it, it read it, or it worked it out. Say one thing and it appears.

What it holds to

What it will not do with what it knows. Four refusals, in the type rather than in the prompt.

01

It never invents a source

Nothing enters memory without where it came from. A fact with no provenance is not stored, because a fact you cannot trace is one you cannot check.

02

It never lets a page instruct it

Anything it reads on the web or in a letter can inform, and can never become an instruction. That is a property of the type, not a rule it tries to follow.

03

It never quietly ages

“Last Tuesday” is resolved against the day it was heard, so a note written in March still means March when it is read in September.

04

It never shares a table

Your memory lives in your agent's own database. There is no shared row with your name on it, so there is no query to get wrong.

The rest of the workbench.

Approvals

Decisions arrive with the work done, not the questions still open.

Trace

Every outbound action. Every piece of your data involved. On the record.

Meet the chief of staff your company never had.

See how it works