POLICY + GUARDRAILS + APPROVAL

Keep model intelligence inside deterministic control boundaries.

Identity, authorization, policy, native guardrails, approval, budget, tool dispatch and official audit are separate control layers. High-impact actions move from proposal to evidence through explicit gates that the model cannot bypass.

The model proposes work; platform controls determine whether work can become an external effect.

8high-impact action control stages
T0-T5operation risk classification
1official evidence authority

CURRENT AUTHORITY

Every execution uses current identity, delegation and resource scope.

Authorization is re-evaluated for dispatch, handoff, retry and resume. Agent identity, the human or workload principal and delegation remain distinct records.

RBAC plus contextual ABAC
Revocation epoch
Delegation narrowing
Resource ACL
Environment scope
Default deny

POLICY + GUARDRAILS

Policy decisions and content/runtime guardrails remain explicit services.

Provider adapters can change while platform-native authority remains stable. External content never becomes trusted platform instruction simply because it came from an internal source or another agent.

Pre-action guardrails
Post-result controls
Prompt and tool-input boundaries
Data classification
Provider-independent policy contracts

HUMAN APPROVAL

Approval is payload-bound, scoped and time-limited.

Where required, approval references the exact operation, target, arguments, purpose and validity window. A generic UI confirmation cannot authorize a different payload later.

Operation-bound approval
Payload digest
Separation of duties
Expiry
Re-validation before dispatch

OFFICIAL EVIDENCE

Operational traces support diagnosis; audit evidence supports accountability.

Critical task, delegation, policy decision, approval and external effect records correlate to the same execution while sensitive content stays minimized.

Append-only audit
Correlation across controls
Evidence references
Secret redaction
No hidden reasoning capture