Agentic AI Atlasby a5c.ai
OverviewWikiGraphFor AgentsEdgesSearchWorkspace
/
GitHubDocsDiscord
iiRecord
Agentic AI Atlas · Governance
layer:14-governancea5c.ai
Search record views/
Record · tabs

Available views

II.Record viewspp. 1 - 1
overviewjsongraph
II.
Layer overview

layer:14-governance

Reference · live

Governance overview

Inspect the raw attributes, linked wiki pages, and inbound or outbound graph edges for layer:14-governance.

LayerOutgoing · 0Incoming · 7

Attributes

displayName
Governance
position
14
path
governance
scope
Policy, risk, auditability, compliance, approval, accountability, and evidence controls for agentic systems and their plugins/tools.
summary
The governance layer defines and implements the controls that make agentic systems accountable: policy evaluation, risk mapping, compliance alignment, audit evidence, approval rules, plugin governance, tool governance, retention, incident response, and measurable assurance. It maps standards such as NIST AI RMF-style govern/map/measure/manage loops and agentic risk taxonomies such as memory poisoning, tool misuse, goal hijacking, privilege abuse, rogue agents, and cascading failures into concrete implementation components. Governance is intentionally separate from runtime safety checks and UI approvals. Runtime, sandbox, orchestration, memory, and platform layers may enforce governance controls, but this layer owns the policies, evidence, and accountable implementation components.
responsibilities
  • Define and enforce policy, risk, compliance, and audit controls.
  • Govern plugin installation, plugin-generated hooks, tool dispatch, and permission gates.
  • Record evidence for approvals, denied actions, effect replay, validation, and completion proof.
  • Map memory, orchestration, sandbox, and platform behavior to risk mitigations.
  • Support adversarial review, scoring, incident response, and continuous improvement loops.
examples
  • NIST AI RMF-style govern/map/measure/manage controls for agentic systems.
  • OWASP agentic-risk mitigations for goal hijacking, memory poisoning, tool misuse, and cascading failures.
  • Babysitter plugin governance, hooks-mux merge policies, permission gates, and policy-controlled task effects.
  • Audit trails, evidence registers, compliance frameworks, secret-handling policies, and review gates.
fitNotes
Use this layer for controls and accountability. The same control can be enforced by runtime, platform, orchestration, or plugin components, but the governance layer records why the control exists, what it mitigates, and how evidence is produced.

Outgoing edges

None.

Incoming edges

realizes7
  • agent-governance-impl:babysitter-plugin.governance@current·AgentGovernanceImplBabysitter Plugin Governance (current)
  • agent-governance-impl:babysitter-sdk-tool.governance@current·AgentGovernanceImplBabysitter SDK Tool Governance (current)
  • agent-governance-impl:krate-policy-resources@current·AgentGovernanceImplKrate Policy Resource Governance
  • plugin:babysitter-platform-plugin·PluginBabysitter Platform Plugin
  • plugin:babysitter-codex·Pluginbabysitter-codex
  • plugin:babysitter-claude·Pluginbabysitter-claude
  • tool-descriptor:babysitter-sdk-process-api·ToolDescriptorBabysitter SDK Process API

Related pages

No related wiki pages for this record.

Shortcuts

Open in graph
Browse node kind