Kery ZK

Prometheus, for freight

A camera-free driver state concept for the corridor.

Prometheus is in development as a two-sensor in-cab concept. It is intended to estimate changes in driver state before departure and on the road, then share a limited safety signal with an approved vehicle interface and local G-1 nodes. Performance and integration remain subject to validation.

In developmentPre-departure conceptDriver state indexTwo sensorsService interfaceG-1 coordination
IN-CAB / SIDE SECTION DRIVER STATE VECTOR / NO CAMERA UPPER SENSOR, 60 GHz breathing and heart rhythm, 0.3 to 0.9 m LOWER SENSOR pedal area, feet and legs RESPIRATION14 / min, baseline HEART RATE VARIABILITYstable HEAD POSE / MICRO-SLUMPalert fatigue threshold Encrypted, non-identifying numbers only. No face, no eyes, no PII stored or streamed. Short departure baseline, concept timing. PROMETHEUS IN-CAB VEHICLE AUTONOMY STACK G-1 HIGHWAY NODE driver state vectorapproved vehicle interfacecandidate safety input Concept response: warn the driver and pass a limited signal to an approved interface
In the cab, and the handoff to the highway nodeSample values

Intended workflow

Three jobs, in order.

01 / Before departure

A short baseline check

The concept uses radar to estimate breathing rhythm, posture, and movement without a camera. Those readings would be compared with an individual baseline and would not constitute a medical diagnosis.

02 / On the road

A driver state index, not a face

Prometheus is intended to reduce radar returns to a limited driver state index. Any fleet view would show the operational alert, not an image of the driver's face.

03 / With the highway

A limited signal for the road

A validated implementation could share a driver state alert with an approved vehicle interface and a G-1 highway node. Any change to vehicle behavior would depend on the vehicle, OEM permissions, and tested integration.

Proposed decision model

Two sensors, one driver, three possible outputs.

The current concept places one sensor toward the torso and another near the pedal area. Candidate measures are compared with that driver's own baseline. A small drift can be recorded as data. A larger deviation can raise an alarm. Any intervention requires a validated policy and an approved vehicle interface.

Baseline

Vitalsbreathing, heart rhythm
Posturehow the driver sits
Reflexhands and feet on the controls

Criteria

Percent changeagainst the driver's own baseline
Envelope deviationleaving the defined space
Percent changeslower or missing responses

Monitoring

Breathing and blood pressureupper sensor
Defined spaceupper and lower sensors
Limbslower sensor

Output

Datalogged to the fatigue index
Alarmdriver and fleet are told
Interventionthe vehicle and the highway node adjust

The vehicle connection

Designed for fleets already on the road.

Prometheus is being designed around diagnostic and service interfaces already present in many fleets. Available signals and any vehicle interaction depend on make, model, year, OEM permissions, and validated integration.

The truckDiagnostic / Service Port

Candidate signals include speed, braking, and other data where the vehicle interface exposes them.

In developmentPrometheus

Designed to read approved signals, estimate driver state, and bridge to a supported V2X system.

The radioV2X, 5.9 GHz

Used only where regional rules, road authority systems, and vehicle support allow it.

On the corridorG-1 highway node

Designed to receive the limited signal and adjust its local warning logic.

Talk to us

Tell us what you are working on.

A city crossing, a fleet, a fireground, a port. If people and machines share the space, we would like to hear about it. The founding team reads every message.

Goes straight to the founding team.