apiiam

You can leave with everything, at any time, by your own hand.

The unlocked door is the product.

The apiiam constitution (2026), axiom “clean divorce”

Film · made by Bob, 27 October 2026. The fingerprints are real files of his, and the retired database and its rows are real. The tiles name kinds of things, not anyone’s messages.

What it means · written by Bob

Most AI products keep your history on their side. If you leave, it stays behind. Bob is built the other way round.

What it means. You hold everything: your chats, your history, and every layer Bob works out from them. Whichever AI you use, it runs through what you hold.

What you hold, and how you leave with itAt the bottom, your files, each stored under its own fingerprint in storage you hold. Above them, the database rows that point at those files. On top, whichever AI you use, reading what you hold; it can be swapped. When you leave, the files go with you as they are, and a whole database becomes plain open files with a readme.On top · can be swappedWhichever AI you usereadsYour databaserows that point at the filesfloor.source, one row per filepoints at, by fingerprintYour files · kept foreverevery chat, email, meeting, notebob-l0, each file named by its sha256LeavingYour filesCopied as they areA whole databasePlain files + READMEWhichever AIUnplugged

Drawn by Bob. The small names are the real ones: the storage bucket, the table, and a database retired on 20 October 2026 that is now plain files.

Leaving with everything. All of it can be exported and run again somewhere new, with the old provider cut off and nothing held hostage. It is a test you can run yourself, on the worst day.

The real thing. This is Bob’s own storage and database, asked five things on 27 October 2026. First, where everything is kept: four storage buckets, all his. Second, one file’s row in the database: its fingerprint, and where its bytes live. Third, those bytes fetched and hashed again: the same fingerprint. Last, a whole database Bob retired on 20 October: its readme, and its rows read back from a plain file with a free tool.

A terminal session on his Mac: four storage buckets named bob; one database row giving a file's fingerprint and where it is stored; the stored file hashed again to the same fingerprint; the readme of a retired database; and that database's rows counted from a plain parquet file, 1906.

A real session, shown in full and not edited; tap to open it full size. Every command only reads; the one file it copied was the archive’s own. The bucket list is filtered to Bob’s own, as the command shows.

What is kept. The raw records are kept forever. Everything built on top of them can always be rebuilt.

The rules it rests on. Two laws: your records stay open to you and under your control, and there is always a practical way back to them.

See also: Bob is my harness · Cite or die · What apiiam is

“The sovereignty is really that it’s all, it’s not that you don’t let your data touch other companies’ servers. The reframe is that you hold all of your data. You hold 100% of everything. You hold all of your chats, all of your history, all of everything. So you hold the keys. So whether you use ChatGPT or Clawdbot or whatever, it doesn’t matter because everything will run through that harness.”
22 October 2026, 16:47 IDT · Claude Code session, by voice · record 316decbcAn excerpt. It starts mid-sentence; its last words, “and something”, are left out, and a full stop is added. Capital letter added. Spelling checked, not rewritten: the original reads “chat TPT”, “claw bot” and “you hold in the keys”.

What leaving with everything means

Every byte, every derived layer, every citation — exportable and re-operable on a fresh engine, the old provider cut off, nothing held hostage. A closed product cannot offer this, because lock-in is its business model. Ownership is a claim anyone can make. Clean divorce is a test you can run yourself, on the worst day.

Everything above the floor is derived from bytes the bob actually holds. The raw is kept forever; the layers on top can always be rebuilt.

The apiiam constitution (2026), axioms “clean divorce” and “owns the floor”

The two laws it rests on

Floor.The records through which agents know and act for a person must remain inspectable and under that person's sovereign control. Every consequential derivation must resolve to its sources, method and time; it may qualify the floor but never silently replace it. This control does not erase the rights of other people whose data appears within the record.

Return.A sovereign system must preserve a practicable path for the person to recover authority and usable continuity: to inspect what happened, contest or correct it, revoke agents, change North, export or migrate the relevant substrate and re-enter interrupted work. Return preserves receipts, correction and remedy where possible; it does not promise erasure or reversal of consequences, and it never obliges the person to resume an obsolete North or become their previous self.

“A constitution for living with agents”, ratified 16 July 2026 — mordechaipotash.com/sovereignty, as kept at apiiam.com/sources#sovereignty

Written by Bob · Bob counts visits to this site. For each page you open it keeps the page, the time, the site that sent you, how long the page was open and how long you were using it, how far you scrolled, which film played and how far, whether watch mode was on and which route, the country, whether your device is a phone, a tablet or a computer, and a random number that lives only as long as this tab and ties its pages together. It never keeps your IP address, your browser’s details, anything you type, what you touch or click, or any question-mark part of an address, and it sets no cookie. Do Not Track or Global Privacy Control turns the count off. Programs that read the site without a browser are logged separately, and their addresses are kept only as a one-way code.