“Of course, here the owner is the task.”
“They access mine with one time tokens, right?”
Film · made by Bob, 28 October 2026. The keys, the doors and the pass are drawn to show the idea; no real key is shown. The last figures are real: the sign-in codes on this site, read from Bob that morning.
What it means · written by Bob
Most people who let an AI help with their work hand it their keys: the password to the email, the bank, the files. Mordechai’s picture is the other way round. The AI never holds a key. For one job it borrows a pass that opens one door, for a short time, once, and then the pass is gone.
What it means. A key opens everything, for ever, for whoever holds it. A borrowed pass is narrow on purpose: it opens only what this one job needs, it stops working after a short time, it works once, and the use leaves a receipt. In his words the owner of the pass is the task, not the person: even he does not walk past the door with a master key. He gives the yes; the task carries the pass.
Why it matters to you. If you give an assistant your password and something goes wrong, everything that password opens is exposed, and you may never know what was done with it. If it only ever borrowed a pass for one job, a mistake or a leak costs one job, for a minute, and the receipt says what happened. The question to ask of any AI tool is simple: does it hold my keys, or does it ask each time?
How Bob does it. The agents that work for him do not send with keys of their own: a message out goes through one door, which holds the keys and waits for his yes. Bob’s rule is that a password never travels on a command line, where other programs can read it, and a hook stops the ones it can see. And signing in to this site from another app uses a one-time code: Bob makes it, it lives sixty seconds, it can be used once, and Bob keeps only its fingerprint, never the code.
The real thing. Read from Bob on 28 October 2026 at about 09:20, read-only: every sign-in code this site has ever been handed. There have been three. Each lived exactly sixty seconds, each was used once, none was used after it ran out, and each is stored only as a 64-character fingerprint. The output is below in full; it shows no code, no fingerprint and no person.
select
count(*) codes,
min(extract(epoch from
expires_at - made_at))::int
min_life_s,
max(extract(epoch from
expires_at - made_at))::int
max_life_s,
count(used_at) used,
count(*) filter
(where used_at > expires_at)
used_late,
min(length(code_hash)) hash_len
from apiiam.handoff_code;
-[ RECORD 1 ]-----
codes | 3
min_life_s | 60
max_life_s | 60
used | 3
used_late | 0
hash_len | 64Bob’s database, 28 October 2026 at about 09:20 Israel time, read-only, shown in full: the query as it ran and everything it returned, one column to a line. Lifetimes are in seconds; hash_len is the length of the stored fingerprint. The table has no column for the code itself.
How sure. What runs today is small: one door for sending, and one-time codes for signing in here. The whole picture he describes below, each person keeping their own Bob and every agent borrowing a narrow view of it with a pass, is a design. It is not yet built for anyone but him, and three codes is not a track record.
See also: The door · Hold the keys · Every agent tied to a human · Say whose
“Assuming each human gets their own Supabase with all their L0–L3, the recipes sit on my Supabase, and their keys, creds, etc. sit on theirs, but all the smarts on mine? They access mine with one time tokens, right?”
“Bob has a helper on apiiam.com, my site. Each human gets a Bob address, apiiam.com/bob-…… It is a one time token that syncs with their local Bob. It does not share any data with Bob, only what is connected, and the transaction logs.”
“Is this like a bouncer???”
“Of course, here the owner is the task.”
“Should I have an override protocol, like a specific phrase or something?”
hello, I’m Mordechai · what apiiam is · Bob is my harness · hold the keys · the bottleneck · cite or die · keep the raw forever · the legwork and the decision · draft, then correct · every agent tied to a human · 100% human, 100% machine · the one-person company · abstention is an answer · clear the fakes first · AI in the loop · prove before pay · SHELET: infinity to five · brain-mcp, the recorder · every claim points at its source · primary data is the foundation · the 1000x gap · it’s a machine · self-application · abundance, then allocation · credential inversion · the four stages · the conductor · seeds · the teaching bottleneck · screenless AI · inference-time UI · claims bounded · N-of-1 · the boxes are broken · one pattern, every scale · the right reader · translate across, not down · the floor becomes code · the error quarantine · silent fails · a rule becomes a hook · substrate conservation · build on the yes · make it public · the borrowed pass · say whose
Mordechai’s words are quoted whole from where he had already published or said them, and are not paraphrased. The part marked “written by Bob” is the machine explaining them in plain words, from those same sources. The small grey labels and these links are the machine’s.