The evidence layer for the safety case you're already publishing.
If your team writes the document the regulator, the insurer, and the public read, FieldSpace generates the per-claim evidence that backs every behavioral acceptance criterion. The same input produces the same output for your auditors, every time.
Who FieldSpace is built for
Operators who carry end-state safety liability and have to defend the safety case to regulators, the public, and the entities underwriting their fleet.
- ✓Robotaxi operatorsDriverless ride-hailing operations with formal safety cases under active publication and revision.
- ✓Autonomous delivery operatorsSidewalk, road, and last-mile delivery fleets operating without an onboard human, with NHTSA exemption petitions and published safety reports.
- ✓Autonomous trucking operatorsDriverless freight operators publishing safety cases for hub-to-hub routes and operating under state-level autonomous trucking regulations.
- ✓Learned-policy operatorsEnd-to-end learned stacks where the policy is not deterministic, but the safety envelope around it has to be.
- ×Tier-1 ADAS suppliersLiability is offloaded to the OEM by contract, so a third-party evidence layer is not a budget-line. Available on request as a secondary engagement.
- ×L2 driver-monitoring fleetsIf a human is the rated driver, the safety case is structured differently. FieldSpace can still produce useful evidence, but is not the primary product fit.
- ×Pure simulation platformsFieldSpace is not a sim vendor. We sit alongside whatever sim the operator already uses, producing evidence the operator's safety team needs.
How FieldSpace fits inside the safety case
Section 2.3 of the Favaro 2023 paper defines five behavioral acceptance criteria dimensions and explicitly invites third-party evaluative methodologies to map into them. FieldSpace populates all five.
| AC DIMENSION | FIELDSPACE EVIDENCE | REPRODUCIBILITY ARTIFACT |
|---|---|---|
| Severity Potential | TTC-bound, predicted delta-V from potential field | nuPlan TTC 0.9219 |
| Conflict Role | Initiator / Responder identification from active repulsive field | Per-frame JSON trace |
| Regulatory Compliance | Speed-limit + drivable-area compliance | nuPlan 1.000 / 1.000 |
| Conflict Avoidance | Route progress without conflict initiation | nuPlan 0.9660 |
| Collision Avoidance | No-at-fault collision + early-warning lead time | nuPlan 0.9766 / 13-15s lead |
| Functionality Status | CPU-only engine survives degraded compute | nfs-modulus crate |
| Event-Level Reasoning | Per-frame trace across 60,019 + 4,550 frames | Per-segment JSON |
| Aggregate-Level Reasoning | Rates across 64 + 50 + 10 scenario / clip sets | Manifest-pinned |
Source: Favaro et al. 2023 "Building a Credible Case for Safety" (arXiv:2306.01917). Numbers anchored to public benchmark artifacts under reproducibility/.
What an operator receives
Three deliverable types. All reproducible to the bit by the operator's safety team, their auditors, and the underwriters pricing their fleet.
Per-claim evidence pack
For each behavioral claim in the operator's published safety case, a reproducibility-pinned evidence trace mapped to the relevant AC dimension. Cite-ready.
ODD coverage report
Quantitative coverage map across the operator's ODD, with gap analysis tied to the behavioral capability dimensions. Update when the ODD extends.
Counterfactual replay log
On an incident or disengagement, the deterministic should-have-happened trace plus the affected claim and the safety case revision delta.
A focused validation engagement, priced in writing
Three phases, fixed scope, fixed fee. Start with a paid evidence pack before any broader commitment.
Safety case alignment
Map FieldSpace evidence to the operator's published safety case structure. Pick the AC dimensions and claims to cover first.
Evidence generation
Run FieldSpace against the operator-supplied ODD spec and scenarios. Produce the per-claim evidence pack with reproducibility-pinned artifacts.
Auditor walkthrough
Joint review with the operator's safety team, audit partner, or insurer. Confirm the evidence replays identically on their side.
Send the safety case. We'll map the evidence.
30-minute validation call first. We bring the AC-framework mapping and the benchmark trail. You bring the safety case structure and the questions your auditors are asking.