Skip to content
Chapter 11

The brain builds

March 22–24, 2026

Chapter 11 — The brain builds

Verified sources: git log Super-OAuth 2026-03-22→24 (34 commits) · git log OriginsDigital (6) · git log TetaRdPG (55) · git log Clickerz (9) · git log Sakuin 2026-03-25 (2) · git log brain: 0 commits The brain repo has no commits over this period. All the activity is in the projects. That is the proof.

Ten days of the brain building itself. Agents, protocols, kernel, distribution, showcase. But a coordination system that coordinates nothing is a toy. On day 11, the question changes: can the brain build?

The answer comes in three days. Four projects. Four deployments. And zero commits in the brain repo. The brain does not need to be modified to work. The infrastructure is in place.

SuperOAuth — the authentication engine

SuperOAuth opens the dance on March 22. The brain has known the project since day 1 — it is the authentication engine, the service that lets all the others exist.

In one day: a dynamic tenant with DB validation and Redis cache, a complete PKCE authorization server (/oauth/authorize + /oauth/token), a SvelteKit frontend with landing, dashboard, and six docs sections. All of it deployed to prod.

512d2d2 (March 22, 15:53) — feat(pkce): authorization server — /oauth/authorize + /oauth/token e99cc69 (March 22, 15:54) — feat(frontend): SvelteKit dashboard + landing + docs

In the evening, the sovereign email system appears — email verification before activation, account merging by token. Authentication is no longer only social — it is sovereign.

10fbc3c (March 22, 17:59) — feat: email sovereign accounts — verify email before activation, merge via token

On the night of the 22nd to the 23rd, ten prod fixes in a burst. A cascade save that does not persist relations. A dashboard that crashes when the email is null. Unlink provider through a direct DELETE instead of a botched cascade save. Duplicate nickname on OAuth creation. The kind of bugs you only find in prod, with real users (even if the user is you on your own projects).

9af5876 (March 23, 02:02) — fix: unlink provider uses direct DELETE instead of unreliable cascade save

30 commits. A complete PKCE authentication server. In prod.

The four clients

Then the real demonstration: plugging the projects into SuperOAuth. On March 24, in one afternoon, two projects receive PKCE login — OriginsDigital has had it since the day before, Sakuin will follow on the 25th.

OriginsDigital — a video platform — receives the E2E PKCE flow with four providers (Discord, GitHub, Google, Twitch). Six commits, CI/CD pipeline.

TetaRdPG — a web RPG — receives login at 13:01. A localStorage fix for the PKCE verifier (cross-site redirects). Twitch added as a fourth provider. Deployed to the VPS.

8c6777c (March 24, 13:01) — feat: PKCE auth + CI/CD deploy

Clickerz — an idle game — same pattern, same time (13:01 too — started in parallel). Four providers. A settings page to link and unlink. Authoritative server save. Multi-tab sync.

91d1616 (March 24, 13:01) — feat: PKCE auth + CI/CD deploy

“chaque projet = un tenant SuperOAuth. Zero friction auth.” (“each project = a SuperOAuth tenant. Zero friction auth.”)

The pattern repeats so often that it will become a toolkit: PKCE client, tenant bootstrap, NestJS token introspection — extracted as templates on April 5. What took a day for the first project will go faster for the next ones.

TetaRdPG explodes

After the auth hookup, TetaRdPG does not stop. The afternoon of March 24 is a marathon.

Sprint 4: 15 achievements, three community goals, hall of fame, player profile. Sprint 5: a complete quest system — accept, progress, claim, story arcs. Repeatable quests outside the pool. Endurance/damage/XP rebalance. Persistent HUD bar. Healing system renamed. Achievements page.

7651f3d (16:34) — feat(sprint5): quest system + arcs + rebalance endurance/damage/xp cfdc5c9 (17:03) — feat: HUD bar — stats persistantes sous le header (“feat: HUD bar — persistent stats under the header”)

20 commits between 13:00 and 17:36. The game designer — an agent forged for the occasion — structures the mechanics while the code follows.

Clickerz matures

The same afternoon, Clickerz receives its authoritative server save. The game state no longer lives only in the browser — the server is the reference. Multi-tab sync arrives: save on blur, reload from server on focus. A 500ms delay to let the blur finish before the focus reload.

8ce54bf (14:30) — feat: server-authoritative save — wait for server before game starts 79ac1b0 (14:43) — feat: multi-tab sync — save on blur, reload from server on focus

And a crucial safeguard: never save the default state to the server. If the game has not finished loading, do not overwrite progress with an empty state.

Sakuin — from idea to prod

The fifth project arrives on March 25, after the three days of fire. Sakuin — a gamified manga tracker for a friend who does not yet know it exists.

f1cff74 (March 25, 01:43) — init: scaffold complet Sakuin — backend NestJS + frontend SvelteKit + CI/CD + deploy VPS (“init: full Sakuin scaffold — NestJS backend + SvelteKit frontend + CI/CD + VPS deploy”) 108f021 (March 25, 02:43) — feat: Sprint 1 core tracker + SuperOAuth PKCE E2E

Scaffold and VPS deploy in the same commit. Sprint 1 an hour later — core tracker with E2E PKCE. Two commits. A project in prod with login, from zero.

Sakuin is not just one more project. It is the proof that the pattern works: from “j’ai une idée” (“I have an idea”) to “c’est en prod avec login” (“it’s in prod with login”) in one session. Not because the code is simple — because the brain knows the stack, the agents know how to deploy, the toolkit already holds the SuperOAuth NestJS consumer and the deploy workflows.

End of the third day. The dashboard:

SuperOAuth     → serveur PKCE complet, email sovereign, 30 commits, 10 fixes prod
OriginsDigital → E2E 4 providers, pipeline CI/CD
TetaRdPG       → 55 commits le 24 mars (20 entre 13h01 et 17h36), quêtes + achievements + HUD, déployé VPS
Clickerz       → save autorité, multi-tab, 4 providers, déployé VPS
Sakuin         → de zéro à prod en 2 commits (25 mars)

And in the brain repo: zero commits. The brain did not need to be touched. The infrastructure was ready. The agents knew what to do. The kernel held. That is the difference between a tool you use and a system that works.

The brain is no longer a project. It is a multiplier. Every hour invested in the kernel — the agents, the toolkits, the protocols — pays itself back with each new project. The invisible infrastructure that makes the rest possible.

“j’en ai rêvé, le brain l’a fabriqué” (“I dreamed it, the brain built it”)

What was built

  • SuperOAuth PKCE server — authorization server + SvelteKit frontend + sovereign email (512d2d2→e8f5cc8, March 22–23)
  • 4 PKCE clients — OriginsDigital (March 22–23), TetaRdPG and Clickerz in one afternoon, (+ Sakuin on the 25th) (8c6777c+91d1616, March 24, 13:01)
  • TetaRdPG Sprint 4+5 — 15 achievements, quests + arcs, HUD, 17 commits (8ee5080→4d25469, March 24)
  • Clickerz — authoritative save, multi-tab sync, provider settings (8ce54bf→8cc9fda, March 24)
  • Sakuin — from zero to prod in 2 commits (f1cff74→108f021, March 25)

Key decisions

  • One tenant, one project. Each application = a SuperOAuth tenant. The auth pattern is solved once and for all.
  • Toolkits extracted. Recurring patterns become reusable templates. The fifth project benefits from the first four.
  • The game designer. A specialized agent forged for TetaRdPG. The brain does not code the mechanics — it thinks them first.
  • From idea to prod in one session. Sakuin proves that the brain infrastructure transforms the effort/result ratio. The bottleneck is no longer technical — it is creative.
  • Zero brain commits. The infrastructure is ready. The projects move forward without touching the kernel. That is the ultimate test.

Quotes

“chaque projet = un tenant SuperOAuth. Zero friction auth.” — “each project = a SuperOAuth tenant. Zero friction auth.”

“j’en ai rêvé, le brain l’a fabriqué” — “I dreamed it, the brain built it”