Technical due diligence / ISO 26262 / ISO 21448 SOTIF

Autonomy and
software safety,
evaluated structurally.

Independent risk evaluation for perception, localization, and sensor fusion stacks that have to survive both the real world and a certification audit.

Fig. 01  /  Track continuity under occlusion Replay
20 m40 m60 m OCCLUDER TRK 07TRK 12 TRK 31 TRK 44 • NEW EGO
The stack reports two objects. There was one. TRK 31 → TRK 44  /  identity lost
Track record
25 years in safety-critical and computational systems
Research
Lead Research Scientist, Validas AG, 2017 to 2025
Consortium
BMWK SafeWahr, with AVL, Intel, TU Clausthal
Record
Granted EP patent, 4 peer-reviewed publications
Services

Where autonomy programs actually break

Not in the feature list. In the assumptions nobody wrote down, the failure boundaries nobody defined, and the evidence nobody can produce when the assessor asks for it.

Diagnostics

Check your own stack first

Self-assessments you can run yourself. No sales call attached, no email wall. If the result looks uncomfortable, that is the point.

Writing

DeepTech perspectives on perception, reasoning, and resilience

Computer Vision/Jul 10, 2026

Your Perception Stack Is a Snapshot Machine

Most perception stacks reason one frame at a time. The network detects, tracking is bolted on afterwards, and the system never really carries the world forward. A snapshot machine cannot validate cleanly, because the thing that would make its output trustworthy is the thing it discards between frames: continuity.

Cognitive Science/Jun 28, 2026

Gödel Is Not a Death Sentence for Reason

Gödel's incompleteness theorem, Hume's induction problem, the halting problem, and AI hallucination are not isolated failures of reason. They point to the same missing term: context.

Autonomy/Jun 25, 2026

Why Autonomous Perception Needs More Than Flat Object Lists

Most ADAS perception stacks classify what they already know. The real world is combinatorial, contextual, and full of unknowns. Semantic fallback systems are needed when flat object lists fail.

About

I evaluate the structural limits of autonomy stacks, before they become operational liabilities.

More than 15 years in safety-critical software and autonomy programs, on top of a longer trajectory through computational graphics, SLAM research, and formal verification. My work covers robustness under real-world constraints, certification feasibility under ISO 26262 and ISO 21448, and the architectural boundaries of modern perception.

Autonomy systems rarely fail because a feature is missing. They fail because a structural constraint was never examined.

Structural depth

Localization, SLAM, sensor fusion, and safety-critical architecture, read at the level where the failure modes actually live.

Engineering rigor

Explicit assumptions, traceable decisions, defined failure boundaries. Everything else is opinion with a slide deck.

Independent oversight

No tool to sell, no platform to defend. The evaluation says what it finds.

Next step

Bring me the part of the stack nobody wants to present.

Thirty minutes, no pitch. Either there is a structural problem worth your time and mine, or there is not, and I will say so.