Bring authorized records together.
Plans, inspections, safety records, observations, scans, cameras, and sensor events remain linked to their sources.
Riftline Spatial · Active research and development
Riftline Spatial combines plans, safety records, inspections, observations, cameras, scans, and sensor events into a continuously updated site model that preserves source provenance, confidence, conflicts, and change history.
Research direction
Static plans age. Observations can be incomplete. Automated detections can be wrong. Riftline Spatial studies how to keep those differences visible and useful.
Plans, inspections, safety records, observations, scans, cameras, and sensor events remain linked to their sources.
Human-guided spatial anchoring establishes scale, orientation, location, and known uncertainty.
Documented and observed conditions are compared without silently overwriting conflicting evidence.
Reviewers inspect sources, confidence, and change history before approving an updated site fact or restriction.
Versioned, machine-readable restrictions can support operators and authorized third-party integrations.
Example applications
Connect current site facts to the plan, record, observation, and reviewer behind them.
Prepare source-linked site context without claiming incident-time certainty.
Locate exits, extinguishers, shutoffs, and other authorized facility assets.
Compare inspection records with later observations and retain unresolved conflict.
Flag potential route obstructions or moved hazards for human review.
Preserve source and confidence for operationally important site locations.
Support local, authorized evaluation in complex or poorly connected environments.
Expose approved restrictions through a read-only boundary without controlling motors.
Current boundaries
Reference integration
An approved Riftline Spatial restriction can constrain movement in the Obsidian reference platform. Unverified observations may restrict movement but may not grant new movement permission.
Emergency-stop behavior, command-authority levels, safe-state behavior, and deterministic movement decisions remain within Obsidian's safety supervisor. Riftline Spatial never directly controls motors, and Obsidian must remain safe when Riftline Spatial is unavailable.
Read about the Obsidian reference boundaryDesign partnership