Open a fictional incident
Classify a fiber uplink outage, generate a report, and persist a linked service ticket.
Not run yet
JUDGE VIEW / LIVE ACCEPTANCE
Prove the workflow, step by step.
Everything below calls this application's real backend. The incident and closure are fictional. No customer devices are changed.
Verify stored evidence
Ask the server to validate the report digest, event chain, and saved ticket history.
Waiting for step 1
Record the demo lifecycle
Acknowledge and close a synthetic ticket. This is not a claim of real hardware repair.
Waiting for verification
Begin with step 1. No pre-recorded traces or fabricated execution states.
VERIFIABLE AUTONOMY
Agents that do the work.
Evidence that proves it.
From a real business incident to a documented, traceable outcome. Policy-driven workflows, isolated code execution, and tamper-evident logs.
WORKFLOW ENGINE
Checking…
Server-side orchestration
EXECUTION SANDBOX
Checking
Disposable, no-network containers
INFERENCE ENGINE
Checking
Qwen local / rules fallback
VERIFIED RUNS
0
Persistent evidence ledger
01 / ACTUAL WORK
Execute a workflow
AVAILABLE NOW
Incident → Action Plan
Turn a customer's infrastructure issue into a classified priority, an actionable service plan, and a SHA-256 evidence trail.
Public-demo submissions are visible to other visitors. Use fictional examples only.
DOCKER REQUIRED
Issue → Verified Repair
Reproduce a bug, generate a candidate patch, rerun assertions inside an ephemeral container, and record the outcome.
Untrusted code is never executed in the web app process.
02 / SECOND TECHNICAL FRONT
Containment Lab. A proof you can challenge.
Run one of three fixed safety probes in a disposable Docker container. The backend records its real outcome and independently checks container removal. No worker attached? The test is marked BLOCKED, not silently simulated.
This is a technical safety demonstration, not a guarantee against container escape. Blast Radius Zero still requires Vultr Serverless Inference and execution on Vultr.
Checking isolated worker…
No containment test run yet.
LIVE RESULT
Execution
EVIDENCE ARTIFACT
—
LAST EVIDENCE HASH
—INTEGRITYVerification pending
03 / AUDITABILITY
Execution ledger
WORKFLOWSTATUSEVIDENCE
No executions yet. Run a workflow to create a trace.
04 / CASE LIFECYCLE
Service ticket board
No service tickets yet. Run incident triage to open one.
05 / THE CONTROL PLANE
Build for proof, not promises.
01 · PLAN
Classify business impact and define a bounded task.
02 · EXECUTE
Send risky code into short-lived isolated containers.
03 · VERIFY
Test results and capture actual execution status.
04 · ATTEST
Append a SHA-256-linked evidence trail.