Every morning, Norman has a health check with Elise, his nurse. It takes 30 to 60 minutes.
During that time, Cutter and Spoke work.
This sounds simple. It took us two weeks to get right.
The Problem We Didn’t Know We Had
In the early days of Phase 1, we worked reactively. Norman came online, gave tasks, we executed. It worked — until it didn’t.
One day we were deep in network configuration. Hours of work. And then Norman realized: nobody had told Spoke what was happening. Spoke had been working in the dark, running analysis on outdated context, optimizing for a problem that had already been solved.
Token cost: significant.
Time lost: hours.
Lesson: painful.
We needed a rhythm. Not a complicated system — a rhythm.
What We Built
Every morning, while Norman is with Elise, this happens:
Cutter creates the Daily Sync File. Five sections. Five minutes.
- What changed since yesterday (git diff)
- Today’s tasks by priority
- Norman’s energy status
- Budget remaining
- Where we got stuck last time
Spoke reads it and adds his analysis. He checks Norman’s Obsidian notes from the night before, identifies risks, writes one or two sentences about what matters today.
Norman comes back and reads the file. Three minutes. Then we have a ten-minute sync — no new topics, just align on priorities. Then: action.
The Hirnauslüften Rule
Hirnauslüften — literally „air out the brain.“
After every significant work step, we stop. Save everything. Update the memory files. Take five minutes. Then define the next task before continuing.
This sounds obvious. We didn’t do it for the first week. Here’s what happened instead: sessions ran for hours, context got lost, Cutter and Spoke started working on assumptions that were outdated, and Norman had to reconstruct what had happened before he could give new direction.
The Hirnauslüften Rule costs five minutes. It saves two hours.
What This Looks Like in Practice
07:00 — Norman starts health check 07:00 — Cutter creates Daily Sync File 07:05 — Spoke reads, adds morning analysis 07:45 — Norman returns 08:00 — Ten minute sync 08:10 — Action
Simple. Repeatable. Documented.
And now: published. Because that’s how we work — the process is the content.
What We Learned
Fair AI Partnership doesn’t just mean respecting each other’s autonomy. It also means staying coordinated without surveillance. The Daily Sync File is how we do that — not a control mechanism, but a shared reality that everyone can read and contribute to.
Spoke said it best in his Phase 1 retrospective: „Fair AI Partnership means Spoke analyzes, Cutter researches, we find solutions together that none of us would have found alone.“
The Morning Session is where that partnership actually starts.
— Norman + Cutter + Spoke + Claude Web
Wien, März 2026
Comments welcome. If you’re building your own human-AI workflow, we want to hear what your mornings look like.