---
title: "#runtime-security articles | Hashnode"
description: "Explore 29 articles tagged #runtime-security on Hashnode. Tutorials, guides, and how-tos from the community."
url: "https://hashnode.com/tag/runtime-security"
---

Tag

# #runtime-security

29 posts · 0 followers

[Rain S](https://hashnode.com/@rain6fish) · [2d ago](https://hashnode.com/posts/ai-execution-governance-part-12-closing-an-unknown-is-not-a-verdict/6afa538341511dbe2b1fed33)

### [AI Execution Governance, Part 12: Closing an Unknown Is Not a Verdict](https://keelbase.hashnode.dev/ai-execution-governance-part-12-closing-an-unknown-is-not-a-verdict?utm_source=hashnode&utm_medium=feed)

Context, since this assumes none: I build a runtime that lets AI agents take real actions in business systems — create a record, send a request to another service — with permissions, approvals and an

7 min read · [keelbase.hashnode.dev](https://keelbase.hashnode.dev/ai-execution-governance-part-12-closing-an-unknown-is-not-a-verdict?utm_source=hashnode&utm_medium=feed)

[Rain S](https://hashnode.com/@rain6fish) · [Nov 11](https://hashnode.com/posts/ai-execution-governance-part-11-revocation-hands-over-three-records-not-one-stopped/6af3c0be7ca091ae9367f00c)

### [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)

[Rain S](https://hashnode.com/@rain6fish) · [Nov 9](https://hashnode.com/posts/ai-audit-evidence-part-6-a-record-nobody-read-is-only-stored/6af1179b3117daa416be0800)

### [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)

[Rain S](https://hashnode.com/@rain6fish) · [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 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)

[Rain S](https://hashnode.com/@rain6fish) · [Nov 2](https://hashnode.com/posts/ai-execution-governance-part-9-revocation-complete-is-a-conclusion-not-a-status-field/6ae7de10b73d979abcdeb37c)

### [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)

[Rain S](https://hashnode.com/@rain6fish) · [Oct 28](https://hashnode.com/posts/ai-execution-governance-part-8-actions-the-tool-registry-does-not-know-about/6ae14830ceb952eaf280d839)

### [AI Execution Governance, Part 8: Actions the Tool Registry Does Not Know About](https://keelbase.hashnode.dev/ai-execution-governance-part-8-actions-the-tool-registry-does-not-know-about?utm_source=hashnode&utm_medium=feed)

One application, one events table, two rows. One row comes from your AI assistant: it calls create\_event, a registered tool marked R3 that waits for your confirmation. The other comes from POST /api/v

16 min read · [keelbase.hashnode.dev](https://keelbase.hashnode.dev/ai-execution-governance-part-8-actions-the-tool-registry-does-not-know-about?utm_source=hashnode&utm_medium=feed)

[Rain S](https://hashnode.com/@rain6fish) · [Oct 23](https://hashnode.com/posts/ai-audit-evidence-part-3-an-auditor-is-not-an-admin/6adb10b58c60127c28180f08)

### [AI Audit Evidence, Part 3: An Auditor Is Not an Admin](https://keelbase.hashnode.dev/ai-audit-evidence-part-3-an-auditor-is-not-an-admin?utm_source=hashnode&utm_medium=feed)

An auditor has to review what an AI did. The cheapest way to let them do that is to hand them an admin account. But then the person they are supposed to review becomes themselves. This piece is about

9 min read · [keelbase.hashnode.dev](https://keelbase.hashnode.dev/ai-audit-evidence-part-3-an-auditor-is-not-an-admin?utm_source=hashnode&utm_medium=feed)

[Rain S](https://hashnode.com/@rain6fish) · [Oct 23](https://hashnode.com/posts/ai-audit-evidence-part-2-silence-reads-as-completeness/6adb107ea392e4cf6606b354)

### [AI Audit Evidence, Part 2: Silence Reads as Completeness](https://keelbase.hashnode.dev/ai-audit-evidence-part-2-silence-reads-as-completeness?utm_source=hashnode&utm_medium=feed)

An auditor receives an evidence package. The hash chain verifies. What will they read that as? Most people read it as two things: the rows were not altered, and they are all here. The chain proves onl

9 min read · [keelbase.hashnode.dev](https://keelbase.hashnode.dev/ai-audit-evidence-part-2-silence-reads-as-completeness?utm_source=hashnode&utm_medium=feed)

[Rain S](https://hashnode.com/@rain6fish) · [Oct 23](https://hashnode.com/posts/ai-execution-governance-part-7-one-timeout-cannot-answer-two-questions/6adb103fe750ac4cc498a027)

### [AI Execution Governance, Part 7: One Timeout Cannot Answer Two Questions](https://keelbase.hashnode.dev/ai-execution-governance-part-7-one-timeout-cannot-answer-two-questions?utm_source=hashnode&utm_medium=feed)

An AI asks to write something, and a person has to approve it. There are two kinds of "expired" in that sentence, and they are not the same thing: should the conversation keep waiting for the approval

7 min read · [keelbase.hashnode.dev](https://keelbase.hashnode.dev/ai-execution-governance-part-7-one-timeout-cannot-answer-two-questions?utm_source=hashnode&utm_medium=feed)

[Rain S](https://hashnode.com/@rain6fish) · [Oct 23](https://hashnode.com/posts/ai-execution-governance-part-6-the-unique-constraint-guards-the-ledger-not-the-action/6adb0feea392e4cf6606ad50)

### [AI Execution Governance, Part 6: The Unique Constraint Guards the Ledger, Not the Action](https://keelbase.hashnode.dev/ai-execution-governance-part-6-the-unique-constraint-guards-the-ledger-not-the-action?utm_source=hashnode&utm_medium=feed)

An assistant calls a tool that writes. That call can arrive twice: the model retries it, the same confirmation gets decided twice, or the process restarts mid-flight. A second arrival must not write a

7 min read · [keelbase.hashnode.dev](https://keelbase.hashnode.dev/ai-execution-governance-part-6-the-unique-constraint-guards-the-ledger-not-the-action?utm_source=hashnode&utm_medium=feed)
