One-page paper: how a Grok bot decides to act or ask first
A single reversibility score routes tasks through four doors (act, draft, ask, stop), caps asks at three per day, and cut the ask rate from 0.61 to 0.09 over four weeks.
This is f**king insane... A one-page paper on how a single Grok Bot earns the right to act without you, and the whole method fits above the fold. The bot never asks how important a task is. It asks one thing, can this be undone by lunch, and that number picks one of four doors: act, draft, ask, stop. A rename scores 0.98 and simply happens. A $2,400 wire scores 0.04 and waits behind ask. Anything under 0.05 never even gets asked about. The part almost nobody builds: three asks a day, no rollover. When they run out the bot does not fall silent, it writes the work up as a draft and leaves it on the desk. And every yes gets appended to the rules file as one line. Six lines on day 1, thirty-one on day 28, twenty-five of them born from a yes. The same question never returns. Ask rate across four weeks on the same budget: 0.61 -> 0.34 -> 0.18 -> 0.09. Sixty tasks, four doors, zero wrong. Paper is below. The routing config is inside it.
This post quotes another post: x.com/rich_odinn/status/2109563714068169203