--- title: "Rain S (@rain6fish) | Hashnode" description: "Rain S (@rain6fish) writes on Hashnode. Read their latest articles and follow their work." url: "https://hashnode.com/@rain6fish" --- @rain6fish # Rain S @rain6fish · Joined October 2026 ### [After the AI Writes, Part 1: Don't Carry Someone Else's Work Into Your Commit](https://keelbase.hashnode.dev/after-the-ai-writes-part-1-don-t-carry-someone-else-s-work-into-your-commit?utm_source=hashnode&utm_medium=feed) Three AI sessions are working in the same checkout. One of them has just finished; you glance at the diff, it looks right, and you run: git add -A && git commit -m "feat: ..." Ten minutes later you o 5 min read · [keelbase.hashnode.dev](https://keelbase.hashnode.dev/after-the-ai-writes-part-1-don-t-carry-someone-else-s-work-into-your-commit?utm_source=hashnode&utm_medium=feed) [1d ago](https://hashnode.com/posts/after-the-ai-writes-part-1-don-t-carry-someone-else-s-work-into-your-commit/6af42a4467673c2e7eac61f7) ### [AI Execution Governance, Part 11: Revocation Hands Over Three Records, Not One "Stopped"](https://keelbase.hashnode.dev/ai-execution-governance-part-11-revocation-hands-over-three-records-not-one-stopped?utm_source=hashnode&utm_medium=feed) An outbound write is in flight. In another window, an administrator revokes the role of the user who started it. Minutes later someone asks: did that call stop? If the system answers only "stopped", t 6 min read · [keelbase.hashnode.dev](https://keelbase.hashnode.dev/ai-execution-governance-part-11-revocation-hands-over-three-records-not-one-stopped?utm_source=hashnode&utm_medium=feed) [1d ago](https://hashnode.com/posts/ai-execution-governance-part-11-revocation-hands-over-three-records-not-one-stopped/6af3c0be7ca091ae9367f00c) ### [AI Audit Evidence, Part 6: A Record Nobody Read Is Only Stored](https://keelbase.hashnode.dev/ai-audit-evidence-part-6-a-record-nobody-read-is-only-stored?utm_source=hashnode&utm_medium=feed) A record sat in the database for a year before anyone opened it. That is not negligence. There is no place in the system that says who should read it, or how often. One sentence: a record was written 4 min read · [keelbase.hashnode.dev](https://keelbase.hashnode.dev/ai-audit-evidence-part-6-a-record-nobody-read-is-only-stored?utm_source=hashnode&utm_medium=feed) [3d ago](https://hashnode.com/posts/ai-audit-evidence-part-6-a-record-nobody-read-is-only-stored/6af1179b3117daa416be0800) ### [AI Execution Governance, Part 10: Can Revocation Stop a Call That Is Already Running?](https://keelbase.hashnode.dev/ai-execution-governance-part-10-can-revocation-stop-a-call-that-is-already-running?utm_source=hashnode&utm_medium=feed) A tool call has passed the gate and is running. Now the role is revoked. Does it stop, or does it finish? Ours finishes. Revocation governs the next call, not this one. That is not the intent of the d 5 min read · [keelbase.hashnode.dev](https://keelbase.hashnode.dev/ai-execution-governance-part-10-can-revocation-stop-a-call-that-is-already-running?utm_source=hashnode&utm_medium=feed) [2](https://hashnode.com/posts/ai-execution-governance-part-10-can-revocation-stop-a-call-that-is-already-running/6aea824f286b35d94b7ac199) [Nov 4](https://hashnode.com/posts/ai-execution-governance-part-10-can-revocation-stop-a-call-that-is-already-running/6aea824f286b35d94b7ac199) ### [AI Execution Governance, Part 9: Revocation Complete Is a Conclusion, Not a Status Field](https://keelbase.hashnode.dev/ai-execution-governance-part-9-revocation-complete-is-a-conclusion-not-a-status-field?utm_source=hashnode&utm_medium=feed) A side-effect row reads revoke\_status = revoked. On the screen it becomes a green badge that says revoked. Those three words are not a field value. They are a conclusion, and a conclusion is supposed 5 min read · [keelbase.hashnode.dev](https://keelbase.hashnode.dev/ai-execution-governance-part-9-revocation-complete-is-a-conclusion-not-a-status-field?utm_source=hashnode&utm_medium=feed) [2](https://hashnode.com/posts/ai-execution-governance-part-9-revocation-complete-is-a-conclusion-not-a-status-field/6ae7de10b73d979abcdeb37c) [Nov 2](https://hashnode.com/posts/ai-execution-governance-part-9-revocation-complete-is-a-conclusion-not-a-status-field/6ae7de10b73d979abcdeb37c)