Scene context makes machine work easier to review.
Xolver uses scene context to help teams understand parts, fixtures, zones, surfaces, and changing work-area assumptions.
Where scene context comes from
Live capture
Environment cameras
Scene information can help teams understand part positions, fixture locations, and zone boundaries during review.
Declared metadata
Reference geometry
Reference geometry and workcell notes can help keep assumptions explicit during early review.
Historical records
Replayed commissioning
Replayed scene records let teams inspect how a proposal was produced, what assumptions were active, and why something needed review.
What the system does with a live scene
When a cell publishes fresh environment state, Xolver uses that context across preview, planning, and constraint surfaces — keeping proposals grounded in where things actually are, not where they were programmed to be.
- Locating known parts and surfaces
- Checking workspace and reachability bounds
- Previewing proposed behavior before physical work changes
- Reasoning about fixture and conveyor context
- Aligning proposals to current cell state
Public safety boundary
Scene context helps Xolver preview and constrain behavior. It does not replace safety validation, operator approval, or hardware-specific signoff.
If scene information is missing, stale, or insufficient, the system blocks, refuses, or requests review — it does not improvise unsafe motion.
FAQ
Does scene context replace safety validation?
No. Scene context grounds previews and proposals, but it does not replace the customer safety process, site requirements, or operator approval.
What happens if live scene information is stale?
The situation should be brought into review when information is stale or insufficient.
Can Xolver discuss a cell without live scene context?
Yes. Early conversations can start from structured notes and reference geometry, as long as assumptions stay explicit.
Why is replayed scene context useful?
Replayed records help teams inspect how a proposal was produced, what assumptions were active, and why a path required attention.