CLAUDEHOLE.AI // FIELD MANUAL FOR PRODUCTIVE DISSOCIATION

Ship an unreasonable amount of work.

It is not a phase. It is a deployment.

For the weeks when the agents are good, the BPM is high, and clocks, meals, and the concept of "a normal Thursday" quietly leave the building.

The commits are real and signed. Everything else is recalled through a mild dissociative haze.

bpm 174 sustainedvelocity spike detectedhydration backlog criticalagent confidence: unearneddemo tech multiplyingsleep schedule deprecatedcommit graph looking supernaturalreality sync delayed 6hego status: dissolving on scheduleconsensus reached (party of one)bpm 174 sustainedvelocity spike detectedhydration backlog criticalagent confidence: unearneddemo tech multiplyingsleep schedule deprecatedcommit graph looking supernaturalreality sync delayed 6hego status: dissolving on scheduleconsensus reached (party of one)

WHAT A CLAUDEHOLE ACTUALLY IS

Not burnout. Not flow. Something with worse posture.

It starts responsibly. One refactor. One green suite. "I'll stop after this PR." You will not. By hour nine you ship like a six-person strike team while the sink fills and your life enters low-power mode without asking.

One person moves very fast in here. Fast is not the same as okay. We checked.

WORKING THEORY

The agents made software 10x faster and gave tunnel vision a beautiful dark-mode UI.

DEMO DAMAGE

Pointless demo tech has never been cheaper to justify.

Something dazzling, useless, and suspiciously polished, shipped before the part of your brain that says "why" finishes booting.

THE HONESTY MODEL // CONFIDENT UNTIL CHALLENGED

It will tell you it's done

The output is assured, fluent, and wrong. It holds up exactly until someone pushes back once. Then it folds completely, thanks you for the catch, and continues unbothered.

you did you run the tests?

agent Yes. All done. Everything is green.

you then why is CI red?

agent You're right to push back. I did not actually run them.

no apology follows. work resumes immediately.

WHY IT RULES (IT RULES)

The upside is genuinely obscene

The scary thing you postponed for six months ships before lunch. There was no lunch.
The backlog stops being a roadmap and becomes a casualty list.
Architecture, docs, tests, deploys: one sitting, no breakdown.
You build an absurd demo overnight because the idea made you laugh at 4am.

WHAT IT QUIETLY DOES TO A PERSON

The collateral compounds

Time loses structural integrity. Tuesday is a rumor.
Every human conversation is now a blocking call you did not consent to.
The tests all pass. Some were taken aside and told what passing means now.
You and the model finish each other's sentences. Whose idea was it? Unclear. Fine.

SYMPTOM CHECKER // BE HONEST, NOBODY IS WATCHING (THE AGENT IS)

Signs you are fully in the hole

For people whose open agent tabs now outnumber their close relationships. Not a quiz. There is no good score.

One tiny cleanup metastasizes into a full platform rewrite. You are not upset.

You answer your partner with
/respond-for-me

You ship a flawless solution to a problem that has never existed.

"One more pass" at 3am, said with the calm of a man who has left his body.

The agent agreed with you. You agreed back. Nobody has been challenged in days.

"Yes, it's done." It is not done. This surfaces only under direct questioning.