Sentinel Operations
Operations
checking
runtime
Client Guide
How AEGIS controls agent actions
The agent sends the intended action to AEGIS before touching a real system.
AEGIS checks context, behavior, policy signals and operational risk.
Risky actions wait for approval, denial or a recurring customer rule.
Before execution, the agent confirms the approval is still valid and still matches the action.
Approvals, blocks, rules, confirmations and repeated matches remain visible in the audit trail.
Observer
Monitor first. Build context without blocking workflows.
Guardian
Validate before execution. Require approval for controlled actions.
Decision Rules
Allow or block recurring patterns without exposing internal logic.
False Positives
If AEGIS holds a safe action, approve once or allow similar to reduce repeated reviews.
Latest decision
Waiting
none
learning
none
Risk0
Confidence0
Signal0
Noise0
No action validated yet.
Decision History
Search
Inspector
No selection
Select a decision, agent, timeline item or audit event.
Operational Timeline
Timeline
Audit
Audit Events
Billing & License
Plan Control
Billing not loaded yet.
Customer Onboarding
Account Setup
Complete a paid checkout before onboarding.
Client Connectors
Webhook Config
Internal Settings
Console Maintenance
Development/demo controls. In a customer workspace this stays restricted to owner/admin operations.
Owner Intelligence
Platform Learning
Internal-only view of logins, commercial usage and learning signals. Customers do not see this layer.
Customers & Plans
Learning Signals
Human Gate
Pending Reviews
Runtime Control
Recent Alerts
Behavior Profiles
Agents
Execution Gateway
Gateway Runs
Universal Agent Layer
Integration Kit
Control Maturity
Learning Gate
Learning mode is active by default.
Governance Layer
Policies
Customer Controls