Repository navigation
Integrated standards
LionDriver answers to five standards: ISO 26262 (functional safety), ISO 21448 (SOTIF), ISO/SAE 21434
(cybersecurity), ISO/PAS 8800 (AI safety) and Automotive SPICE (process capability). Many organisations run each
one as its own project, with its own team, documents and report. This page explains, from the start, why LionDriver
runs them as one system instead, and how you can see that in its records. It explains and links. The lifecycle is in
the process model (WP-P-11), the work products in the
register, WP-M-00, the hazard log in the
HARA, WP-C-03 §7 and the case in assurance/case-records/.
Every figure is drawn at each wiki sync by tools/wiki/integrated_animations.py.
The lane and interface counts, the register coverage, the hazard log, the trace lanes and the case status are read
from the records, and every other phrase is checked against its record. When a record changes, the build fails
instead of showing old text.
In silos, the same hazard is found three times under three names, and a problem that belongs to two standards can be found twice or not at all. Integrated does not mean merged: each standard keeps its own questions, methods and assessor. It means one lifecycle, shared items and checked joins.
An interface is a point where one discipline's work depends on another's result: the TARA rates safety impact
against the HARA's hazards, for example. Each interface names the two work products and quotes text from both, so the
model cannot claim a link the documents do not make. These are different from the safety–security interactions in
hatara/, which ask whether a measure for one helps or hurts the other.
Each row of the register names every standard the work product serves. A work product written once is counted wherever it applies; an empty stretch shows where a standard has no work product of its own.
The HARA keeps one row per vehicle-level hazard with the SOTIF hazards and the cyber attacks that lead to it. The figure checks that row against the TARA's own damage scenarios and flags any hazard the TARA reaches but the log does not name. Below it, the trace: a solid lane is in the trace data and checked by CI; a dashed one is linked in its work-product tables only (From hazard to test follows one chain).
The safety envelope on the panda is where the standards meet in the product. Each asks something different of it, but it is built, verified and cited once. A gap in it is therefore a gap in every case at once.
One top claim, one branch per standard, each argued its own way. Evidence can hold up claims in two branches, and recorded doubts (defeaters) point at the claims they weaken, wherever those sit. What is a safety case? shows how a case is read.
- Standards at a glance: how the standards divide the work.
- SOTIF and ISO 26262, Cybersecurity and ISO/SAE 21434, AI safety and ISO/PAS 8800 and ASPICE: is the process capable?: one page per standard.
- Glossary for the work product and ID codes.