Skip to content
VerifAIer

PERSONALFor the AI that acts on your behalf

VerifAIer Me

Assistants are starting to do things, not just say things. VerifAIer Me is how you keep a record of what yours did, on your own device, in a form you can check later.

For the AI that acts on your behalf. It audits interactions you bring to it; it is not an agent runtime and it does not act for you.

The shiftWhat changed?

It stopped being a chat.

An assistant that answers questions is something you read. An assistant that books, buys, sends, edits and remembers is something that acts for you. The second one raises four questions the first one never did.

What does it remember?

Memory is the part people notice last. Something you said months ago comes back, and there is no list of what it kept.

What can it reach?

Mail, files, calendar, payments, a browser. Access is granted once, in a hurry, and rarely looked at again.

What is it allowed to do?

Reading your calendar and moving a meeting are different acts. Most of the time there is no line drawn between them.

What did it actually do?

Weeks later, this is the only question that matters, and it is the one nothing was designed to answer.

Companies worked this out years ago. Nobody built it for a person.

Every serious organisation keeps a record of what its systems were permitted to do and what they did. You are about to have systems acting on your behalf, in your name, with your money and your relationships. The same idea, at the size of one person. Not a smaller imitation of it either: the way a conversation is sealed here is the way an operation is sealed inside a company running the same platform, and a file you check on your laptop is checked the same way an auditor checks one.

Available nowWhat works right now?

Start with one conversation you already had.

Bring in a conversation, seal it, and check it whenever you like. Three steps, done in a couple of minutes, on your own machine.

Available today: AVAILABLE
Step 1

Import

Bring in a conversation you already had with an assistant. That becomes your first workspace. No account of theirs is connected, and nothing is pulled in on its own.

Step 2

Seal

Sealing takes a fingerprint of exactly what is there and writes down when. From then on, any change to the contents shows up as a different fingerprint.

Step 3

Check

Come back in a month or a year and check it. The check runs on your device against the file itself. It never asks us whether it is genuine.

Your workspacesealed
conversation
march · travel plans
fingerprint
a91f7c04e2b8…
sealed at
14:06 · your device
checked
unchanged since
This is the whole object. It is a file you hold, not an entry in a service you visit, and it is evidence rather than a promise: nothing here asks you to believe a claim you cannot check yourself.

What it does not do yet

Nothing is captured automatically. It does not sit beside your assistant while you use it, and it does not watch anything in the background.

Everything in this chapter is something you do on purpose, after the fact. That is the honest shape of the product today, and it is worth knowing before the next chapter.

Available now
Personal AI Audit
A deterministic pass over a conversation you imported. A finding means a rule matched, never that a claim is true or false.
Flight Recorder
The ordered record of what you did in your own workspace, kept where you keep it.
Memory Receipts
A receipt over what was sealed, checkable later without asking anyone.
Findings
What the rules matched, with the reason beside each one and nothing ranked above another.
Timeline
Append-only, yours, and readable in order.
Evidence Export
Everything leaves in open formats and verifies offline.
Six capabilities ship today. It does not watch, intercept or block anything: nothing is captured unless you bring it in, and no reputation score is computed about you or anyone else.
Note

Four disclosure levels decide how much leaves a workspace if you ever share one: RECEIPT_ONLY, SUMMARY, REVIEW, DETAILED. Each is opt-in, the default discloses an empty body, and the deepest is gated on a plan feature and refused without it.

DirectionWhere is this going?

Where this is going.

Next major evolution. A personal layer that sits with your assistant rather than behind it: one place where you set what it may reach, see what it kept, and hold the record of what it did. None of the capabilities below is available today. No date is attached to any of them, and none is a service commitment.

Planned, and not built yet: PLANNED
RoadmapPlanned, and not built yet: PLANNED

Personal Runtime

A personal layer that sits with your assistant rather than behind it.

RoadmapPlanned, and not built yet: PLANNED

Real-Time Governance

Evaluation while the assistant acts, rather than after you bring the conversation in yourself.

RoadmapPlanned, and not built yet: PLANNED

Ask Before Acting

A prompt at the moment an assistant is about to do something, rather than a record of it afterwards.

RoadmapPlanned, and not built yet: PLANNED

Permission Policies

One page listing what your assistant may reach and what it may do there, in sentences rather than switches.

RoadmapPlanned, and not built yet: PLANNED

Runtime Safety Controls

Allow, Warn, Require Approval and Block as outcomes, plus Emergency Suspension. Not one of those outcomes is produced by anything shipping today.

RoadmapPlanned, and not built yet: PLANNED

Memory Governance

A view of what has been kept about you, where it came from, and what it is used for, with the ability to remove a thing and know it is gone.

Not claimed today
Nothing records your assistant while you use it

There is no background capture, and no listener beside the app.

Nothing stops an action

There is no permission your assistant asks this product about, and nothing here can decline anything on your behalf.

No memory is shown to you

None is read, because nothing here has access to what an assistant kept.

No assistant is connected

Nothing here is an integration with a service you use.

A thing that is coming and a thing that works are worth keeping apart. The chapter above is the second kind; this one is the first.

Where it will liveCan I download it?

Three places, none of them ready.

There is nothing to download today and no release date. These are the three surfaces being built for, each with the thing it is waiting on.

Desktop
Waiting on a packaged installer. No packaged installer exists yet, for this or for anything else in the family.
Planned, and not built yet: PLANNED macOS, Windows, Linux
Apple App Store
Waiting on the desktop surface first, then review. A local-first product on a phone is a different design, not a smaller window.
Planned, and not built yet: PLANNED iPhone, iPad
Google Play
Waiting on the same mobile design work as above.
Planned, and not built yet: PLANNED Android
Note

Rows rather than buttons, because a button that cannot be pressed says the page is broken and a row says the work is not finished. When a surface is ready its row becomes a button, in the same place.

Start with one conversation. Keep the habit.

The first sealed conversation takes about two minutes and proves the idea to yourself: a record you hold, that you can check without asking anyone. Everything else here is direction. Two minutes is the honest size of the offer today, and it is enough to know whether you want the rest.