---
title: "#governance articles | Hashnode"
description: "Capture Enterprise Architecture Governance Process. Read the latest #governance articles and tutorials on Hashnode."
url: "https://hashnode.com/tag/governance"
---

Tag

# #governance

365 posts · 12 followers

[Agentic Trainers](https://hashnode.com/@agentictrainers) · [13h ago](https://hashnode.com/posts/who-guards-the-ai-guardrails-five-independence-tests-for-any-ai-agent-oversight-tool/6af517e500ec84dbbcd3f87c)

### [Who Guards the AI Guardrails? Five Independence Tests for Any AI Agent Oversight Tool](https://agentictrainers.hashnode.dev/who-guards-the-ai-guardrails-five-independence-tests-for-any-ai-agent-oversight-tool?utm_source=hashnode&utm_medium=feed)

Vendors now sell the agents and the tools that police them. Here's how to check whether the checker is independent.

30 min read · [agentictrainers.hashnode.dev](https://agentictrainers.hashnode.dev/who-guards-the-ai-guardrails-five-independence-tests-for-any-ai-agent-oversight-tool?utm_source=hashnode&utm_medium=feed)

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

[Karthik Gokul](https://hashnode.com/@Mrmhspec9641) · [6d ago](https://hashnode.com/posts/who-decides-what-an-ai-agent-is-allowed-to-do/6aedb1e6cf6d8af7603b4728)

### [Who Decides What an AI Agent Is Allowed to Do?](https://nuroenai.hashnode.dev/who-decides-what-an-ai-agent-is-allowed-to-do?utm_source=hashnode&utm_medium=feed)

Design explicit AI agent authorization with scoped approvals, trusted identity, execution checks, and practical failure-path tests.

4 min read · [nuroenai.hashnode.dev](https://nuroenai.hashnode.dev/who-decides-what-an-ai-agent-is-allowed-to-do?utm_source=hashnode&utm_medium=feed)

[Ronan Oliveira](https://hashnode.com/@oliveiraronan) · [6d ago](https://hashnode.com/posts/from-policy-pdf-to-runtime-enforcing-ai-governance-on-every-agent-call/6aed08eb774b1cc68719a87b)

### [From policy PDF to runtime: enforcing AI governance on every agent call](https://zihinai.hashnode.dev/from-policy-pdf-to-runtime-enforcing-ai-governance-on-every-agent-call?utm_source=hashnode&utm_medium=feed)

How contextual security policies (CSP) with scope inheritance turn AI governance into rules enforced at runtime: RBAC, schedule, data, behavior, with evidence.

3 min read · [zihinai.hashnode.dev](https://zihinai.hashnode.dev/from-policy-pdf-to-runtime-enforcing-ai-governance-on-every-agent-call?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)

[Kazem Mortazavi](https://hashnode.com/@kazem-mortazavi) · [Oct 31](https://hashnode.com/posts/shadow-ai-managing-unapproved-ai-tools-without-driving-them-underground/6ae56372d8529e94efaa720d)

### [Shadow AI: Managing Unapproved AI Tools Without Driving Them Underground](https://securityland.hashnode.dev/shadow-ai-managing-unapproved-ai-tools-without-driving-them-underground?utm_source=hashnode&utm_medium=feed)

Employees no longer wait for IT approval to draft a report, analyze a spreadsheet, or write a few lines of code. They open a public chatbot and get the job done. That convenience has created a risk th

3 min read · [securityland.hashnode.dev](https://securityland.hashnode.dev/shadow-ai-managing-unapproved-ai-tools-without-driving-them-underground?utm_source=hashnode&utm_medium=feed)

[George Ezejiofor](https://hashnode.com/@georgeezejiofor) · [Oct 29](https://hashnode.com/posts/grc-open-source-falco-wazuh-probo-kubernetes/6ae386252f55b0638f0e5915)

### [GRC Open-Source Tools: Falco, Wazuh & Probo (CrowdStrike/Vanta Alternative, Zero SaaS Bills)](https://georgeezejiofor.com/grc-open-source-falco-wazuh-probo-kubernetes?utm_source=hashnode&utm_medium=feed)

GRC Open-Source Tools: Falco, Wazuh & Probo (CrowdStrike/Vanta Alternative, Zero SaaS Bills)

24 min read · [georgeezejiofor.com](https://georgeezejiofor.com/grc-open-source-falco-wazuh-probo-kubernetes?utm_source=hashnode&utm_medium=feed)

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