Flat object lists drop what they have not seen before. This demo abstracts each detection up a semantic taxonomy to the most specific level it can safely justify, and cross-checks it with an independent segmentation path.

A flat object list is a closed world. Anything outside its fixed set of classes becomes a blank, and a blank on the road is a safety problem: the object is still there, the system just has no word for it. This demo shows a perception design that does not drop what it has not seen before.
Instead of forcing a single label, every detection is abstracted up a semantic taxonomy to the most specific level the system can safely justify. A clear pedestrian stays a pedestrian; an unfamiliar object still lands at, say, "dynamic obstacle" rather than nothing. The novel object is not lost, it is placed as precisely as the evidence allows.
A second, independent segmentation path then cross-checks that verdict. Two paths that can disagree are worth far more than one confident classifier, because the disagreement is exactly where the risk lives.
Pick a scene, toggle the segmentation overlay, and click any detection to watch its descent down the taxonomy and read the cross-check verdict. A flat-list view sits next to the hierarchical one, so the difference is visible rather than argued.
The demo is the reference implementation of F. Schaller, "Hierarchical Taxonomic Abstraction for the Safe Handling of Novel Objects in Autonomous Driving Perception" (Zenodo, 2026, doi:10.5281/zenodo.21593472), building on "The Role of Semantic Models in Constraining Pattern Recognition" (Intelligent Environments 2025, doi:10.3233/AISE250023). Detections are computed offline with YOLOv8, CLIP, and CLIPSeg; the page itself is fully static.
The full source is open on GitHub: github.com/freshNfunky/IE2025-Research-Paper.
This is the working demonstration of the argument in Why autonomous perception needs more than flat object lists.

Map your organisation's AI readiness against a model-based maturity matrix. Mark what you have, set where you want to go, and get a dependency-ordered roadmap plus a personalised report.

A humanoid robot on a shared floor needs different controls than an agent drafting copy. Derive the fitting oversight regime from three properties you can actually check, then turn that verdict into a compliance checklist you can export.

Seven questions along the perception-to-release chain reveal where the evidence trail from your perception stack's failure modes to the safety goal is missing, without requiring ground truth.