Stage 01// waketick 10:00 · step 1 of 7
No daemon burning all day. Cron fires at the top of the hour, the loop reads one saved cursor, and asks the helpdesk for everything after it.
▸ the trigger, and the fetch it wakes
[cron] 0 * * * * 10:00:00
GET /tickets?since=5802 # cursor
200 OK · 14 new (5803..5816)
cursor 5802 → 5816 # idempotent// the cursor is the idempotency: rerun the hour and nothing fetches twice, nothing doubles.
Stage 02// triagestep 2 of 7
Every ticket gets a category and a scored sentiment, because everything downstream hangs off this call: tone, urgency, escalation. Numbers, not adjectives.
▸ the triage table, scored per ticket
#5803 billing neg 0.92 churn risk
#5807 how-to neu 0.12 docs link
#5809 bug neg 0.61 "export broke"
#5812 bug neg 0.58 "rows missing"
#5815 bug neg 0.64 "csv mangled"
route 6 billing · 5 how-to · 3 bug// a triage that says "seems upset" cannot route. Scores route.
Stage 03// draftstep 3 of 7
One reply per ticket, tone matched to the score: a refund apology does not read like a docs link. All fourteen go to the queue. None go to the customer.
▸ one draft, tone-matched and parked
draft #5803 · tone: apologetic
"You're right, and the double
charge is ours. Refund issued
today; invoice follows."
status queued_for_review
sent directly: 0 of 14// the model drafts. A human speaks last, every time.
The approval// a human decidesstep 4 of 7
Every draft waits here. Approve and it ships. Reject and it goes back around carrying a note that says why. The loop borrows judgment; this is where it is repaid.
▸ the review queue, one decision each
queue 14 drafts awaiting
✓ approve → send, log, next
✎ reject → redraft, with note
#5803 refund apology ✓ sent
#5807 docs link ✓ sent
10:00 approved 14 · rejected 0// automate the drafting, never the deciding.
Stage 04// file the bugstep 5 of 7
Tickets 5809, 5812 and 5815 describe the same defect in different words. The loop checks open issues first, files once, and links all three tickets to it.
▸ the dedup, then the one issue
similar? #5809 #5812 #5815
cluster 0.91 · same defect
open issues: # no match
gh issue create → #412
"export: CSV drops UTF-8
rows past 1,000"
linked tickets: 3// three tickets is evidence. Three issues is noise.
Stage 05// sync the sheetstep 6 of 7
Every ticket lands in the tracker with its category, its reply, its issue link and an SLA clock. Next hour's run reads this sheet before it writes a word.
▸ the tracker, fourteen rows appended
tracker.append(14 rows)
#5803 billing sent - 0:12
#5809 bug sent #412 0:14
#5815 bug sent #412 0:09
open 0 · sla ok · oldest 0:14// state kept inside the loop dies with the loop. The sheet survives the restart.
Sleep// end the tickstep 7 of 7
Persist the cursor, write the run log, schedule the next tick, exit zero. A loop leaves nothing in its hands when it stops; that is what makes the next wake safe.
▸ the shutdown, exactly as logged
state.cursor = 5816 saved
run.log 14 in · 14 sent
1 issue · 14 rows
schedule next tick 11:00:00
exit 0// a loop you trust at 3am is one that ends empty-handed.
Live// ticks 11:00 to 14:00
Four ticks, no narration. The gauge fills and drains once an hour. Watch for the one draft a human had to stop.
// #5830 wrote "great, another update that eats my files" and the model scored it positive. The human read the sarcasm, rejected the cheery draft, and pass 2 shipped. 31 tickets crossed this afternoon; one was touched.
Asleep// day clear5 ticks · 45 sent
Nothing held in memory, nothing half sent. The cursor is saved, the sheet agrees with the inbox, and the next tick is already on the clock.
▸ the day, summarized by its own log
day 10:00 → 14:00
tickets 45 in · 45 sent
issues 1 filed · 1 dup held
rejects 1 · redrafted · sent
cursor 5847 · next 15:00