I closed 340 tasks in Arcanada's second month. And I spent almost all of that time at the computer — eighteen to twenty hours a day, often through the night.
I'm not writing this as a complaint. The motivation hasn't gone anywhere: I still get up and reach for the system with the same drive I had in April. But the second month was the first time I seriously ran into two things I used to only read about in other people — procrastination, and the edge of burnout. And I think I found a way to live with both without easing off the pace.
This is the closing article of the cycle. The most personal one. No digital fetishes, no productivity-guru pose. Only what happens to a person who built an autonomous ecosystem — and is still chained to the console, by his own choice.
Let me say it plainly upfront: the kind of autonomy where you can stand up and walk away, I don't have yet. It's the goal I'm moving toward, and moving hard. But the honest report for the month is that I'm still at the desk. I've just learned not to burn out there.
Procrastination: why I run from the big into the small
In programming there's the idea of "procrastination by setup." Instead of writing the feature, you tune the editor. Instead of closing the epic, you rename a variable that has annoyed you for six months. A small task gives quick dopamine. A big one gives anxiety that it won't fit in the context window.
In the second month I caught a clear pattern in myself: if an L4 task — a week-long epic — sat in the backlog, I would start cleaning archives, rewriting READMEs, fixing CLAUDE.md formatting. Fifteen minutes, and I had "done something." In reality I had run away.
I'm not proud of it, but I don't beat myself up either. It's just mechanics: the brain picks easy dopamine. My job as the operator isn't to scold myself but to reshape the process so the big stuff doesn't scare me and the small stuff doesn't disguise the escape.
The numbers confirm the work got harder: among labeled tasks, the share of complex ones — those with a mandatory PRD or multi-phase epics — rose from 29% to 33%. But more energy went into them not because they're harder in themselves, but because I took longer to start. Procrastination isn't about time. It's about the courage to step over the threshold.
Anti-burnout: I switch, I don't stop
The main discovery of the month wasn't technical. I figured out how not to burn out without lowering the load.
I have hundreds of projects in my head. The ecosystem registry holds 26 of them right now, and more than twenty are live: with tasks, servers, deadlines of their own. I used to think this was a problem — spreading myself thin, never finishing. In the second month it turned out to be exactly what saves me.
The mechanic is simple. When I catch myself procrastinating, or feel worn down on one track, I don't force it. I switch to another project. Tired — I take what brings joy: something light, with a result visible within an hour. Full of energy — I take what needs doing, even if it has dragged on and been an eyesore for ages. The fatigue from one thing gets cancelled by interest in another, and the boring-but-important piece gets done with a fresh head.
This isn't discipline in the usual sense. It's routing myself — the same thing my orchestrator does with tasks between agents, only inside my own head. And it's what keeps me going eighteen hours a day without that grey "well, again" that crept in mid-month.
There was an evening when I stared at the task list and couldn't make myself open a single one. Not because it was hard. Because everything had blurred into one: prompt, code, review, archive, commit, prompt again. The old me would have pressed harder and sunk deeper. This time I just closed the current project and opened another — one I'd been wanting to touch for a while. Twenty minutes later the drive was back.
Over the second month I closed 340 tasks — almost the same as the first (341). The pace was the same; it cost more. And it was switching that carried me, more than anything else. Sport and family are there too, and they help: the gym three times a week to reset the head, not for the body; dinners with my wife without a single word about Claude limits. But honestly, the main lever is moving between projects. The rest holds the background; this is what pulls.
Autonomy: a goal, not a fact
Here I have to confess to what isn't there.
An early draft of this report had a pretty scene: as if I'd left town for the weekend with just a phone, and the system closed dozens of tasks without me. It sounds like the perfect ending to the "release the reins" arc. But it would be a lie, and I promised to write without dressing things up.
The truth is this: I'm still at the console. Every day, for many hours. The orchestrator carries a task from initialization to archive, but behind every deadlock, every failure, every "the agent did the wrong thing," it's still me standing there. Running Arcanada from a phone, dictating a task by voice and going for a walk — that's what I'm moving toward, and seriously. The plan is next month. But today it's a dream, not a screenshot from life.
In the first article of the cycle I wrote about the rollback — about returning to manual control after trying to let go. It felt like defeat then. Now I see it as a stage: that rollback was needed to build a system that will one day hold the reins without me. "One day" is the key word. Not "already."
What I kept for myself and what I gave to the agents
I didn't build a perfect system. The orchestrator still stumbles on patches with locks. The implementer agent sometimes writes code that has to be rewritten. Coworker drops a session when a provider goes down.
But I drew a boundary.
I kept for myself the things that need a human: writing articles, reflection, architectural decisions like "which service to launch next," talking to people, sport, family.
I gave the agents what I used to do with my fingers: code implementation, data validation, routine cleanup, writing tests, deployment, monitoring.
The numbers here aren't for boasting but for scale: over the second month my datarim agent handled 1,345 calls and generated 5.1 million output tokens. For $14. I would have spent a year writing that much text by hand. Each of those 1,345 times is a piece of work I didn't have to do myself, and time freed up for what I actually want to push forward.
What it's all for: the long game
I'm not calling on anyone to "drop everything and go autonomous." I'm not promising that agents will save humanity. And I'm certainly not playing the productivity guru — I'm up to my neck in work eighteen hours a day myself.
But this month I understood what I'm holding on for, and why I don't burn out even at this pace. It's the scale of the goal.
I set myself plans that, honestly, I may not finish in a lifetime. Hundreds of projects, an ecosystem bigger than one person. And that doesn't frighten me — it holds me up, on one condition: that you understand how such a plan can be handed on, after you. Not "get it all done," but "build it so others continue."
And after that, the simple part. A huge, maybe unreachable plan breaks into a myriad of small pieces. And every day you do one piece. One step. Then another. Not for a checkmark and not for an output metric, but for the quiet pleasure of today coming out a little better than yesterday.
That, it seems, is the real protection against burnout. Not walking away from the desk — I still have a way to go before that. But having something at the desk worth sitting for, and having each day bring one small, honest win.
I don't know what the third month will bring. I know one thing: tomorrow I'll sit back down at the console, open one of the twenty projects — the one my heart leans toward, or the one that has waited longest — and do another piece. And most likely, I'll enjoy it.
This concludes the cycle on Arcanada's first and second months. And the next publication is already tomorrow — about the lessons of the third month. I'm waiting for it eagerly; I can't wait to share what has come of it.