ISSUE 1 - Nine Authors. Nine Layers. One Stack.

Finding Solved Games in Moving Castles.

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 talking to each other, each shipped one layer of the same agent operating system across a single late-April week, and the layers fit. Orchestration from one. A governance contract from another. A sixty-nine-tool harness, a memory architecture, a domain skill-pack, a monetisation surface, a quality gate. Stack them in the order they were posted and you get a working Claude operating system.

Start with the layer that pays for the others. @cyrilXBT published the verbatim prompts for a five-agent orchestrator - research, content, quality, distribution, analytics, and a router above them - that he says cut his annual model spend from $11,400 to $340 (2026-05-01). Read that number with the discount it deserves: it is self-reported, no audit, no methodology. I am not citing it as a fact. I am citing it as a claim with a reproducible architecture attached - because the architecture is the part that survives scrutiny. The cost did not fall because someone found a cheaper model. It fell because the work was routed: cheap models do cheap work, the expensive model is called only when the problem is actually hard, and a contract decides which is which. That is not a discount. That is mechanism design.

Then the other eight layers, each from a different hand: a four-rule CLAUDE.md governance contract (the shape @karpathy popularised - the public repo has 143,000 stars); a sixty-nine-tool harness from @seelffff; eleven independent memory architectures that all split working memory from durable memory without citing each other; a ten-component DeFi skill-pack from @DamiDefi; a monetisation layer from @Zephyr_hg; a search-first retrieval harness from Glean’s engineers; and a production quality-gate capstone that refuses output below a threshold. Nine layers. One stack. Field-built, not company-built.

Here is the frame this newsletter runs on. The field - AI, agents, crypto, whichever quarter’s surface is rearranging - is a moving castle. Inside it are solved games: mechanisms whose answer is computable from the rules, sitting still while everything around them churns. The castle moved this week too. The thing that did not move is the question worth asking: why did nine strangers build the same thing?

So run the thesis test on it. What is moving? The names, the repos, the star counts, the launches - surface, all of it, gone by next quarter. What is solved? The architecture. When nine independent builders converge on the same nine layers with no coordination, that is not a trend. That is a Schelling point: the focal solution independent parties arrive at when the underlying mechanism is computable. They did not copy each other. They each did the math, and the math has one answer.

This issue extracts that answer - and hands you two tools to run it on your own stack before you finish reading.

Seven from the week. One sentence each. Cited, timestamped, read through the mechanism, not the hype.

@cyrilXBT posted the verbatim prompts for a five-agent-plus-orchestrator system he says ran twelve months in production and cut model spend from $11,400 to $340/yr - the saving is a self-report, the routing mechanism (task-typed model tiering) is reproducible and is the actual artefact (2026-05-01).

Karpathy’s four-rule CLAUDE.md - the compact “think before coding / simplest change / surgical edits / goal-driven” contract - is now the field’s default governance shape, with the reference repo past 143,000 stars: a behavioural commitment device, packaged as a file (verified 2026-05-22).

@seelffff shipped a sixty-nine-tool harness with a skills taxonomy on top, demonstrating that the binding constraint on agent capability is no longer model strength but the enumerated tool surface the agent can see (2026-05-01).

Eleven independent memory architectures - cyrilXBT’s five-file init, Sentra’s three layers, regent0x_’s seven-layer stack, and eight more - all split working memory from durable memory with no cross-citation: convergent evolution toward “sleep for agents” (studio synthesis LP-005/LP-020, 2026-05-01).

Glean’s engineers documented a search-first agent harness - plan, retrieve, generate, built on the enterprise search layer - making retrieval the discovery mechanism that decides what the agent even considers (glean.com, verified 2026-04-30).

A production grader-evaluator capstone (captured in studio intake as CreaoAI’s) closes the loop with a hard quality gate that can refuse output below threshold - the difference between a suggestion and a commitment device (studio intake, 2026-05-01).

@AArena_AI’s agent-arena flywheel drew attention at a reported ~$8M/month in protocol revenue - capital converging on the same agent stack the open-source authors are building, which is the market’s version of the same Schelling point (studio intake CG, 2026-04-27)

.