After a crash or an out-of-service order: what happened, and what cannot be concluded yet
A model drafts the analysis because reading a dozen records fast is where it helps. Code decides what it is allowed to claim: every statement must cite a numbered source, and a root cause needs a corroborated fact about this incident. The rest is listed as abstained.
Rear-end collision, I-40 EB
Driver B-2207 · Borderline fileTractor-trailer rear-ended a passenger vehicle in slowed traffic on I-40 eastbound. Minor injury reported, vehicle towed. Driver was cited at the scene. Post-accident drug/alcohol test was administered; result is pending. ELD pull is available.
- knownDOT-recordable crash: injury + tow-away, driver cited at scene.
- knownDriver has a following-too-close citation 5 months ago and a speeding event 3 months ago.
- knownELD shows driver was in hour 9 of an 11-hour driving window - within HOS limits.
- pendingPost-accident controlled-substances/alcohol test result.
- pendingPolice report narrative / dash-cam footage.
“Get the analysis” serves the stored run when there is one. “Re-run live” calls the model again, inside a daily budget; if the budget is spent you get the stored run or the rule-based analysis, labelled.
- Every timeline entry, root cause and policy trigger cites a numbered source that exists.
- A root cause cites at least one corroborated fact about this incident; history and policy alone cannot carry one.
- Below two corroborated facts, no root cause is asserted - the file is held open (policy POL-13).
- Anything removed is listed under Abstained, with the reason.
This incident has enough corroborated evidence for cited root causes.