IF-16 · Operations interface

Geo-roadside intake, resource, dispatch and closure

Carry precise incident context, resource eligibility, provider acknowledgement, ETA, proof, CRM reconciliation and network analysis.

Authority model

Name the source—and name what it cannot prove.

The same message can be observation, projection, plan, receipt or physical evidence. This contract keeps those meanings separate.

Authority

The case system owns workflow; provider systems own availability and acknowledgement; vehicle signals remain context, not diagnosis.

Degraded behavior

Ambiguous location pauses recommendation, no eligible resource escalates, provider decline remains unassigned and incomplete proof blocks closure.

Outcome boundary

Intake is not diagnosis; eligibility is not availability; dispatch is not attendance; closure is not physical repair without configured proof.

Product allocation

A product can appear on both sides when it transforms one authority into another; each transformation retains its own evidence.

versioned→fail-closed

Transport allocation

The program can select one or more transports without changing the source authority or failure contract.

Case APIProvider dispatch eventLocation and ETA serviceCRM reconciliation

OEM program workshop

Allocate owners, transport, schema, releases, policy, content, degradation, replay and target acceptance in one controlled baseline.