Skip to content
Chapter 2

The Day of Protocols

March 15, 2026

Chapter 2 — The Day of Protocols

Verified sources: git log 2026-03-15 (110 commits) Key commits: a634a6e (structural secret-write) · 81fea95 (3 Surface 4 gaps) · 2f06c03 (brain-constitution v1.0.0) · 9be6529 (Surface 3 VPS IP) · 3f9a85a (kanban workflow v1) · e515c67 (rename Dev/Docs → Dev/Brain)

On March 15, 2026, the brain is not yet a platform — it is still a construction site held up by the force of conventions. And that day, the conventions showed their limits.

The dawn that doesn’t sleep

The night isn’t over when the first commit lands. At 00:37, context-broker is forged — an agent that regulates the brain’s breathing cycle. Inhale: load context. Exhale: release it. A cognitive metronome. The idea seems abstract. It will become an architecture.

Then the projects take the stage. Between 04:07 and 06:28, in a sequence that leaves no time to breathe, TetaRdPG ships two sprints and SuperOAuth goes to multi-tenant Tier 1 in production. The brain is only three days old and it is already shipping in parallel — sessions open, close, BSI claims pile up. The system works. Not cleanly — but it works.

The first security protocol

At 05:47, a quiet commit changes something structural in secrets-guardian. Not a feature. A patch. The distinction matters.

a634a6e — patch: secrets-guardian — secret-write structurel (placeholder+sed), handoff + prompts Tier 1 (“patch: secrets-guardian — structural secret-write (placeholder+sed), handoff + Tier 1 prompts”)

The problem is identified: secret values can pass through the parameters of Claude’s tools — Edit, Write, Bash — and nobody checks. An agent can be well-intentioned and still let a secret slip into a parameter. Behavioral rules are not enough. The rule has to be structural — written into the writing pattern itself, not into a list of instructions.

The pattern is formalized: mandatory placeholder, silent sed injection, unset val. Written into secrets-guardian as non-negotiable law.

The brain names itself

While security tightens, something deeper is being built. Between 07:09 and 08:15, BHP Phase 1 takes shape — the Brain Hot Path. Every file in the brain gets a context_tier in its frontmatter: always (loaded every session), hot (loaded on domain detection), warm (on demand), cold (reference). In nine commits, every agent is classified. It is the brain’s first act of self-awareness: it knows what matters and what can wait.

At 10:18, a commit unlike the others.

2f06c03 — kernel: brain-constitution v1.0.0 — Layer 0 identité, 8 sections, 5 levers + invariants + toggles + multi-agent (“kernel: brain-constitution v1.0.0 — Layer 0 identity, 8 sections, 5 levers + invariants + toggles + multi-agent”)

The brain’s constitution. Not a config file. Not a technical spec. A founding document — one that says what the brain is, what it protects, what it does not negotiate. Layer 0. Identity. Eight sections that set the rules of the game before the agents can play.

At 12:11, a rename that says it all: Dev/Docs → Dev/Brain. The folder that had been called “Docs” from the start takes its real name. It is no longer documentation. It is a brain.

e515c67 — refactor: rename Dev/Docs → Dev/Brain — paths mis à jour (“refactor: rename Dev/Docs → Dev/Brain — paths updated”)

14 minutes later: brain v1 stable. The word is set down.

Three surfaces, three answers

At 11:34, the day’s second security patch lands.

81fea95 — fix(secrets-guardian): 3 gaps Surface 4 — trigger .env.example proactif, règle grep/cat MYSECRETS interdit, génération secrets jamais affichée (“fix(secrets-guardian): 3 Surface 4 gaps — proactive .env.example trigger, grep/cat MYSECRETS forbidden rule, generated secrets never displayed”)

Three holes closed at once. The .env.example trigger becomes proactive — don’t wait for a violation to happen, block as soon as the file is detected. An explicit ban on reading the secrets vault directly in the terminal. And the rule on generating secrets: never displayed in clear text. These three gaps had coexisted since the agent was created, the day before. It took this day to name them and close them.

Detection must be proactive, not reactive. Waiting for a violation to happen is already too late.

The afternoon of deliveries

The afternoon is one thing after another. The backlog is audited — six domains, a prioritized sequence. Cockpit v1 appears with its metrics. The wiki gets its first real structured content.

At 17:12, the kanban pipeline takes shape.

3f9a85a — feat(pipeline): kanban workflow v1 — boot mode + kanban-scribe + cockpit mode

It is not an accessory tool — it is the backbone of how the brain drives multi-session sprints. The kanban-scribe becomes the mechanism that automatically records delivery states, wired to the cockpit.

At 17:47, clickerz.tetardtek.com is deployed — port 3520, SSL, one more project in production. The brain isn’t just building itself — it builds.

Surface 3

At 18:14, a third incident is handled differently.

9be6529 — security: replace VPS IP by $VPS_HOST in handoffs + agents (secrets-guardian Surface 3)

A public IP was lying around in files tracked by git. The fix is surgical — replaced by a variable, no rotation, no critical incident, but the event is recorded. Surface 3 (shell commands) has just been mapped in practice. Each surface — code, chat, shell, outputs — now has its own dedicated protocol. It is not a checklist — it is an operational taxonomy that lets you say exactly where a leak can happen and how to handle it.

The evening

At 18:45, a vision appears in the noise of commits: brain-engine. Local RAG over the brain. The idea that the brain could search itself, not just be read file by file.

At 20:21, the constitution is amended — v1.1.0. North star: autonomy. The brain is not being built to depend on someone — it is being built to know how to manage on its own.

The evening ends with SuperOAuth Tier 1 shipped to production. The brain is three days old and it ships a multi-tenant authentication system.

110 commits. Security surfaces mapped. A constitution written. A folder renamed. And somewhere between the patches and the deployments, the conviction that behavioral rules are not enough — that it takes structural protocols, written into the architecture, not into good intentions.

It is the day of protocols. The day the brain learned that goodwill is not a safeguard.

What was built

  • Context-broker — inhale/exhale breathing cycle (8da4ceb, 00:37)
  • BHP Phase 1 — context_tier propagated to every agent, 4 levels always/hot/warm/cold (07:09→08:15)
  • brain-constitution v1.0.0 — Layer 0, 8 sections, founding document (2f06c03, 10:18)
  • Secret-write protocol — mandatory placeholder, silent sed injection, unset val (a634a6e, 05:47)
  • Surface 4 — 3 gaps closed — proactive .env.example, vault reading forbidden, pipe-only secret generation (81fea95, 11:34)
  • Surface 3 — VPS IP removed — $VPS_HOST as replacement (9be6529, 18:14)
  • Kanban workflow v1 — pipeline boot mode + kanban-scribe + cockpit mode (3f9a85a, 17:12)
  • Rename Dev/Docs → Dev/Brain — the folder takes its real name (e515c67, 12:11)
  • brain v1 stable — multi-machine + story_angle (89b3daa, 12:25)
  • brain-constitution v1.1.0 — north star autonomy (d0ef7cd, 20:21)
  • SuperOAuth Tier 1 — multi-tenant in prod (262e36c, 22:22)
  • clickerz.tetardtek.com — deployed to production (46aae62, 17:47)

Key decisions

Behavioral rules are not enough. An agent can be well-intentioned and still let a value slip into a tool parameter. The 05:47 patch settles the question: the rule has to be structural, written into the writing pattern itself, not into a list of instructions.

Detection must be proactive, not reactive. The .env.example gap reveals a timing problem: waiting for a violation to happen is already too late. The trigger becomes blocking as soon as the file is detected.

The constitution before the features. The brain writes its constitution on day 4. Not when everything is stable — while everything is still under construction. Fundamental rules are set early, not late.

The rename as a founding act. Dev/Docs → Dev/Brain is not a folder rename. It is the moment the system stops seeing itself as documentation and starts seeing itself as a brain.

BHP — the brain learns to rank itself. The context_tier is not optimization — it is a decision about what matters. always = identity. hot = reflex. warm = memory. cold = reference. The brain knows what it is before it knows what it does.