apiiam

“Someone else’s L3 can become an L0.”

2 June 2026, 20:05 IDT · Claude Code session · record 42c9a3cb

One person’s finished thought is the next person’s raw material.

The title is his, quoted below. L0 is his word for the raw layer, the record exactly as it came in; L3 is the top, what a person decides. The line under the title is Bob’s plain English for it, not his.

Film · made by Bob, 28 October 2026. The two stacks are drawn to show the idea, about nobody. The ruling at the end and its record are real, read from Bob that morning (shown below).

What it means · written by Bob

Bob keeps everything in layers: the raw record at the bottom, exactly as it came in, then what was worked out from it, then what Mordechai decided. This idea is about what happens to the top layer when it leaves. A finished thought, once it is published or sent, does not arrive finished. It arrives as raw.

What it means. When you send someone your conclusion, it lands at the bottom of their stack, not the top. They keep it as it came, read it, work it out, and decide for themselves. The same holds for one person over time: your own conclusion, read again months later, is raw to you then. Nothing is ever copied upward into someone else’s decisions; it always comes in again at the floor.

Why it matters to you. If you run a company, most of what reaches you is someone else’s conclusion: a report, a proposal, a summary from a tool. Treat it as raw. Keep it exactly as it arrived, and do your own reading on top of it. Then, when a decision is questioned later, you can show what came in and what you made of it, as two different things.

The real thing. At 09:07 on 28 October 2026 Mordechai made a ruling about a page on this site. Bob stored it twice over: first his words as a raw record on the floor, named by their own fingerprint, then the ruling, pointing back to that record. Read again that morning, the bytes still hash to the same name. The same lanes hold every ruling of his taken this way, and every spoken answer Bob has sent to his phone, kept as raw.

A terminal session on Bob's database. Ruling 7b20d29e, topic apiiam/rule-to-hook-vendor-names, fingerprint 155a923ec9c9c395. Its record on the floor: lane attestation, author me, 2026-10-28 07:07:00 UTC. The ruling's bytes hashed again: true. Then two lanes counted: attestation, me, world, 948; mobile_speak, agent-mine, self, 8285.

A real session on Bob’s database, 28 October 2026 at about 09:20 Israel time, shown in full and not edited; tap to open it full size. Read-only. 07:07 UTC is 09:07 Israel time. “attestation” is the lane his rulings come in on; “mobile_speak” is the lane of Bob’s spoken answers to him. Counts only; no ruling or answer is shown beyond this one, which is about this site.

How sure. This is a working idea of his, not a proven law. He raised it as a question, asking what the machine thought of it, and framed his own view as a belief (his words are below). The page shows two places where Bob does it today; it does not claim that everything he sends is kept this way. The vault note that named it a law was written with an AI, so it is not quoted here.

See also: Keep the raw forever · Primary data is the foundation · Every claim points at its source · Cite or die

“i would say the l0 is the most raw digital copy we have that is an axiom also something completely different i was thinking that when an l3 becomes published or sent in an email etc it should maybe become a l0 again ie one human’s l3 becomes another human’s l0 what you think of that ????”
6 May 2026, 09:45 IDT · Claude Code session · record b263c216Quoted whole. Spelling checked, not rewritten: the original reads “diff”, “i wa”, “ect”, “humans” and “becoms”.
“i guess this also means that the l0-l3 is by definition unique to each human even though individual ln could be shared … the lower down the ln the more objective the higher up the more me”
6 May 2026, 09:52 IDT · Claude Code session · record 050bafc8An excerpt. The middle, an example that names two other people, is cut. Spelling checked, not rewritten: the original reads “alo meens”, “defn”, “tho”, “indurvidual” and “cound”.
“an L0 is either just when something is born or it is when something is made personal for this person or this entity. … Someone else’s L3 can become an L0. And even my L3 from another time can become my own L0, I think.”
2 June 2026, 20:05 IDT · Claude Code session · record 42c9a3cbAn excerpt. The opening (“Another thing I’d really like to talk about is that”), a stray “Sor.” and his closing ask to talk it through are left out.
“wait there is not more l3 there is l0 l1 l2 l2plus then l3 is the human ai surface or the human l2 surface and then l3 becomes new l0”
9 June 2026, 18:40 IDT · Claude Code session · record 6292e44cIt corrected an AI that had been storing the top layer as a fixed thing. Quoted whole. Spelling checked, not rewritten: the original reads “surafce”.

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.