YOUR GROK BOT WILL EITHER CATCH ITS OWN FAILURES OR HAND THEM TO YOU AT 11PM. THE FORK IS THREE FILES, LAYERED IN THIS ORDER. for weeks i thought every failure was a new one. bot missed a deadline. bot sent a message it should have parked. bot repeated a question i had already decided. they were not different failures. they had three shapes. no clear owner. no clear stop. no clear schedule. every screw-up was one of these three. the article names the fix as three files. read them as a stack, each layer closing one shape: 01/ charter. scope of ownership. closes: "who was supposed to catch this?" one page in Bot actions, Description. name, reports to, what he owns, the verbs he must park (send, publish, spend, delete, sign). 02/ house_rules. scope of what is reversible. closes: "why did the bot even try that?" ten one-line rules he signs before touching anything. rule 1 (if i cannot undo it in a minute, i park it) alone closes the biggest class. 03/ routines. scope of when work happens without a prompt. closes: "why am i still the one starting every task?" five saved jobs, three recurring, two triggered. brief at 7, review on friday, handoff at 6, silent-inbox catcher, monthly audit. read the stack from the bottom up. each layer inherits the ones below it. every future specialist Chief drafts starts at layer one and picks up the same three files. when a new failure lands, it belongs to exactly one layer. add the rule there, and it never fires again from any bot on the account. paste layer 01 tonight. add layer 02 tomorrow before the next task. layer 03 can wait until the first parked question comes back the way you would have written it.
