Summary/TL;DRThe Postscript Predicted It. The Smell I Missed Wasn't In the Postscript.
The Fourteen Hours essay closed with a postscript naming the next problem: models that ask too many questions or assume too confidently both fail. The mature shape is present, don't ask blind, don't decide silently. Sessions 2 through 6 were that postscript, executed.
Three rules went into the harness over the course of those sessions: a four-mode protocol that gates questions to the modes where they belong, a checkpoint format every turn ends in, and an honest accounting of what trust I had built and what trust I was deferring. Each rule was a response to a specific friction. None of them required a new model. All of them required me to write down something I had been doing implicitly.
What the postscript did not predict, and what I almost missed across all six sessions, was a quieter failure. By session six I had lived two days of swipe, swipe, continue every fifteen minutes, and I described the rhythm as a well-oiled workflow. Each individual tap was effortless. So the part of me that watches for friction never fired. So I adapted to the rhythm. So the rhythm became my workday. The continue-tap was not in any of the rules I added. It was not in any of the encoded learnings. It was just there, and I treated it as a feature when it was a smell.
The micro-rituals are the most dangerous bottleneck because they cost nothing individually, which means the operator never flags them, which means the workflow can absorb the operator into itself without resistance. The result of this stretch was the workflow that worked, the rules that earned their place, and the harder lesson that smoothness in a sustained micro-rhythm is the warning sign, not the success metric.
Where the First Essay Left Off
The first essay closed with a perspective check I owed myself. I had complained about fourteen hours from discovery to deployment. I had to remind myself, in writing, that a year ago that workflow did not exist at all. The complaint was real; the perspective was missing.
The postscript named what I had felt but not yet named: the model asked more qualifying questions than I was used to. At first I read this as pedantic. On a second pass I noticed the questions were catching real conflict between things I had decided in different sessions. The questions were good. I just was not in the mood for them.
The postscript ended on what I thought was the next essay: teaching the model to present rather than to ask blindly or decide silently. The mature shape, I wrote, is the one a good employee uses with a boss: here is the conflict, here is what I would do and why, here is the decision I need from you.
That essay turned out not to be the next essay. The next essay is this one. Because before I could write about teaching models to present, I had to actually do it across five sessions and see whether it worked.
Session TwoNaming the Question Problem
Session two was a small, scoped task. I do not remember what specifically. I remember the friction, and I remember the moment I stopped to fix it.
The friction was the same friction the postscript had named. The model asked questions mid-execution. I had locked the scope at the planning gate. I had said go. And it asked.
I almost typed an irritated reply. Then I stopped, because I had just published an essay about how the questions were good in principle. The honest move was not to push back on the questions. The honest move was to tell the model when questions belonged.
So I added one rule to the harness: questions are encouraged in exploration, planning, and validation. Questions are banned during execution. If the model has a question during execution, it looks the answer up in the docs, uses its discernment, and finishes. If it genuinely cannot proceed, it names the one specific blocker and reverts to planning.
The rule is in the operating contract now. I did not realize at the time that I was also writing the spine of the next essay.
Sessions Three and Four — The Rule Held
Sessions three and four were the proof that the rule was not a one-off fix. Both ran end-to-end without the question problem. The model asked freely during planning. It went quiet during execution. It surfaced concerns during validation, where I wanted them.
I noticed two things in those sessions that I had not predicted.
First, the rule made the planning sessions denser. The model asked more there. I answered more. The plans got tighter as a result. The questions had not gone away; they had moved to the mode where they cost the least.
Second, the validation step caught real things. Things the execution had quietly noticed but not interrupted to surface. By the time validation came, the model could collect its concerns, present them with proposed resolutions, and let me decide whether to accept, steer, or pivot. That is the present, don't ask blind shape the Fourteen Hours postscript had predicted. I had not designed for it. The rule produced it as a side effect.
Session FiveAccidentally Discovering the Checkpoint Shape
Session five hit the per-turn tool-call ceiling for the first time on this workflow. The model had been working for fifteen minutes inside one of my turns, ran out of budget, and stopped.
What it produced before stopping was clean: one paragraph naming what was done, what was next, and that there was no blocker. Then it waited.
I tapped continue. It resumed. The cycle closed in three seconds.
I noticed something at the end of that turn that I did not act on yet but did write down: the shape of that forced checkpoint was exactly the shape every turn should have had from the start. Mobile-readable. Resumable. Compressed. The model had not been producing it voluntarily. The ceiling forced it to.
I added a second rule to the harness that night: every turn ends in done, next, blocker or none, regardless of whether the ceiling is forcing it. That rule is also in the operating contract now.
What I did not notice at the time, and probably should have: I had also, in that same session, accepted a new ritual without flagging it. The continue-tap. Once every fifteen minutes. The ceiling-checkpoint shape was a real win. The continue-tap was a smell I treated as a feature. I would not see it as a smell for another two days.
Session SixThe Ritual Becomes Visible
Session six was the most well-oiled session of the stretch. The four-mode protocol held. The checkpoint format held. The model spawned managed agents to code. It spawned managed agents to validate. Bugbot caught a small handful of real issues on the PR. The Sonnet validator ran the gauntlet. Both passed. I merged.
And my biggest job all day had been flipping back to the app every fifteen minutes to tap continue.
By that evening I had lived two days of swipe, swipe, continue. Every fifteen minutes. The rhythm was so smooth that I described it to someone, out loud, as a well-oiled workflow. The rhythm was so small that no individual tap felt like friction. And the rhythm was so constant that, by the end of day two, I had built my workday around it without noticing.
The work was happening. The trust was holding. The bottleneck had moved completely off my judgment.
It had also done something worse than I realized at the time. It had absorbed me into the workflow as a mechanical component. The continue-tap was not a workflow step the operator was supposed to do. It was a ritual the workflow had imposed and I had adapted to without flagging it. And the adaptation was the failure, not the tap.
That recognition is what produced the next essay (Shifting Bottlenecks, Climbing Ladders) and the canon constraint that came with it. Session six made the ritual visible. Sessions two through five had quietly assembled the conditions under which I stopped seeing it.
What Stuck
Three rules earned their place across the five sessions:
Question gating by mode. Encouraged in exploration, planning, validation. Banned in execution. RTFM and use discernment if you have a question and you are executing. This rule did the most work. It is what turned the model from pedantic into pleasant.
Checkpoint format every turn. Done, next, blocker or none. Adopted voluntarily, not waiting for the ceiling to force it. This rule preserved my attention for actual decisions and made every turn skimmable on a phone.
Honest accounting of trust deferred. Several times across the five sessions, I declined to automate something I could have automated (continue-taps, agent self-validation, fully unattended runs). Each time, I named the reason: I was still building familiarity. The rule is not "do it manually forever." The rule is "name when you are deferring trust on purpose and when you are deferring it by default."
What I Almost Didn't See
The thing I almost missed across all six sessions: I accepted a ritual without flagging it.
The continue-tap rhythm was not in any of the rules I added to the harness. It was not in any of the encoded learnings. It was not in any of the session journals. It was just there, every fifteen minutes, for two days, and I described it positively when I described it at all.
The reason I missed it is the reason it is dangerous. Each individual tap was effortless. Nothing about the act registered as friction. So the part of me that watches for friction never fired. So I adapted to the rhythm. So the rhythm became my workday.
That is the same disease the Burger King manager had. Each of her individual tasks was thirty seconds. Nothing about any single one registered as effort. So the part of her that should have flagged "I am doing all of this myself and the line is not moving" never fired. So she rituals through it for almost two hours without noticing.
The micro-rituals are the smell. Not because they cost much individually. Because they cost nothing individually, which means the operator never flags them, which means the workflow can absorb the operator into itself without resistance.
I have one rule I am adding to the harness from this observation, and it is the most important one of the three: when I notice a sustained micro-rhythm of taps or swipes or approvals, I treat it as a smell rather than a feature. I redesign the workflow to remove the rhythm rather than adapting to it. The smoothness of the rhythm is exactly the warning sign.
It would have been a better outcome to flag this on day one of the stretch instead of day six. The fact that I did not is the data I needed.
What Did Not Stick
Two things I tried did not earn their place.
Pre-emptive long preflight checks before every turn. I tried, briefly, to have the model run oddkit_preflight at the start of every turn. The cost in tool budget exceeded the value. Most turns did not need a preflight; they needed to do the work the previous turn's checkpoint had specified. Preflight stayed at its right place: at planning-to-execution mode boundaries.
Treating "continue" as a feature. I considered designing turns deliberately to fit within the ceiling so that the continue-tap rhythm would feel like a feature. For two days I lived inside something close to that pattern without flagging it. The rhythm felt smooth so I treated it as smooth. The harder reading, surfacing in Shifting Bottlenecks and now in this report, is that a smooth micro-rhythm is the smell. Not the cost of any individual tap; the cost of adapting to a rhythm that should never have existed. The right answer is to use larger phase-aligned turns and treat the ceiling as the safety valve it was designed to be, and to refuse the rhythm before it becomes invisible.
What This Cost Compared to Session One
Session one cost fourteen hours, five pull requests, an hour and forty minutes of broken production, and one moment of saying you idiot, you lied out loud to a chat window.
Sessions two through six, combined, cost something close to that fourteen hours. Spread across five working sessions instead of one. Producing far more shipped work. Without the broken production and without the angry moments.
The model did not get better between session one and session two. The harness did. The harness is mine to write. The model is not.
What the Postscript Got Right and What It Missed
The Fourteen Hours postscript said: the next step isn't fewer questions or more confidence. It's teaching these models to present.
That was right. The four-mode rule is a teaching of when to present, not whether. The checkpoint format is a teaching of how to present. Both lifted directly from the postscript's framing.
What the postscript missed: it framed the lesson as one we would have to teach the models. Sessions two through six showed it is more accurate to say we have to teach the harness. The model takes the training. The training is the rules in the harness. The harness is what I write.
A year ago I would have said the next quarter's improvement was going to come from a better model. After these five sessions, I would say the next quarter's improvement is going to come from a better-written set of rules in the harness, with whatever model is current at the time.
What This Essay Is Not, And What Came Before It
This essay is not a guide. It is a field report. I have not tested whether the four-mode rule and the checkpoint format work for anyone other than me. They might. They might not. The mechanism that produced them is the part worth borrowing: notice the friction, write the rule that addresses it, watch whether it holds across multiple sessions.
That mechanism is what Write First, Build Second (in the Shifting Bottlenecks essay) is also pointing at, from a different angle. Both essays are the same observation: the work is in the writing, and the writing is what the next session inherits.
There is also an essay before either of those that I want to credit directly. In March I wrote Copy. Paste. about the ritual that defined AI-augmented work in 2025 and the first quarter of 2026. The closing of that essay was a wish. I hope this essay ages poorly. I can't wait to not be able to imagine it. The native-container coding workflow that made this stretch of sessions possible is the workflow that delivered on that wish, seven weeks later. I almost did not notice it had happened.
The continue-tap rhythm I have been writing about across this PR is the next instance of the same disease Copy. Paste. named. Smaller. Quieter. Easier to miss. The micro-rituals are still the smell. They have just gotten small enough that the operator has to look harder to see them. That is the work the next stretch of sessions is for.
Companion essays: Copy. Paste. is the March 2026 essay that named the parent ritual. Fourteen Hours with Opus 4.7 is the day-one field report. Shifting Bottlenecks, Climbing Ladders is the framework that emerged from this stretch.