Brake-state recovery must remain compatible while the restart path is still disputed.
Legacy ECU compatibility protects the vehicle program, while a late middleware commitment protects the release window.
Who you’d be doing this for
“I watched the value come back green, then it was still the one from before the restart.”
Meron Barasa · Vehicle Software Engineer
Integrates the OEM brake-state SWC with the generated AUTOSAR RTE and Vehicle OS runtime.
What is at stake
Brake-state recovery returns a stale value in some restart cycles, and the integration gate closes in five days. You must weigh a compatible interface contract against evidence that is expensive to reproduce on target hardware.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- integration date vs target proof
- legacy compatibility vs recovery behavior
- HIL capacity vs broader reproduction
- middleware change vs operational containment
Why Applied Intuition
Vehicle OS integration must bridge centralized compute with customer-delivered SWCs and legacy ECU behavior.
Written with these in mind
Not your kind of problem? 65 more at Applied Intuition, or browse every organization.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.