The ISO 17356-3 PDF had warned him. On page 58, a single, overlooked sentence: "The behavior of the system when a Counter exceeds its maximum value is implementation-defined."

He ripped the tablet from the mount, scrolling furiously. There—Section 13.2: ErrorHook . A last-ditch function call that could override the OS scheduler in an emergency.

Dr. Aris Thorne was not a religious man, but he kept a single, weathered PDF open on his third monitor at all times. It was ISO 17356-3:2006 – Road vehicles — Open interface for embedded automotive applications — Part 3: OSEK/VDX Operating System (OS) .

The Chimera box hummed. Two LEDs turned from red to steady green.

Silence.

Lena gasped. "It worked! It actually understood your ancient dinosaur language!"

He shouted at his voice assistant: "Execute ErrorHook routine 0x4F!"

Tonight was the test.

Aris smiled. "Section 7.2.3. It's a warning about priority inversion. I've accounted for it."

Aris had defined it as "ignore." That was now a catastrophic error.

With seconds to spare before Lena’s car hit the abandoned hangar, Aris didn't type a single line of new code. He re-used an ancient function from the PDF's example appendix—a piece of sample code written by a German engineer in 1999, meant to demonstrate ShutdownOS .