Evidence And Readiness
Xolver treats physical autonomy as a deployment-specific decision. A system is not ready just because a model produced a plausible action.
What Evidence Means
Readiness depends on the resolved cell, runtime contract, safety boundaries, adapter behavior, operator approvals, and evidence trail for the deployment path being considered.
Evidence is the record of how a proposed behavior was evaluated.
- Runtime contract references
- Selected OEM compatibility pack
- Safety-zone configuration
- Preview or replay metadata
- Adapter readiness results
- Soak or stability records
- Operator approval records
- Blocked checks and refusal reasons
- Deployment proposal summaries
Why Evidence Matters
Evidence is useful because it turns autonomy from a black-box claim into a reviewable operational record.
Robotic systems fail when intent, control, and safety are treated as one opaque loop.
- What the system believed
- What it proposed
- What was allowed
- What was blocked
- Who approved live operation
- Why the system refused or escalated
Preview Ready
The cell draft is coherent enough to generate non-executable previews.
Preview readiness may include valid metadata, selected skills, workspace references, and safety-zone definitions. It does not imply permission to move hardware.
Bench Ready
The cell has enough evidence for controlled bench evaluation.
Bench readiness may include adapter readiness records, simulator-backed baselines, soak/stability evidence, and commissioning-stage checks. It still requires controlled supervision.
Supervised Live Ready
The deployment has operator approval, live-actuation gates, hardware-specific checks, and safety I/O validation.
This stage is intentionally conservative. Xolver requires evidence and explicit approval before physical behavior can move beyond preview.
Production Ready
Production readiness is path-specific and depends on real cell validation, operational policy, safety integration, and deployment evidence.
Xolver does not treat simulator-only results as production certification.
This supports safer pilots, clearer operator review, and more disciplined expansion from shadow evaluation to active control.
FAQ
Is simulator evidence enough for production readiness?
No. Simulator-backed evidence can support preview or bench readiness, but production readiness depends on real cell validation, safety integration, operational policy, and deployment-specific evidence.
Why does Xolver separate preview ready from live ready?
A coherent preview proves that the system can inspect and explain a proposed behavior. Live readiness requires a stronger set of gates, including hardware checks, safety I/O validation, operator approval, and live-actuation policy.
What happens when evidence is incomplete?
The deployment path should remain blocked, limited to preview, or escalated for review. Missing evidence is treated as a readiness condition, not as a detail to improvise around.
Who uses the evidence trail?
Operators, integrators, safety reviewers, and engineering teams use evidence to reconstruct what the system believed, proposed, allowed, blocked, and escalated.