Deterministic boundary
Synthetic fixtures, evidence references, uncertainty states, validation, catalogue matching, and stable receipts.
Crash evidence in.
Inspectable scenario out.
A crash-to-validation boundary that keeps provenance, uncertainty, deterministic checks, catalogue coverage, and the final decision in one reviewable receipt.
Honest prototype boundaryNo real crash database, generative extractor, automotive accuracy, ASAM compatibility, or safety certification is claimed.
The decision contract
One boundary between model output and engineering use.
- 01
Bind evidence
Every populated attribute points back to a stable source identifier and field path.
- 02
Preserve uncertainty
Missing speed remains unknown. The boundary never invents a convenient range.
- 03
Validate independently
Deterministic range, schema, privacy, and consistency gates control promotion.
- 04
Explain coverage
Catalogue candidates expose each matched and unmatched constraint, not only a score.
- 05
Seal the decision
A canonical SHA-256 receipt makes later changes to evidence or output detectable.
Live boundary test
Change one evidence state. Inspect the whole decision.
Awaiting local run
No decision exists yet.
Select a synthetic evidence state and build the receipt. The browser performs the calculation locally and sends no data.
This interaction demonstrates the deterministic acceptance boundary only. It does not extract from real reports, call a model, assign crash fault, or certify a scenario for safety use.
Five-month Advance path
The missing work stays visible.
Licensed source adapters
Two open European accident sources, a versioned scenario schema, data cards, and a labelled baseline.
Constrained extraction
Disclosed LLM/VLM extraction, calibration, kinematic gates, expert review, and simulation-oriented export.