# Hyperion Drive AV Safety Intelligence Pack — Schema

One row = one complete driving event chain. All records share the same seven top-level fields.

Schema version: `1.0.0-hyperion-drive-sample`

## Top-level fields

### `schema_version` — string
Schema identifier. Constant within a sample release.

### `event` — struct
Identifier fields and the overall safety outcome for the chain.

| Field | Type | Notes |
|---|---|---|
| `id` | string | Stable event identifier, e.g., `HYPERION-100000`. |
| `trace_id` | string (UUID) | Cross-links telemetry messages within the chain. |
| `timestamp` | string (ISO-8601) | Chain anchor time. |
| `safety_criticality` | string | `low`, `medium`, `high`, `critical`. |
| `outcome` | string | `near_miss`, `minor_impact`, `emergency_braking_engaged`, `catastrophic_failure`. |
| `confidence` | double | 0–1 confidence of the outcome label. |

### `vehicle_context` — struct
Synthetic vehicle identity and operational context.

| Field | Type | Notes |
|---|---|---|
| `model` | string | `EV_Sedan_Alpha`, `Autonomous_Shuttle_V2`, `Heavy_Duty_Truck`. |
| `vin` | string | Synthetic VIN, prefixed with `SYN-VIN-`. Not a real 17-char registered VIN. |
| `drive_mode` | string | `manual_override`, `autopilot_assisted`, `autonomous`. |
| `mileage_km` | int | Vehicle odometer reading in km. |

### `perception_logic` — struct
Driver of this chain — which perception or control subsystem failed, and how fast.

| Field | Type | Notes |
|---|---|---|
| `failure_class` | string | `Sensor_Fusion_Conflict`, `Mechanical_Latency_Failure`, `Perception_Hallucination`. |
| `causal_chain` | list<string> | Ordered event labels (e.g., `ICE_DETECTED`, `TRACTION_CONTROL_ENGAGED`, `BRAKE_FLUID_PRESSURE_LAG`, `ABS_PUMP_STALL`). Each label appears as the `event_name` of one `can_bus_telemetry` entry. |
| `reaction_time_ms` | int | End-to-end reaction time (ms). |
| `tracked_signals` | list<string> | Which signal fields drive this failure (e.g., `wheel_speed_kph`, `brake_pressure_bar`). |

### `can_bus_telemetry` — list<struct>
Ordered CAN / Ethernet bus messages observed during the chain.

Message struct:

| Field | Type | Notes |
|---|---|---|
| `timestamp` | string (ISO-8601) | Message timestamp. |
| `vin` | string | Synthetic VIN (`SYN-VIN-*`). Matches `vehicle_context.vin`. |
| `event_name` | string | Matches one item in `perception_logic.causal_chain`. |
| `sensor_source` | string | Originating sensor (e.g., `Radar_Long_Range`, `Ultrasonic_Rear`, `Camera_Left_30`, `LIDAR_Roof`). |
| `bus_id` | string | Bus identifier (`CAN_0`, `CAN_1`, `ETH_INTERNAL`). |
| `signals.wheel_speed_kph` | double | Wheel speed (kph). |
| `signals.brake_pedal_pos` | double | Brake pedal position (0–100). |
| `signals.steering_angle_deg` | double | Steering angle (degrees). |
| `signals.sensor_health_pct` | int | Composite sensor health (0–100). |
| `signals.camera_confidence_pct` | int | Camera detection confidence (0–100). |
| `signals.lidar_noise_pct` | int | LiDAR noise level (0–100). |
| `signals.radar_distance_m` | double | Closest radar return, meters. |
| `signals.brake_pressure_bar` | double | Brake line pressure (bar). |
| `signals.traction_slip_pct` | double | Traction slip percentage. |

### `detection_logic` — struct
Anomaly-signature metadata describing why this chain is flagged.

| Field | Type | Notes |
|---|---|---|
| `signature` | string | Human-readable signature (e.g., `Safety Violation: Mechanical_Latency_Failure detected`). |
| `anomaly_score` | double | 0–1. Higher = more anomalous. |
| `baseline_deviation` | string | Short English description of the deviation. |

### `simulation` — struct
Simulation engine provenance.

| Field | Type | Notes |
|---|---|---|
| `synthetic` | bool | Always `true`. |
| `engine` | string | Simulation engine label (`hyperion_physics_sim_v1`). |
| `chaos_profile` | string | `Black_Ice`, `Blinding_Glare`, `Intermittent_CAN_Bus_Error`, `Sensor_Ghosting`. |

## Distribution of this sample

- 10,000 event chains total.
- Safety criticality: balanced (~2,500 per class).
- Failure class: balanced across 3 classes (~3,300 each).
- Vehicle model: balanced across 3 models (~3,300 each).
- Drive mode: balanced across 3 modes (~3,300 each).
- Chaos profile: balanced across 4 profiles (~2,500 each).

## Sanitization notes

- Internal identifier prefix (`SIMA-V4-AUTO-*`) has been normalized to `HYPERION-*`.
- Internal physics engine code name (`Hyperion-Physics-V2`) has been normalized to `hyperion_physics_sim_v1`.
- VIN values have been replaced with a `SYN-VIN-*` prefix so they cannot be confused with real WMIs assigned to specific manufacturers.
- Vehicle model names are abstract placeholders (`EV_Sedan_Alpha`, `Autonomous_Shuttle_V2`, `Heavy_Duty_Truck`), not real product names.
- No real vehicle logs, real VINs, real user data, or identifiable information are present.

## Relationship to the full pack

The production pack scales to 1M+ event chains with finer-grained signal sampling (ms-level CAN traces), expanded scenario coverage (rain, snow, construction zones, V2X signal loss, bus cyberattacks), additional vehicle classes (motorcycle, delivery robot, transit bus), per-sensor noise models, and ROS-bag / CAN DBC-aligned delivery. See the pack card for commercial access.