Clinics and healthcare admin
Patient intake summaries, scheduling notes, insurance prep, and staff handoffs with PHI warnings and approval.
Explore clinic workflowsWonderWave consulting powered by Velociti
Private AI pilots with governed bots, local models, and proof.
WonderWave helps IT teams and regulated local businesses test one sensitive AI workflow through Velociti’s control layer: Sentinel approvals, bounded bots, local model routing, runtime visibility, and audit evidence.
Sentinel approval
Local model route
Rancher visibility
Forgejo/GitOps lineage
Gemma 4 Closeout HermesSenPnlOverview01 Sentinel Overview
Document Workflow Sentinel
Hermes · sentinel-gemma4-document-worker-bdaa3b
IdleSentinel approvedRancher readyGitOps linkedSecret-ref only
OverviewRuntimeRancherSecurityEvidenceActivity
HealthIdle
Operational reads are allowed; write executors remain gated by Sentinel policy.
Sentinel gates4
Purpose, duration, network, and filesystem controls active.
RuntimeCleaned
Rancher reports no orphaned bot containers.
Model routeLocal
Gemma endpoint selected; hosted API denied.
Sentinel gatesBot scope, duration, filesystem access, and network routes are approved before work begins.
Local model controlPrompts, logs, screenshots, and workflow outputs can route through approved local models.
Runtime proofRancher-backed visibility shows what is running, cleaned up, or drifting from policy.
Evidence closeoutApprovals, denials, bot actions, model routes, and cleanup records stay reviewable.
Powered by Velociti
The platform layer behind WonderWave pilots.
Velociti gives WonderWave a governed operating surface for secure AI work: Sentinel bot authority, local model routes, chat-connected workflows, Rancher runtime visibility, Forgejo/GitOps lineage, and durable evidence.
Workflow-first
Sensitive workflows need visible boundaries and local controls.
With WonderWave, nothing leaves your local systems and no information is shared externally.
Local systems
Velociti Sentinel
Local model
Private output
Internal records
External sharing blocked
Hosted API
WonderWave local control
Data stays inside your environment
Local model route
Encrypted storage
Audit evidence
External sharing path
Outbound data route is closed
No file upload route
No hosted prompt path
No external model sharing
Law firms and legal ops
Matter intake, document triage, deadline extraction, and source citations with privilege-aware review.
Explore legal workflowsAccounting and finance teams
Client request assistants, document prep, bookkeeping notes, and tax-data warnings before output.
Explore finance workflowsLocal service businesses
Customer intake, estimate prep, job handoffs, and internal knowledge Q&A with scoped source access.
Explore service workflowsVelociti walkthrough
See a governed bot in action.
A local Velociti demo showing chat intake, Sentinel approval, bot launch, local model routing, runtime proof, GitOps lineage, and audit closeout.
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
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
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
Phase / workflowW1W2W3W4W5W6
Sentinel scopeauthority map
Local runtimeVelociti workspace
Bot workflowpilot bot
Model routelocal endpoint
Rancher + GitOpsruntime proof
Closeoutevidence record
7visible control stages from chat request to evidence closeout.
4Sentinel gates across purpose, lease, tools, and network route.
Control layer
Govern bots, models, agents, runtime, and evidence with Sentinel under your authority.
Velociti gives each pilot a visible operating boundary under your control: Sentinel reviews every bot against rules you set, then records local model routes, approved tools, runtime proof, and closeout evidence for every workflow.
SentinelApproved scope before execution
Purpose, target, duration, filesystem access, and network routes are recorded before a bot runs.
ModelsLocal route for sensitive work
Model choices are attached to the workflow record so IT can see which endpoint handled the task.
GatesWrite actions require approval
Read-only checks can move quickly while deploy, restart, delete, or export actions stay gated.
EvidenceApprovals, denials, logs, and cleanup retained
The pilot record shows what ran, what stayed blocked, and what evidence exists.
Pilot process
From Sentinel scope to granular audit and log trails.
Each step produces reviewable evidence: authority rules, bot activity, model route records, runtime logs, approvals, denials, and closeout artifacts.
Sentinel Scope
Map purpose, target systems, allowed tools, denied actions, lease duration, and approval owners.
Velociti Pilot
Build one governed workflow with a bounded bot, local model route, and visible runtime state.
Team Rollout
Train staff on chat requests, approvals, evidence review, and handoff rules before expansion.
Governance Support
Improve bot scopes, Sentinel gates, model routing, runtime probes, and evidence reporting over time.
Artifacts your team can review
Granular audits and log trails your team can actually inspect.
This is not a black box. Each artifact gives IT and operations something concrete to inspect, approve, revise, or reject before a wider rollout.
Example workflow run
Matter document worker
- Request capturedUser, purpose, target folder, and 30-minute lease recorded.Logged
- Sentinel gate checkedRead-only access allowed. Write actions remain approval-gated.Allowed
- Bot launched locallyBounded worker starts under Sentinel with filesystem and network scope.Scoped
- Model route verifiedLocal Gemma route selected. Hosted model API path remains blocked.Blocked
- Runtime probe savedRancher state, labels, cleanup status, and drift notes attached.Evidence
- Reviewer decisionApprove, edit, or reject action captured with the final closeout note.Reviewable
No black box
Every action leaves a trail your team can open.
WonderWave pilots expose the authority rule, bot action, model endpoint, runtime state, denial reason, and human decision behind the workflow.
AuthoritySentinel scope, lease, owner
Bot activityStart, stop, tool use, target
Model routeLocal endpoint and blocked paths
RuntimeContainer state and cleanup
DenialsPolicy reason and timestamp
CloseoutReviewer action and notes
Sentinel authority mapPurpose, lease, tools, network, filesystem, approvals.
Bot workflow prototypeA governed workflow running under one approval record.
Runtime probe reportRancher state, labels, cleanup, and drift notes.
Evidence packageLogs, denials, model route, screenshots, closeout notes.
Rollout recommendationExpand, revise, or stop based on operational evidence.
Resources
Prepare the pilot before the first call.
Use the readiness checklist and resource hub to bring the workflow, local environment, approval owners, and evidence questions into the pilot review.
Business typeClinic, law, accounting, finance, service.
Data categoryPatient, legal, tax, financial, customer, operations.
WorkflowOne repeated process with an owner, bot boundary, and review point.
Data sampleSynthetic, redacted, or approved examples.
Request a private AI pilot review
Bring one sensitive workflow. Leave with a safer pilot path.
Share the business type, workflow candidate, software stack, sensitive data category, and whether sample or redacted data is available.
- Do not submit passwords, private keys, PHI, regulated records, or confidential customer files through this public form.
- Use this form to request a review, not to transfer production data.
- WonderWave will use your answers to decide whether a private AI pilot makes sense.
Pilot review form
Share the business context WonderWave needs to evaluate whether a Velociti-powered private AI pilot is a good fit.
If the form does not load, open the pilot review form in a new tab.
Questions before a pilot review
Frequently Asked Questions
Open the questions that matter to your team before deciding whether a private AI pilot is worth reviewing.
Does sensitive workflow data leave our local environment?
The private pilot path is designed so sensitive workflow data, prompts, logs, model outputs, and evidence stay inside the approved local or customer-controlled environment.
What is Sentinel reviewing?
Sentinel reviews bot requests against rules you set: purpose, target system, duration, allowed tools, denied actions, network route, filesystem access, and approval owner.
What do you need from our team?
WonderWave typically needs a workflow owner, current software stack, target systems, sample or redacted examples, approval owner, known risk points, and a description of what the workflow should produce.
What stays human?
Risky actions, final decisions, exports, policy exceptions, low-confidence outputs, and professional judgment remain with named reviewers. The pilot can draft, classify, summarize, search, and prepare evidence for review.
Can this work with our existing systems?
The pilot is scoped around existing tools and approved sources where possible: folders, documents, chat surfaces, repositories, runtime systems, records, and workflow outputs your team already uses.
What artifacts do we receive?
Common artifacts include a Sentinel authority map, workflow prototype, local model route notes, runtime probe report, evidence package, review checklist, audit trail, and rollout recommendation.