How it works

It writes things down while they happen, so nothing has to be rebuilt later.

Capture, structure, recall. Three steps in that order, and the order is the whole point: meaning is kept at the moment the data is made, not guessed at afterwards when a model comes looking for it.

Loose scattered marks on the left, the same marks arranged into an ordered grid in the middle, and a single answer drawn out of that grid on the right. CAPTURE STRUCTURE RECALL
A Tuesday, for example

Building the world of each client, team, or project.

Nobody set this up. It is just where the day went.

  1. 9:02 amTheir channel, catching up on the thread from last night
  2. 9:20 amThe folder in your mail, three replies deep
  3. 10:15 amThe call, and the thing they asked for on it
  4. 11:40 amScreenshots, dragged into the client folder
  5. 2:30 pmThe version you made because of the call
  6. 4:50 pmThe version you actually sent

Six moments across four tools, and not one of them knows about the others. You did all of it. By Friday you will remember roughly two.

This is the part nobody logs, because logging it has never been worth the effort. It is worth it the moment it costs you nothing.

  • Friday, 4pm.
    The client update.     NowYou scroll back five days through four tools, reconstructing your own week, then write it up. Most of an hour, every week, for work you already did once. With a recordIt is already assembled. You edit it and send it.
  • "We never asked
    for that."     NowYou know they did. You cannot find it. You eat the hours and it happens again next quarter. With a recordTuesday, 2:14pm, in their channel, from them. Ten seconds.
  • Renewal. NowNobody can say what you actually did for them this year, so you undersell it and discount to be safe. With a recordTwelve months of work, itemised, without anybody reconstructing a thing.

Not for the client. Not for a model. So you can show what you did without having to remember it.

The pipeline

Structured and organized before a model gets involved.

01

Capture

A message, a note, an invoice, a voice memo. Each becomes a UMO the moment it exists, hashed and signed at the source.

02

Structure

Entities, topics and relationships are extracted deterministically. Not embeddings that approximate meaning, but structure that carries it.

03

Recall

Ask a question and get a bounded set of records back, each addressable, each with the seal intact. Feed a model or do not.

A model is optional at every step. That is deliberate.

So what is a UMO

One thing that happened, sealed at the moment it happened.

A Universal Memory Object is the smallest unit MI™ works in. A voice memo, an invoice line, a note to yourself. It carries its own content hash, its own signature, and its place in the chain.

The record belongs to you, not to a row in our database. Each one carries the hash and the signature needed to check it against itself, rather than against our word for it.

0184-invoice.umosealed
Captured2026-08-02 09:41:07 +01:00
Sourceaccounting.sync · system-signed
Entitiessupplier, amount, due date, PO ref
Contentsha256 9b23f0…41ac
SignatureEd25519 · owner key
Chainrecord 184 · root 7c40…

Structure extracted at capture, not guessed at read. That is why recall can return a bounded set instead of a best effort.

The statement

Ask for a time frame, not a keyword.

A statement covers a span of time, names every source it drew on, and declares its own boundary. You can see what is in it before you spend anything on it.

It is not a better search box. It is a smaller, known set of records, each one addressable and each one sealed.

> what did we agree with this client in January
I don't have that context.
No sources cited.
No record of what I saw.

Every assistant you already pay for, answering a question your own company answered eighteen months ago.

Capture controls

You decide when it starts. And when it stops.

Nothing is captured because a folder happened to be open. Capture has a beginning and an end you set, in words a person would use.

  1. 1
    Connect a source
    Point it at Slack, a mailbox, a repo, or just a folder. Connecting is not the same as granting: nothing has been handed to a model yet.
  2. 2
    Set the boundary
    One project, one channel, one folder, one date range. The boundary is the control, and it is the thing you can point at later when somebody asks what was in scope.
  3. 3
    Start and stop it yourself
    Capture runs when you say so and ends when you say so. You always know which of those two states you are in.
  4. 4
    See what came in
    Every record is listed as it arrives, with where it came from. If something landed that should not have, you find out now rather than in an audit.
  5. 5
    Grant, separately
    Only now does anything reach a model, and only the fields you allow. Revoke it and the next request gets nothing, without deleting the record itself.
A real one

Tuesday, one client, one channel.

You turn capture on for the Northbank project at 9am and off at 6pm. It takes the channel, the shared folder and the calendar entries inside that window.

Your other eleven channels are untouched. Nobody had to write a policy for that, because the boundary was the setting.

NorthbankCapturing

09:00 to 18:00 · you set this

3Sources
41Records
0Granted

In scope#northbankDrive folderCalendar

Nothing has gone to a model. Capturing and granting are two different switches.

What connects

The tools you already run.

  • SlackMessages, threads, reactions.Who said it and when.
  • GitHubCommits, pull requests, reviews.What changed and who approved it.
  • GmailThreads and attachments.The ask and the answer, together.
  • NotionPages and edit history.Which version was live in March.
  • FigmaFiles and version history.What moved between them.
  • Linear & JiraIssues, states, transitions.When it moved and on whose say-so.
  • Google CalendarEvents and attendees.That it happened and who was in it.
  • Drag and dropAny folder you choose.No connector required.

Capture is the product. Everything downstream is a consequence of it.

The record starts when the work does, not when somebody (or something) asks for it.

Free beta for 30 days.

Try free Back to the start