OSS + ELC EU 2026

As part of the ongoing effort to achieve IEC 61508 certification, Zephyr's requirements capture process is underway. Yet there is still no clear picture of how these requirements trace to the tests that verify them or the code that implements them. Safety evidence is largely documented evidence, so the primary concern is generating auditable documents: requirement and test specifications, test reports, and traceability matrices.
The challenge is collecting this evidence in a community-compatible way — low-friction processes and tooling that developers and maintainers will accept.

This talk proposes a pipeline built on Zephyr's existing documentation tools (Doxygen/Sphinx) to extract the needed information from annotated source and tests, then trace it back against requirements into an end-to-end chain.
Two demos are shown: a minimal working example against Zephyr itself, and a self-contained pipeline for a Zephyr module the authors maintain. Required process adaptations and guidelines are explained. The work is an open proposal for discussion; once agreed, it gives the community a scalable foundation to advance safety efforts, with concrete tasks contributors can pick up.