Components › Human Control & Oversight › Consent & Scope Gates
HC04 · Control

Consent & Scope Gates

Purpose Intercepts an agent before it takes action in a new system, with new data, or beyond its originally authorized scope — requiring affirmative human consent.
Use when An agent requests access to a system, data type, or user population not covered by the original authorization.
Do not use As a substitute for initial authorization design — scope gates handle expansion, not initial setup.
Failure mode prevented Agents silently expanding their operational scope across systems and data types without explicit user authorization.
Example Dark Academia
Overview
Design rule

Any action outside the agent's original declared scope requires a new consent gate. Blanket pre-authorization is not acceptable.

Theming API

Override these CSS custom properties to apply your own visual treatment without touching the component's behavioral contracts.

Shared semantic tokens

Token Controls
--rad-surface-card Card background
--rad-color-text-primary Scope item text
--rad-color-text-secondary Description body
--rad-color-text-meta Requested-scope sublabel
--rad-color-approve Approve button fill
--rad-color-reject Reject button label and border
--rad-radius-card Card border radius

Component-scoped tokens

Token Controls
--rad-scope-gate-border Card border
--rad-scope-gate-color Header label, icon, + accent
--rad-scope-gate-requested-bg New scope panel background

"*The agent asks permission here. This is not a suggestion. Do not look for workarounds.*"

← Previous Agent State Indicators Next → Agent Attention Triggers

Intellectual Property

RAD is the original work of Jackie Curry. All rights reserved. No portion may be reproduced, adapted, or incorporated into any product or system without express written permission.

Permitted: citation in academic or editorial contexts with full attribution.

Licensing

© 2025 Jackie Curry. All rights reserved. Publication date: 2025.

For licensing inquiries, connect on LinkedIn →