newsletter
Issue 16: Guardians and Guards
What happens when enforcement fails
newsletter
newsletter
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 13: The Jury of Clones
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 0 — Welcome Letter (v2, corrected redraft)
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,
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 Tape The moving conversation (this week): Rules as code. Smart contracts. Automation. Guardrails. "We have
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 Tape 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