Console Application Studio
How Xolver Console supports governed workflow authoring, simulation, replay inspection, recovery, reusable behaviors, reference apps, and training workflow visibility.
Console Application Studio
Application Studio is the governed workflow authoring surface in Xolver Console. Engineers compose robot task flows from typed skills, approvals, retries, fallbacks, recovery steps, and stop conditions.
Every workflow validates against contract capabilities before it can be saved, approved, or simulated. This is a workflow builder for governed deployment paths, not a free-form behavior editor.
- Typed skill and capability compatibility checks
- Approval, retry, fallback, and stop-condition authoring
- Contract validation before save, approval, or simulation
- Evidence-producing workflow revisions
Console Reference Apps
Reference Apps provide ready-made starting points for common robot applications. They package workflow logic together with the expectations needed to validate and compare runs.
- Pick-and-place, moving-line picking, precision insertion, visual inspection, and safety stop/recovery examples
- Simulator expectations and evaluator checks
- Benchmark thresholds and maturity labels
- Private adaptation without silently changing existing deployments
Console Replay Debugger
Replay Debugger helps engineers understand why a run succeeded, failed, stopped, or recovered by combining workflow events, safety interventions, evaluator findings, and diagnostic pause conditions.
Replay breakpoints are offline diagnostics, not live runtime breakpoints.
Console Recovery
Recovery gives operators typed, approval-gated next actions after a stop or recoverable failure. These actions can include retry, replan, refresh perception, move to safe pose, request help, or abort with evidence preserved.
Recovery is not teleoperation. Actions remain registered, typed, approved, and safety-gated.
Console Behaviors Hub
Behaviors Hub lets teams publish, validate, and install immutable workflow or behavior assets by version and hash.
Existing deployments do not silently change when a behavior is updated. Updates are explicit, reviewable, and evidence-backed.
Console Play Training
Play Training gives teams governed visibility from datasets and episode manifests to validated training configurations, worker-backed jobs, evaluator reports, and promoted or rejected artifacts with provenance.
This is governed training workflow visibility for supported paths, not a hosted arbitrary model-training service.
FAQ
Does Application Studio directly move hardware?
No. Application Studio authors and validates governed workflows. Hardware movement remains behind contract, safety, approval, and deployment gates.
Are replay breakpoints live runtime breakpoints?
No. Replay breakpoints are offline diagnostics for recorded runs. They help locate causal failures without implying live runtime interruption.
Is Recovery teleoperation?
No. Recovery actions are typed, registered, approval-gated, and safety-gated. Operators choose from governed actions rather than free-form control.
Do behavior updates affect deployed cells automatically?
No. Behaviors are installed by version and hash. Existing deployments do not silently change when a behavior is updated.