feat(core): add EnforcementMode enum to governance contracts (#1727)

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: viswa-uipath

packages/uipath-core/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "uipath-core"
-version = "0.5.18"
+version = "0.5.19"
 description = "UiPath Core abstractions"
 readme = { file = "README.md", content-type = "text/markdown" }
 requires-python = ">=3.11"

packages/uipath-core/src/uipath/core/governance/__init__.py

@@ -18,12 +18,13 @@
     GovernanceViolation,
     Severity,
 )
-from .models import Action, AuditRecord, LifecycleHook, RuleEvaluation
+from .models import Action, AuditRecord, EnforcementMode, LifecycleHook, RuleEvaluation
 
 __all__ = [
     # Output models (cross adapter boundary)
     "Action",
     "AuditRecord",
+    "EnforcementMode",
     "LifecycleHook",
     "RuleEvaluation",
     # Config

packages/uipath-core/src/uipath/core/governance/config.py

@@ -1,8 +1,11 @@
 """Governance configuration.
 
 Process-level feature-flag gate that decides whether the Python
-governance checker runs at all. Enforcement mode is per-policy and
-lives in the runtime package alongside the ``/runtime/policy`` client.
+governance checker runs at all. The
+:class:`uipath.core.governance.EnforcementMode` value type is defined
+in :mod:`uipath.core.governance.models`; the per-policy runtime state
+that selects a mode (backend-supplied via the ``/runtime/policy``
+client) lives in the ``uipath-runtime`` package.
 """
 
 from __future__ import annotations

packages/uipath-core/src/uipath/core/governance/models.py

@@ -1,10 +1,17 @@
-"""Shared governance output types.
-
-These dataclasses cross the adapter boundary — every evaluator
-implementation (native, AGT, composite, …) produces them, and every
-adapter consumes them. They are kept free of policy-input concepts
-(``Rule``/``Check``/``Condition``) so the adapter packages don't
-inherit the native policy model.
+"""Shared governance contracts.
+
+Two groups of types live here, both kept free of policy-input concepts
+(``Rule``/``Check``/``Condition``) so adapter packages don't inherit
+the native policy model:
+
+- **Output types** (:class:`Action`, :class:`LifecycleHook`,
+  :class:`RuleEvaluation`, :class:`AuditRecord`) — cross the adapter
+  boundary at evaluation time: every evaluator implementation (native,
+  AGT, composite, …) produces them, and every adapter consumes them.
+- **Configuration value types** (:class:`EnforcementMode`) — describe
+  governance configuration shared by core, runtime, and consumers. The
+  runtime state that selects an enforcement mode lives in
+  ``uipath-runtime``; only the value type lives here.
 """
 
 from __future__ import annotations
@@ -35,6 +42,14 @@ class LifecycleHook(str, Enum):
     AFTER_TOOL = "after_tool"
 
 
+class EnforcementMode(str, Enum):
+    """Governance enforcement modes."""
+
+    AUDIT = "audit"  # Evaluate and log; never block.
+    ENFORCE = "enforce"  # Block on DENY rules.
+    DISABLED = "disabled"  # Skip evaluation entirely.
+
+
 @dataclass
 class RuleEvaluation:
     """Result of evaluating a single rule."""