AI Agent Governance

SMERC is a runtime permission layer for AI-agent actions

SMERC stands for Structural Momentum Entropy Range Confidence. The short name remains the product brand; the full name explains the signal model behind the governance layer.

SMERC evaluates whether an automated action is recoverable enough to execute before it creates side effects. It is designed for security, platform, DevSecOps, and AI governance teams reviewing agentic workflows.

Home AI deployment governance Runtime AI governance Agent permissions SMERC vs guardrails CISO review GitHub Actions pilot AI-readable summary GitHub repo

Plain-English Definition

What SMERC does

SMERC sits between model outputs, tool calls, workflow automation, and real-world execution. When an AI agent or automated process proposes an action, SMERC evaluates the action and returns a replayable posture: ALLOW, THROTTLE, FREEZE, DENY, or ESCALATE.

Traditional authorization usually asks whether an identity or workflow is allowed. SMERC asks an additional question: if this action goes wrong, can the organization recover, contain, pause, roll back, or explain it?

Search Terms

What SMERC should be compared against

SMERC belongs near AI agent governance, runtime governance, agent authorization, policy-as-code, AI gateways, deployment controls, security approval workflows, and recoverability scoring. It does not claim to replace those systems.

The sharper difference is recoverability-aware permissioning: SMERC evaluates reversibility, containment strength, rollback latency, evidence validity, anomaly pressure, impact scope, and authorization confidence before execution.

Important Boundary

What SMERC is not claiming

SMERC is pilot-grade software. It is not production-certified, not compliance-attested, and not proven to reduce incidents in live customer environments. The current goal is external technical review and bounded shadow-mode pilot evidence.

SMERC does not replace IAM, OPA, AI gateways, SIEM, EDR, approval systems, model safety systems, or human accountability.

Review Path

How a reviewer should inspect SMERC

Inspect GitHub repository Read CISO overview Review GitHub Actions pilot Open structured profile Open SMERC Beacon Open llms.txt