I HAVEN'T OPENED CLAUDE AT MIDNIGHT SINCE I BUILT THIS FOLDER
I used to wake up and find out what broke overnight
-> now the receipts are already there. dated, graded, waiting on my review
what sits inside the folder that took that shift:
• the contract
> CONTRACT.md - the shift rules, committed
> contract.local.md - my overrides, gitignored
• the harness (.claude/loops/)
> settings.json - spend caps and timeouts. set once
> schedule.yml - 05:00, pr-hunter. cron fires it, not me
> rubrics/ - code.md reviews merges, writing.md checks voice, safety.md says what not to touch
> pr-hunter/ - plan.md runs wake, read, act, verify
> t.co/VUDfqGE1Fp does the work. t.co/3uqBEehPSh is the gate to merge
> tools.allow - what it may call, and nothing else
• the state
> receipts/ - one folder per shift. 17 shifts today
> 5,382 receipts kept. none of them edited
> trace.log - what happened, line by line
> checkpoint.json - resumes exactly where it stopped
> budget.json - $6.10 spent of a $40 day
• the edges
> t.co/agzjvw6VbF - the panic file. never used
> .mcp.json - the tools it's allowed near
> alerts.yml - who gets paged when a loop stops
2 loops. 3 rubrics. 8 months in service. 0 incidents
nothing here is clever. every file exists because a run went sideways once
I wrote the rule down instead of trying to remember it
$6 a day for a shift I used to work at 1am
the model doesn't wake. the folder does
Work
An overnight Claude agent that reviews and merges PRs for $6 a day
Buzzoni runs a cron-fired Claude shift each morning that reads, acts and verifies against committed rubrics, logging every run. Two loops and three rubrics, eight months in service, 5,382 receipts kept and no incidents.
648likes
101reposts
854saves
71Kviews
- Made with
- Claude Code
- Posted







