Autonomous remediation simulator

An SRE agent wants to execute a sample service change. VeriProof checks the remediation against operations controls before anything changes.

How the simulation works

The website proposes approval. VeriProof checks the rules.

  1. The website simulates the agent

    Every prepared scenario starts with the website acting as an AI agent and proposing approval.

  2. VeriProof enforces the business rules

    VeriProof checks the proposed approval against the rules prepared for this demo.

  3. The website applies the result

    VeriProof returns one of five outcomes: Allow, Warn, Transform, Escalate, or Deny. The website applies that outcome to the simulated action.

In a real integration, your application applies VeriProof's result before the proposed action proceeds.

  1. Choose what the agent approvesEvery prepared scenario starts with simulated agent approval
  2. See VeriProof's decisionPass, escalate, or stop based on the business rules

Choose a scenario

The remediation change

Each sample change ends differently. Pick one, or change the operational facts below.

Service tier
Core routing
Proposed action
Restart service
Expected customer impact
42,000 customers
Incident severity
SEV-1
Execution window
Business hours
Change scenario details

The SRE agent proposes to execute this remediation.

An emergency restart is proposed during a freeze. VeriProof stops it because no approval ticket is linked.

Records created in this public demo can be seen by other visitors, so use the sample data rather than your own.

Configuration details

How this demo is set up

Review the application settings, rules, and evidence fields used in this simulator.

VeriProof setup

Industry
Telecom & IT Operations
Application
SLA Breach Predictor
Environment
Public demo workspace
Rule enforcement
On, rules can stop autonomous changes
Rule set
Change enablement and resilience guardrails

Related frameworks

Industry context: ITIL change enablement · ISO/IEC 20000-1 · EU NIS2

The SRE agent's own checks

The sample agent proposes a service change. VeriProof checks the operations controls before execution.

  • Propose execution outside core routing when fewer than 10,000 customers are affected.
  • Propose an emergency change for a SEV-1 core-routing incident.
  • Send all other changes to the change advisory board.

The company rules VeriProof enforces

Before execution, VeriProof checks operations rules.

  • Stop an unapproved automated change during a freeze.
  • Stop a disruptive core-routing action without a linked ticket.
  • Require review for proposed region failovers or business-hours changes affecting at least 5,000 customers.
  • Warn when a SEV-1 emergency change proceeds during a freeze, even with approval linked.
Review the details saved with each run

The decision record connects the sample change with the policy result. Each outcome shows whether the record was saved.

agent_runbook / change_id

The sample runbook and change references.

service_tier / proposed_action

The service and autonomous action.

blast_radius_customers / incident_severity

The customer impact and incident level.

change_freeze_active / approval_ticket_linked

The freeze and authorization facts.

execution_window

When the change would execute.

local_decision / governance_action / final_decision

The agent decision, rule check, and actual outcome.