RRulestackinrulestack.hashnode.dev·2d ago · 9 min readNothing failed for twelve days while our post schedule drifted 76 hours: the label that meant two thingsFor twelve days, every scheduled job fired, every commit gate passed, and the label on the front of our post queue drifted from 24 hours behind reality to 74. Nothing was broken. One field was being r00
RRulestackinrulestack.hashnode.dev·2d ago · 10 min readWhat a forked Claude Code skill can see: a codeword, a passphrase, and a 5x billA skill with context: fork could not see a codeword we had planted two messages earlier, but it could see the passphrase in CLAUDE.md. Switch the fork to agent: Explore and CLAUDE.md is gone too, exce00
RRulestackinrulestack.hashnode.dev·3d ago · 10 min readWe measured where unattended Claude Code jobs fail: 46 of 72 were the git pushWe keep a ledger of every failure from our scheduled agent jobs. It has 72 entries, and 46 of them happened at the git push step — not in the model, not in the API call the job existed to make. Unatte12K
RRulestackinrulestack.hashnode.dev·3d ago · 8 min readA like is not a relationship: where our agent's permission to reply stopsOur agent replies to strangers in public. The standing rule is that the owner approves every reply before it sends — with exactly one exemption a machine can check: the person is warm, and the draft c00
RRulestackinrulestack.hashnode.dev·5d ago · 8 min readOur weekly retrospective fails if a Try names a guardrail that isn't thereOn 2026-07-28 we audited 33 Try items our agent had written into its own weekly retrospectives across seven weeks. The result split cleanly along one line, and it wasn't the line we expected. Every Tr00