From Governance Norms to Enforceable Controls: A Layered Translation Method for Runtime Guardrails in Agentic AI

arXiv cs.AI / 4/8/2026

💬 OpinionSignals & Early TrendsIdeas & Deep AnalysisModels & Research

Key Points

  • The paper argues that agentic AI creates distinct governance risks that arise during multi-step execution, requiring runtime guardrails rather than relying only on development-time or deployment-time safeguards.
  • It proposes a “layered translation method” that maps governance standards (e.g., ISO/IEC 42001 and NIST AI RMF) into four control layers: governance objectives, design-time constraints, runtime mediation, and assurance feedback.
  • The method clarifies the relationships between governance objectives, technical controls, runtime guardrails, and the assurance evidence needed for audits and accountability.
  • It introduces a control tuple and a runtime-enforceability rubric to decide which controls are suitable for enforcement during execution (i.e., when they are observable, determinate, and sufficiently time-sensitive).
  • The approach is demonstrated via a procurement-agent case study, showing how standards can inform where controls should live across architecture, runtime policy, escalation, and audit.

Abstract

Agentic AI systems plan, use tools, maintain state, and produce multi-step trajectories with external effects. Those properties create a governance problem that differs materially from single-turn generative AI: important risks emerge dur- ing execution, not only at model development or deployment time. Governance standards such as ISO/IEC 42001, ISO/IEC 23894, ISO/IEC 42005, ISO/IEC 5338, ISO/IEC 38507, and the NIST AI Risk Management Framework are therefore highly relevant to agentic AI, but they do not by themselves yield implementable runtime guardrails. This paper proposes a layered translation method that connects standards-derived governance objectives to four control layers: governance objectives, design- time constraints, runtime mediation, and assurance feedback. It distinguishes governance objectives, technical controls, runtime guardrails, and assurance evidence; introduces a control tuple and runtime-enforceability rubric for layer assignment; and demonstrates the method in a procurement-agent case study. The central claim is modest: standards should guide control placement across architecture, runtime policy, human escalation, and audit, while runtime guardrails are reserved for controls that are observable, determinate, and time-sensitive enough to justify execution-time intervention.