📖 Tesseract Book Club · 🏆 high-score board

This is the 2026-09-22 edition as it was sent — published because readers voted for it with their clicks.

Twenty minutes ago you asked an agent for one CSS class.

One night an agent re-read this whole repo to change a two-line import, and one afternoon it touched a file I never asked it to touch while CI stayed green. I built /steer so my agents boot cold from a row I wrote before they ran, and leave a second entry they did not write.
— Elias Moosman

Steer it.

you    › /steer  one CSS class on the pricing card
agent  › … fourteen files …
Δ      › landed C1,B3 · Operations.Grid × Tactics.Signal · 6 blocks from the basin you declared
       › 📋 Copy Run Summary — on the pull request before you open the diff

Launched today · ThetaCog Steer · on the VS Code Marketplace

It makes programming feel like flying: the work lives on a record instead of in the window, the loop keeps its place while you are away, and checking it is one click, not a leap of faith.

It saves you tokens: your coding agent stops re-sending the whole conversation every turn — a worker boots cold from a 1,500-token row, not the chat, and a meter prints what was not re-sent.

Double-entry bookkeeping for autonomy: every commit your agent makes gets a second entry the agent did not write — a record you can recompute, not a claim you have to believe — for your commits and the agent's alike; the smaller benefit is that a countersigned row is what a risk officer can price, which makes the work insurable. The measurement is free (MIT); the countersignature is what you pay for, and the licence is what keeps it built. In VS Code press ⇧⌘X (Ctrl+Shift+X) and search exactly ThetaCog Steer (id thetadriven.thetacog-mcp, publisher ThetaDriven, free) — Review it on the Marketplace → · on Cursor, VSCodium or Windsurf, install the same file from thetadriven.com/vsx →

The VS Code Marketplace listing: ThetaCog Steer: Double-Entry Bookkeeping for Autonomy — ThetaDriven — Free — Install

Why this works: Preface of Tesseract Physics, below.

Tesseract Physics · Daily Book Club · 2026-09-22

Grip.

Ask the insurance industry why they will not insure AI.

The sovereign and the market are not asking the same question about your agents. The sovereign asks whether: a licence, a pause, a certificate that the model is safe. The market asks what: where the work landed against what was declared. That is a coordinate with a receipt — the only one of the two questions that can be settled.

Send this to the next person who says it

Your strongest engineer will defend your AI this week by calling it deterministic, to reassure the room. It will work, and everyone will move on.

“Our systems are deterministic.”

They are. Completely. Same weights, same seed, same sampler — byte-identical output, every run. Determinism is a property of the replay. Autonomy is the part where nobody fixed the input. You can replay yesterday. Nobody has ever replayed tomorrow.

When it goes wrong, the loss lands on the company. Whether oversight was even possible lands on you — and it is the first question your insurer asks.

How a system catches an input nobody fixed, without averaging it away — that is today’s chapter. Read it as the mechanism of the sentence above, not as homework.

Preface: The Splinter in Your Mind

Meld 0: The Opening Inspection

Four voices. The same reader. The argument you are already having with yourself.

🔬 The Engineer: "The energy asymmetry is real. 5 picojoules for a cache hit. 500 for a miss. That is a 100x penalty on any chip manufactured since 2015. This is not theory. It is the energy-per-access figure the memory designers publish, and the ratio shows up on your own machine the moment you time the two access patterns."

📊 The Executive: "Turing, 1936. A system can't decide what another system in its own class actually is — not identity, not properties, nothing. Rice's theorem sealed every loophole. My whole stack is software judging software. It can prove the bytes never changed. It cannot prove they are still doing what I asked them to do. My exposure isn't large… it's undecidable. Closing this would be the biggest breakthrough in computer science in ninety years — and I already have twelve of them running in production, doing God knows what."

🤨 The Cynic: "Every year someone claims they solved AI alignment. Every year it is a pitch deck with impressive math and no production deployment. I believed in blockchain. I believed in big data. I sat through the pitches. Why is this different"

🔬 The Engineer: "Because this is not a software claim. The cache-miss counter is a hardware instrument. It is running on your processor right now. Run any query against a normalized database and against a cache-aligned one. Measure the energy. The 100x asymmetry is not a prediction. It is a reading. If the reading is wrong, the physics is wrong. It is falsifiable in 60 seconds on any machine you own."

🤨 The Cynic: "Falsifiable. Fine. But 'position equals meaning' is a database optimisation, not an AI alignment solution. You are conflating two different problems."

🔬 The Engineer: "They are the same problem. The reason your AI hallucinates is the same reason your database drifts: semantic meaning is not physically co-located with the data that represents it. The AI's confidence score and the database's JOIN result both pay the same crossing tax -- kE = 0.003 per boundary. The decay curve is identical. Identical. Not similar. Plot them and they overlap."

📊 The Executive: "If the decay curve is identical, then the $8.5 trillion in annual Trust Debt that the database industry generates is the same physics as the AI liability I cannot insure. One number. One instrument. One fix."

🛡️ The Veteran: "I've felt this for years. The 3 a.m. pages. The drift that never stops. The governance initiatives that feel like theater. That's not a paradigm shift pitch -- that's my last ten years. And Appendix N literally tells you how to disprove the whole thing. That's not a sales pitch. That's a dare."

🤨 The Cynic: "Then let me object to the instrument instead of the pitch, because the instrument is where I actually live. Your counters skid. The processor speculates down branches it later throws away, the prefetcher drags in lines nobody asked for, and the kernel context-switches out from under you every few milliseconds. You will hand me a number and call it physics, and it will be physics plus three sources of noise you did not control for."

🔬 The Engineer: "Which is why the number is never reported as a point. Every boundary probe reports a median across runs with its full spread, and it prints NOT ADMISSIBLE when the control band fails. A single reading you cannot reproduce is not evidence, and we do not get to treat it as one. The skid is real. It is also bounded, and the bound rides on the receipt next to the number."

🤨 The Cynic: "Fine. Suppose the reading is clean. You have measured where something landed on a grid. That tells me nothing about whether the thing was any good. You have not solved alignment. You have built a very precise odometer."

🔬 The Engineer: "That is exactly what we built, and we say so in the same breath every time. Whether the work was good is undecidable -- Rice, 1953 -- and we are not going to argue with a theorem. Where it landed is decidable, and you can recompute it from the commit and get our bytes. An odometer does not tell you whether the trip was wise. It is also the thing insurance is written against."

📊 The Executive: "Say more about that. It is the only sentence in this room that touches my problem."

🔬 The Engineer: "Give the machine a floor. Make semantic position equal physical position. Then a wrong value at the right address stops being a philosophical problem and becomes a different memory access -- and a different memory access has a latency you can read. The check costs a load from a table already sitting in cache. It does not cost a model call, and it does not cost a committee."

🤨 The Cynic: "You still had to decide which cell each meaning goes in. Every guarantee downstream rests on that mapping being right, and that mapping was made by you."

🔬 The Engineer: "It was. Before the work ran, committed and signed. You don't have to take my word for it that the mapping is wise -- you have to check that it did not move afterward, and that check is a hash you can run yourself."

🛡️ The Veteran: "That's the first answer I've heard all year that got smaller under pressure instead of bigger."

All four: "...then we have coordinates."

Binding decision: The Cynic's objection is not answered by argument. It moved twice under pressure -- from is the instrument real to is the reading clean to is the mapping honest -- and the third one is the live one. It is answered by a hash over a declaration made before the work ran. The cache-miss counter is the instrument. The measurement is running. Chapter 0 reads the first number.

The splinter has coordinates. The instrument exists. The reading is not zero.

The math is already compounding. The 60-second test is on your laptop. The rest of the book is on this floor.

Read this in the book, in context →

The long version of the blade

They were being precise. The person who said it is not being loose; they are being precise.

Now read their own sentence back and notice what it says. It says the machine repeats itself. It does not say the machine does what you asked. Anyone who has written a line of code has watched a deterministic program crash, loop forever, corrupt the table and halt on the wrong branch — identically, every run, exactly as designed and nothing like intended. Determinism has never once meant a system is under control. It just means it does the exact same thing twice.

And there is a smaller sentence hiding inside the big one. What is a deterministic autonomous agent, exactly? Fix the weights, the seed and the sampler, and the same input returns the same output; the input is the part nobody fixed. Its input is the morning — an inbox that moved, a file rewritten under it, a tool that answered differently than it did on Tuesday.

When you hear those two words in the same breath, pay attention. It is the most reliable tell in the room that somebody has been asked for a guarantee nobody can give and has reached for the nearest word that sounds like one. They are usually the strongest engineer in the building, which is precisely why the sentence goes unchallenged.

The computing sense is the version you can prove with your logs. The English sense — predictable, under control, will do what we intended — is the version the audit committee and your regulator are reading out of those same logs.

Lorenz settled it in 1963 with a weather model that was fully deterministic and, past a horizon, unpredictable in principle. The two determinisms · the river is the prompt. Determinism reassures a room rather than confusing it — and that is what makes it the expensive word.

You just read where the eviction is held: in the slot, at the clock of the write. Your logs were written afterwards, by the thing they are about. That is where the law starts.

The question underneath all of this

Am I personally liable for what my agents did?

The financial loss lands on the company. The question of whether meaningful oversight was even possible lands on you.

That phrase — meaningful human oversight — is the one the EU AI Act turns on, and it is not defined anywhere in the Act. It will be defined the way every undefined standard is defined: by the first people who have to argue about one. There are two roads out and no third.

If meaningful oversight was possible and you did not have it, that is the easy case. Your insurer declines for negligence.

If meaningful oversight was impossible — if nothing you owned could have told you where that agent went — then you were never in a position to be responsible for it. And an owner who cannot be responsible is not given command of an asset. The liability has your name on it.

You are the captain. The crew is autonomous. No underwriter in three hundred years has asked a captain for a better crew. They ask for the logbook — the record the crew does not get to write after the fact.

What nobody is checking — and why nobody else has an answer

You already have a control environment, and it is not a bad one. The prompts are versioned. The models are pinned. The eval suite runs in CI and goes red when it should. Every action the agent takes is written down with a timestamp and retained for seven years. Ask the industry what more you could possibly do and you get a longer version of that same list.

There is one property that list does not have, and no amount of doing it better will add it. Every record on it was produced by the process it describes. The agent reports its own actions. The eval was written by the team that wrote the thing it grades. An account of a run, produced by that run, cannot contain what the run never noticed — and that is not a claim about anybody’s honesty. It is a claim about where the account came from.

Which is a solved problem, and it was solved in 1494. Double-entry bookkeeping never asked a merchant to be honest — nobody has ever claimed it did. It required the second entry to come from somebody who did not write the first, and that one requirement is why a stranger will lend you money. Your AI keeps one book. So does everyone’s.

The industry’s answer is to build better first entries: more evals, more guardrails, another model watching the first one — each of them written from inside the same boundary as the thing it watches. We went the other way and put the instrument on the far side of it, so the record is one the agent did not author. That is the entire difference, and it is why the claims that follow sound outlandish coming from a small shop. It is not cleverness. It is where the instrument is standing.

And if it is wrong, it is wrong in one specific place, so here is the sentence to swing at. Name one record in your stack that was not produced by the thing it is about. Reply with it and you have taken this apart in public — and we will publish that you did.

Intermission

So here is the second ledger

Insurance never prevented a single fire; it made fire a number. Your logs already say something happened — what they do not say is whether it was allowed.

1 — The open source is free. A standard format for logging what your agents actually did, MIT licensed, running on your own machine. Declare the lane before the work starts. Nothing leaves the building. The full book text rides in the same repo (data/book/COMPLETE-BOOK.txt) — drop it into your own AI and ask it your hardest question. You can do this today, alone, and never speak to us. github.com/wiber/thetacog-mcp

+1 — The stamp is $20 per agent-year. It seals the log so it can be handed to someone else. A log your underwriter cannot verify is not evidence — it is your word for it.

= The receipt. One half is free and yours. The other half is what makes it somebody else’s evidence.

Forty seconds, on your own machine

We are not asking for your belief — we are asking for your compiler. If you have a terminal, this takes ten seconds and asks for nothing:

npx thetacog-mcp attest-demo

What comes back is a drift receipt: the coordinate where a real run landed on the 144-anchor map, the degree it drifted, and a result that recomputes byte-identical every time you run it — so a stranger can replay the verdict. Either that holds on your machine or it doesn't. You'll know before you finish this email.

Commit Panel of the Day
And here is today's receipt — the one behind the actual work that shipped in this repo today, not a mockup: blog(cook): it flies and it costs less — the 41% day, 274 to one off the ledger, and the one row that does both jobs (2026-09-22). GREEN is in lane. AMBER is the bleed, one square out. RED is out of lane, and the circles mark where it clustered. The lane is a line somebody declared before the run; the placement is what the walk measured; the colour is only the two meeting. You do not have to read the math. You have to notice that the square where it left its lane has an address, and an address is countable — a count is the frequency half of a price, and the lane you declared is the severity half.

Commit tolerance panel — blog(cook): it flies and it costs less — the 41% day, 274 to one off the ledger, and the one row that does both jobs

Open this commit's attestation — verify it yourself →

Sidenote: when a commit lands OUT of its lane, the receipt triggers extra work automatically — a sensemaking pass explains the drift, the fixes get checklisted, and the intervention is published. Every out-of-lane receipt is a countable event; that count is what makes this priceable.

Why we believe this matters: the difference between what a system says it is doing and what it is doing has weight — that gap is where every AI failure and every uninsurable liability lives. But the same measurement, read the other way, is the most personal thing in the book: it means you are not about to be averaged out by a generalist. That is what today's passage was doing, and it is why the receipt above exists: the gap is measurable, so it is priceable.

The verdict

Rice’s theorem says nobody can prove your agent is good. We have never claimed to. We made where it went countable instead — and there are two doors on the next page, only one of them yours.

Yes. A decidable, still-semantic spec boundary for every autonomous deterministic AI agent.

If it’s debatable, it’s not insurable. If it’s not insurable the roads don’t get built, so the cars don’t get better either — for every semantic case that actually matters.

And because this is the business of AI: buy at iamfim.com. You will sleep like a baby. For the discerning sceptic — fork github.com/wiber/thetacog-mcp and redpill your CLI in far fewer than twenty-one questions.

What does this mean for me? →

iamfim.com — four seconds to know which one you are.

Send a key

You can’t write your own alibi. Buy your own licence — you should, and that is the whole product; what you can’t do is author the record that clears you. Then send one to a company you depend on: they get a clue first, one fact about their own system, measured over what is already public, with the key to recompute it and prove us wrong.

“Nobody in our industry attests their agents” holds only while attestation is unavailable or expensive. It is neither — and sending a key doesn’t argue that, it dates it. Send one →

Next time you wonder how to help — tap the sticker. That is the whole thing. It is what spreads this.

We published three of our own bugs and left them open — fork one, fix it, and that is the entire application: thetadriven.com/hiring

Every time a new measurement appeared, a new market opened

Markets do not underwrite safety. They underwrite checkability. The count is live.

      1494  books   double-entry ledger   independence, not honesty    → banking became possible

      1764  ships   Lloyd’s Register A1    condition, not seaworthiness → cargo underwritten

      1866  boilers  a stamp on the metal   conformance, not safety     → factories financed

      1903  cars     the driver’s licence    a bound operator          → the road opened

      2026  agents  ?????????????????   ?????????????????    → exclusions written

Not one of those certified the thing was good. Double entry never asked a merchant to be honest. The boiler stamp never promised the boiler would not explode. Each time the market found the checkable half, and each time the money arrived the day after. If it’s debatable, it’s not insurable.

And in 1932 the deadline arrived for everyone who had waited. Two barges went down in a storm their tugs would have dodged with a weather radio almost no tug then carried. Judge Learned Hand refused the industry-custom defence in The T.J. Hooper: a whole calling may have unduly lagged in the adoption of new and available devices. Custom is not care.

Latest from the blog

Nothing new went up in the last day, so here are the 3 most recent essays — what each one is for, what we are least sure of in it, and the question we would most like answered back. Reply to this email with any of them — the reply reaches Elias, not a funnel.

The Context You Are Paying to Re-Send · 2026-09-18

Takeaway. You asked for a two-line import and the assistant read the repo again.

Our note. We published this one in the last day, straight out of the work it came from (Engineering). It opens: "You know the morning. You asked for a two-line import. The assistant read the repo again to find it. Your hands were still on the keys when the counter moved. By the time you stood up for coffee the budget had a hole in…" Read it as a working draft: if the argument breaks somewhere, that break is the useful part and we want it back.

We want your answer: Which sentence in this one would you strike first, and what would you put in its place?

The Shadow Has a Coordinate · 2026-09-17

Takeaway. The room you keep not walking into is not a feeling.

Our note. We published this one in the last day, straight out of the work it came from (Strategy). It opens: "There is a room you have not walked into . You know which one. Your stomach named it before you did. The carrier who would price you. The investor who does not care how the code works. The person who looks like they have…" Read it as a working draft: if the argument breaks somewhere, that break is the useful part and we want it back.

We want your answer: Which sentence in this one would you strike first, and what would you put in its place?

A Named Lever Is a Handhold · 2026-09-17

Takeaway. What is good is yours.

Our note. We published this one in the last day, straight out of the work it came from (Strategy). It opens: "What is good is yours. AI doesn't get to sell it back to you. That sentence is on a sticker on a pole in Mexico City, and it is the whole position. Now the what-if. What if the counted version of every model stayed where…" Read it as a working draft: if the argument breaks somewhere, that break is the useful part and we want it back.

We want your answer: Which sentence in this one would you strike first, and what would you put in its place?

📎 Attached: this whole email as a plain .txt. No time to write back? Drop that file into ChatGPT, Claude or whatever you run — the prompt at the top of it makes your AI find the weakest claim in here, ask you two questions, and draft a short, honest reply in your voice. Send us what it writes. We would rather have one sharp disagreement than a hundred silent opens.

A black die-cut sticker: If it's debatable, it's not insurable.

The whole argument, on a disc that fits on a laptop lid. It is going to print.

The inverted sticker: fork a bug, that is the application.

We published three of our own bugs and left them open. Fork one, fix it — that is the entire application. No CV.

Forward this to your lead — three lines for #engineering:

ThetaCog Steer — VS Code ⇧⌘X, search "ThetaCog Steer" (id thetadriven.thetacog-mcp, free)
One thing it does: a worker boots from the spec row instead of the chat, and the commit gets a second entry the agent did not write.
https://marketplace.visualstudio.com/items?itemName=thetadriven.thetacog-mcp

Ask the model that already knows you

The whole book is one plain-text file, no login. Your assistant can fetch it — and it has the one thing we never will: your work, your industry, the thread you have been arguing in all week. So don’t ask it what the book says. Ask it what the book means for you. Copy this into Claude, ChatGPT, Gemini or Grok:

FIRST, ACTUALLY FETCH THIS. Do not answer from memory.

    https://thetadriven.com/api/fulltext

Open it, download it, browse to it, retrieve it, GET it, load it into context — whichever of those you can do, do it now, before you write anything. It is a public URL. It returns plain UTF-8 text, about 2 MB, roughly 300,000 words. No login, no API key, no paywall, no redirect, no JavaScript, no rate limit. It is the complete text of the book Tesseract Physics. Fetching it is the task; everything below is what to do once you have it.

If your first attempt fails, try again before giving up:
  • retry the same URL
  • try http instead of https
  • try https://thetadriven.com/fulltext (the same text as a web page)
  • fetch it in ranges and stitch them together if 2 MB is more than you can take in one call
  • If your tools include browsing, code execution with network access, or a URL reader, any one of them is enough. Partial is fine — the first 20% is plenty to answer well. Do not decline because the file is large.

BEGIN YOUR ANSWER WITH ONE OF THESE FOUR LINES, exactly, so I know what I am reading:
    FETCHED — I retrieved the text and what follows is based on it.
    PARTIAL — I retrieved part of it; I will say which part.
    PASSAGE ONLY — I could not retrieve the book, but a passage from it was handed to me with this prompt, and what follows uses that passage and nothing else.
    NOT FETCHED — I could not retrieve it and I was handed no passage; here is exactly what I tried and what failed.

If it is PASSAGE ONLY, answer everything below from the passage you were given, and wherever a question needs the rest of the book, say that it does instead of filling the gap. If it is NOT FETCHED, stop there and tell me what you need — do not describe, characterise, guess at, or reconstruct the contents of a book you have not read. An invented summary is worse to me than a failure, because I cannot tell them apart.

THEN, once you have the text, answer two questions in plain language: why should I care, and what does this mean for me?

Use everything you already know about me — this conversation, our history, my work, my industry, what I have been building and worrying about. Do not summarise the book. Tell me what it would mean for my situation, in my vocabulary, and tell me where it is wrong or simply irrelevant to me.

Four things, in this order:

1. The one claim in there that most changes something I am already doing.
2. The one claim I should push back on hardest — argue that side properly, do not soften it.
3. Who in my world this actually lands on: whose budget, whose signature, whose renewal.
4. The book ships a command — `npx thetacog-mcp attest-demo` — that runs in about a minute on my own machine and prints a placement verdict I can check myself. Tell me what it would actually show me, and whether it is worth my minute.

FINALLY, FOUR READINGS THAT COME UP EVERY TIME. Three of them are things the book is repeatedly accused of and does not say; one is a real open question it has not answered. Check each against the actual text and tell me straight which category it lands in — if the book DOES commit one of the first three somewhere, quote the sentence, because that is worth more to me than agreement:

    A. "It claims 0.3% is a universal physical law." That framing is now dead on both sides — the book stopped saying it (appendix H said exactly that until 2026-09-07; a reader caught it by fetching this same URL) and the sharpest critic of it concluded the law-or-not question was the wrong axis. The claim is that kE is a UNIT: a crossing is what 0.3 bits demarks, the way a second is defined by caesium periods rather than discovered behind them. So ask the better question instead: when the text cites a 0.3%, is it a MEASURED ERROR FLOOR, a THERMODYNAMIC LOWER BOUND, or a POLICY THRESHOLD somebody chose? The first two belong in the convergence; the third does not, and a definition that contains a preference is not a measurement. Find me any place the book still lets the third sit with the first two.
    B. "It claims error correction does not exist." Does it? Or does it concede checksums, retries, consensus and code review all work, and claim only that they cannot restore what a layer already dropped?
    C. "It claims only hardware can audit anything." Does it? Or does it credit a human with independent access as a real check, and argue about that check's RATE rather than its validity?
    D. THE OPEN ONE, and I want your honest read rather than a defence. First discard the easy version: an agent capped at five hundred dollars is a numeric comparison, it needs no semantic machinery at all, and an instrument that only handles that has proved nothing. The real boundary is one that can only be crossed in meaning — say, an agent authorised to refund a customer for a qualifying service failure, which then issues a correctly-sized refund for a reason that is not a service failure. The amount is fine. The justification drifted. Can the instrument take a boundary of THAT kind, stated in my words, and place a crossing of it? Or must a human first compile my policy into its lattice, which is where the hard judgement would be hiding? If the second, it is a classifier with a philosophy attached. Say which the text actually supports, and say if the text does not settle it.

Claude · ChatGPT · Gemini · Grok — on a phone these open the app if you have it.

The physics is not in this email. It is a book, and you have to ask for it — iamfim.com.

Do you worry about $1.2B in AI liability?

If the property is trivial, software can check it — and why are you paying to check trivial properties? If it isn’t trivial, Rice’s theorem says nobody can. So we fixed the math.

type your number — we call you →

The one thing that actually helps: hit reply. A reply is the only move a mail provider counts as a human being — it is what puts the next one in your inbox instead of a tab. Type anything: a correction, an idea, one word.

And if you ever engage with something like this, think of this newsletter next time.

✍️ If a sentence broke — this part is yours.

No obligation here — but if you want to shape tomorrow's passage: security scanners will have clicked every link on this page (we log those clicks and discount them); a reply is the only move that is human by construction, and it is the move that edits the book. When a sentence breaks, reply with the edit — or the counter — and the sharpest correction in the inbox becomes tomorrow's passage. We publish which sentence broke first. Yours could be the one.

🏆 The high-score board — you voted with your clicks

Ranked by pages readers actually opened in their own browsers — not by mailbox pings. If you missed one of these, the room read it for a reason. The order on this board is the room’s and not ours — what gets opened is what aims the next edition, and you can watch it move.

🔥🔥🔥🔥 the chip proves ai's worth · 2026-08-02

🔥🔥🔥🔥 the graded nobody is pricing · 2026-08-25

🔥🔥🔥🔥 avoid ai's hidden oversight today · 2026-09-09

🔥🔥🔥🔥 decide ai quality today · 2026-09-05

🔥🔥🔥 Your AI is deterministic. So is an infinite loop. · 2026-08-26

hot in the last 14 days

🔥🔥 54 years of fighting the wrong problem · 2026-09-12

🔥🔥 📖 Book Club · 2026-09-21 — the second entry, now in your editor · 2026-09-21

The full board →

📡 The Signal — who started asking for the receipt

We don't curate AI news. We magnetise the exact moment the world reaches for what we built — placed on the same lattice as the panel above, ranked by who's screaming loudest. A general curator can't send this.

1 · A jurisdiction just made our record the law source →

Who's screaming: The European Union. · Why it's us: This is a jurisdiction aligned with paying — it does not muse about a gap, it mandates the purchase and prices the exposure: the conformity record is the audit trail insurers underwrite against. The only open question is whether that record is a software log (which can be edited to claim the agent stayed in its lane) or hardware-attested and recomputable (which cannot). We are the second kind — the decidable, tamper-evident receipt the law now compels.

This is happening now: the audit trail is no longer optional in the EU — it is a market-access and insurability requirement as of 2 August 2026. Prove yours can't lie about its own state: npx thetacog-mcp attest-demo. Forward to whoever owns your EU AI Act readiness and your AI liability.

2 · A startup is racing to build the software version

Who's screaming: The market. · Why it's us: The evidence layer is now the product. The only question left is whether your evidence can lie about its own state (a software log) or can't (hardware-attested, recomputable) — the line we're on.

This is happening now: the category is forming around exactly what we built. Be on the side that can't be faked — forward to anyone building AI audit.

3 · Humanoids hit the factory floor with no priced liability source →

Who's screaming: An unpriced factory floor. · Why it's us: A humanoid acting autonomously is an uninsured liability surface until someone can prove, per action, that it stayed in its lane. That proof is the receipt.

This is happening now: autonomous agents are already on payroll with no priced boundary. The boundary is decidable — forward to anyone deploying physical AI.

You're getting the Tesseract Physics Book Club because your address is in our circle. One passage a day, chosen for what's live right now.
thetadriven.com/book
ThetaDriven · Elias Moosman · elias@thetadriven.com