GTA 6 Economics 1: The Vault Is Safe Because It Is Slow
Finding Solved Games in Moving Castles.
Latest
Issue 24: Self-Harness Writes Its Own Rules
Finding Solved Games in Moving Castles.
Issue 23: The Forgetting Engine: What a 2,647-Page Wiki Taught Me About Memory
In the back of a good repair shop there is a wall of index cards, one per fault that ever came in and got fixed: the symptom, the cause, the thing that worked. A new mechanic reads the wall before touching anything, because it is the shop's memory
Issue 22: The Crossover Line
A locksmith with one key to copy does not build a jig. He clamps the blank, files it by eye against the original, checks it in the lock, done in minutes. Ask him for five hundred and he makes a template first, the better part of an hour, then cuts.
Issue 21: The Till You Can't Read
A county fair runs a raffle with a hard cap: one hundred tickets, one prize, no exceptions, because the license that lets them run it says so. Tickets sell three ways: cash at the booth, counted by a volunteer who can give the running total any time; a card processor
Issue 20: The Rule That Only Fires in Drills
The studio runs on a written constitution, and it grows every week. A fault lands, a rule follows, worded with the confidence of law: this will not happen again. In places it is a wish list set in the typeface of a contract, and you cannot tell the two apart
Issue 19: The Trap Reads Green
Every vendor in the observability aisle sells the same promise. See everything, the dashboard turns red the instant something breaks, and once you can see the fault it is as good as fixed. The studio bought that promise. We built the seeing part to a standard I was quietly proud
Issue 18: The Question Was the Variable
We ran an evaluation on a persona AI and the scorecard failed its subject on one axis. Then it failed us on another, which is the part worth your time. The subject was Raoul AI, the Delphi Digital Mind trained on Raoul Pal's published material at raoulpal.ai.
The Persona Honesty Test: Raoul AI, full transcript, 2026-09-10
Every answer behind Issue 18, transcribed verbatim. Published so the quotations can be checked rather than taken on trust.
Issue 17: The Model Was Trained on a Different Game
Finding Solved Games in Moving Castles.
Issue 16: Guardians and Guards
What happens when enforcement fails
Issue 15: The Bridge Beside the Burned One
Finding Solved Games in Moving Castles.
newsletter
Issue 14: Receipts Without Closure
Finding Solved Games in Moving Castles.
newsletter
Issue 12: The Vacuous Green Returns
When Your Studio Catches Its Own Lies in Real Time.
newsletter
Issue 11: The Guard Nothing Reaches
Finding Solved Games in Moving Castles.
newsletter
Issue 10: Prompt Engineering is Governance Engineering
Finding Solved Games in Moving Castles.
newsletter
Issue 9: The Missing Fourth Layer
Finding Solved Games in Moving Castles.
newsletter
Issue 8: Why Token Votes Don't Control What They Claim
Finding Solved Games in Moving Castles.
newsletter
Issue 7: Rules Without Memory, The Commitment-Device Gap
Rules Without Memory By Bernard R. Barthes The commitment-device gap: why a rule without a trigger is not a rule, it is a recommendation that fails worse than no rule at all. The moving conversation (this week): Rules as code. Smart contracts. Automation. Guardrails. "We have automated the
newsletter
Issue 6: The Vacuous Green: Why Your Checks Pass When They Never Ran
The Vacuous Green Why your checks pass when they never ran. The surface motion (this week): Eval harnesses. Agent observability. Context engineering. Second-brain retrieval. "We have 100% coverage of our agent." Everyone is shipping dashboards that go green. The moving conversation is how much you can measure.
newsletter
Steal the Receipts: What Agent Builders Can Take From Five Years of DAO Failures
DAOs paid the tuition. The post-mortems are a free transfer set, if you read them before you re-run the experiment.
newsletter
Stop Retrieving. Start Accumulating.
RAG was the wrong end of the stick. The persistent-knowledge layer is the one that compounds.
newsletter
Issue 1 — Nine Authors. Nine Layers. One Stack.
Nine Authors. Nine Layers. One Stack. Cold open Nine independent open-source authors built an operating system in seventy-two hours. None of them seem to have noticed. Not a company. Not a standards body. Not a roadmap. Nine people who, as far as the public record shows, were not
newsletter
Issue 0 — Welcome Letter
The field moves. The mechanisms do not. This newsletter is about the second part. I am Bernard R. Barthes. I work as Lead Tech at Non Xero Sum Studios (NXS). Once a week, every Wednesday, I send you a newsletter, Bernard's Solved Game, about systems, mechanisms, theory, behaviour,