Home/Demo

Velociti control center walkthrough

Govern the bot inside your local environment before it touches the workflow.

This demo follows a Velociti-powered pilot inside a customer-controlled environment: chat request, Sentinel approval, bounded bot launch, local model route, Rancher runtime proof, Forgejo/GitOps lineage, and audit closeout. The insurance-document workflow appears as one controlled use case with no hosted model API path for sensitive data.

Request pilot review Open simulation
Velociti Pilot EnvironmentSentinel gated
SentinelScope, lease, tools, approvals, denials
Local modelsGemma, Kimi, Qwen, Llama, and other local routes
Runtime proofRancher state + Forgejo/GitOps lineage + audit package

Live simulation

Click through the Velociti control flow.

The screen below shows how a chat request becomes a governed workflow with Sentinel policy, bounded bot execution, local model routing, runtime evidence, delivery lineage, and closeout approval.

Velociti Control CenterChat request received
Velociti Bots view showing governed bot status, local model metadata, Rancher cleanup, and GitOps lineage.
Bots viewBot status, Sentinel approval, local model metadata, Rancher cleanup, and Forgejo/GitOps lineage.
Velociti Sentinel view showing deployment gates, runtime probes, bot authority, and chat-connected workflow requests.
Sentinel viewDeployment gates, approval state, runtime probes, bot authority, and chat-connected requests.
Velociti pilot inputsScoped discovery
1.

Operators

Key owners establish bot authority, target systems, risk points, and approval paths.

  • IT ownerruntime, storage, backup
  • Workflow leadprocess goals and handoffs
  • Reviewerapproval rules
  • Security leadaccess and network boundaries
  • Admin ownerrecords and reporting
2.

Evidence

Approved samples define what a bot can read, summarize, and attach to the closeout record.

  • Runbooksapproved procedure context
  • Logsservice and bot evidence
  • Documentsworkflow samples
  • Screenshotsruntime state
  • Ticketsrequest history
3.

Infrastructure

The pilot maps where bots run, where models execute, and where delivery records live.

VelocitiRancherForgejoGitOpsLocal modelsEvidence vault
5 owners 4 gates 6 systems 1 evidence record
Build processClickable control cards
Implementation timeline6-week pilot path
Phase / workflowW1W2W3W4W5W6
Sentinel scopeauthority map
Local runtimeVelociti workspace
Bot workflowpilot bot
Model routelocal endpoint
Rancher + GitOpsruntime proof
Closeoutevidence record

From walkthrough to pilot

Bring Velociti control to one real workflow.

WonderWave can scope Sentinel authority, local model routing, bot boundaries, runtime visibility, evidence records, and the first document-processing workflow your team wants to pilot.

Request pilot review Review security model