A photo that does not tell the next person why it was taken or whether anything is missing.
WHY THIS WORKS
Capture the vehicle up close. Let Halo build the listing views.
A conventional capture process asks the person holding the phone to frame each final shot and typically needs roughly 12 to 18 feet of clearance to frame the whole side across vehicle types. Halo changes the job. Your staff capture the vehicle in close-range sections with approximately 5 feet of clearance. Halo checks the coverage and builds the final views.
- CLOSE-RANGE
- GUIDED
- VEHICLE-AWARE
- VERIFIED
VSI SEQUENCE
Observe. Understand. Register. Guide. Verify.
Halo identifies the vehicle, understands where the phone is, guides the next capture, checks the coverage, and keeps the result with the VIN.
- 01Observe
- 02Understand
- 03Register
- 04Guide
- 05Verify
- 06Trusted Record
THE VIN-LINKED RECORD
Halo keeps the information a photo file leaves out.
Halo knows which vehicle the photo belongs to, what the job required, whether the capture is complete, and where the finished set needs to go.
The photos stay with the VIN, the capture job, the coverage check, and the delivery status.
- The photo job
- The right vehicle
- The person who captured it
- What has been captured
- What is still missing
- Where the finished set goes
SECURE LINK
Send the photo job to the person already near the vehicle.
A secure link opens the right vehicle and the right job on a supported phone. The person who requested the work does not need to be standing beside the vehicle.
Halo is designed for dealership staff using supported phones. The guidance replaces freehand framing with a step-by-step capture sequence that can be tested with your team during the POC.
REQUEST TO RESPONSE
The person at the vehicle does the capture. The person who asked for it gets the result.
Halo keeps the request, the capture, the finished photo set, and the delivery together so the job does not disappear between people or systems.
01Evidence request
A dealership workflow asks for fresh evidence of the vehicle instead of waiting for a new folder of photos.
FOUNDING POC SCOPE
02secure link
The request becomes a secure capture session with a native-blue Open secure capture action for the person already near the vehicle.
FOUNDING POC SCOPE
03authorized person beside the vehicle
Halo connects the session to an authorized person standing beside the same physical vehicle.
FOUNDING POC SCOPE
04guided live observation
Guided Capture shows the required view, keeps the phone naturally scaled, and preserves the live vehicle context.
FOUNDING POC SCOPE
05Vehicle Spatial Intelligence
VSI reads stable vehicle features and registers the observation against vehicle-relative geometry.
FOUNDING POC SCOPE
06coverage and confidence verification
Coverage resolves as a required observation path, distinct from the landmark field that identified the vehicle structure.
POC MEASURE
07trusted vehicle record
The completed observation returns to a recognizable dealership workflow as part of the vehicle record.
FOUNDING POC SCOPE
08API, workflow, partner, or AI-agent response
Founding POC workflow responses are in scope. Evidence request APIs are NEXT. Partner and AI-agent responses remain FUTURE DIRECTION.
FUTURE DIRECTION








WHAT HALO KNOWS
Where the person is. What part of the vehicle Halo can see. What is still missing.
VSI does not treat every photo as interchangeable. It understands the vehicle, keeps track of the close-range sections already captured, and guides the person to the next one.

DEALERSHIP OPERATIONS
One rooftop shows whether the technology works in the real world.
The founding POC tests the whole photo job at one live rooftop: guided close-range capture, final views, approved background and finish, shared status, and delivery to one agreed destination.
- FOUNDING POC SCOPEGuided Capture
- FOUNDING POC SCOPEStandardized views
- FOUNDING POC SCOPEHalo Flows
- FOUNDING POC SCOPEOperations Board
- FOUNDING POC SCOPEDealer-system routing
PLATFORM DIRECTION
The same guided-observation model can support more than merchandising.
Merchandising is the first job. Over time, the same approach could help with appraisals, reconditioning, service, and other decisions that depend on seeing the vehicle. We call that longer-term direction Trusted Vehicle Observation Infrastructure.
Evidence Graph
Over time, vehicle observations can become relationships between VINs, people, sessions, requests, coverage, changes, and downstream decisions.
Visual Passport
A vehicle could carry a living visual passport that preserves what was observed, when it was observed, and which workflows relied on that record.
Provenance
C2PA could allow selected signed provenance assertions to travel with vehicle media. Provenance does not determine whether a depicted vehicle fact is true; it can make origin and change context inspectable.
Read the C2PA source noteChange and review
When a new observation differs from the trusted record, Halo can surface a change signal and route review before teams publish or act.
Objects that can ask for evidence.
A trusted observation layer becomes more useful when software, partners, and future agents can request evidence and receive structured context instead of unverified image files.
- FOUNDING POC SCOPECapture sessionA secure request brings an authorized person to the vehicle and records the guided observation state.
- FOUNDING POC SCOPEWorkflow statusDealership teams can see which vehicle stage changed and what action should happen next.
- NEXTEvidence request APIPartners and internal systems can request fresh observation instead of relying only on stale image files.
- FUTURE DIRECTIONAI-agent responseAgents could request verified vehicle evidence and receive structured record context instead of guessing from unverified media.
Prove the dealership job first. Earn the right to expand.
Our focus today is dealership merchandising. We will not present the broader platform as available until the product has earned that claim in real work.
- Merchandising proof
- Workflow expansion
- Partner evidence requests
- Vehicle evidence graph
- Embedded visual infrastructure
DEPLOYMENT REVIEW
Show us where the finished photos need to go.
Bring one rooftop, one current photo process, and one destination. We will show you what Halo can handle now and what still needs to be proven.
REVIEW DEPLOYMENT








