Continuous compliance with Rust in automotive software
summary
Claims that an always–audit-ready, continuous functional safety workflow is practical: a reference implementation and a telemetry POC that streams to AWS produces linked requirements, tests and a traceability matrix as HTML/PDF, gives immediate CI feedback on non‑compliance, and reduces mean‑time‑to‑recovery. Uses Sphinx (with a new Sphinx reads Rust plugin), PlantUML, cargo test & clippy, CircleCI and Cargo to extract artifacts automatically. Ferrous Chain follows the same approach, so the pattern already works in practice.
AI-written summary · about
chapters (14)
- 0:00Continuous compliance intro
- 1:53Automotive needs standards
- 3:58Key automotive standards
- 5:24Current compliance pain points
- 7:08What is continuous compliance
- 9:16Open source compliance tools
- 10:00Rust compliance workflow demo
- 15:21Real-world compliance example
- 16:03Rust simplifies compliance
- 18:36Compliance benefits
- 19:42Q&A: QM and ASIL certification
- 20:46Q&A: Evolving libraries compliance
- 22:51Q&A: Requirements simplification
- 23:55Q&A: Qualification efficiency
related talks
26mFerrocene - qualifying the Rust compiler using a fully open source tool stack
56mRust for Safe and Scalable Automotive: Insights from
27mContinuous Compliance: Agile Practices for Software Compliance
07mLightning Talk: “How Rust Is Steering Automotive Software Toward Safety”
56mRust for Foundation Software
46mPanel: Rust in Safety Critical
31mValidating Rust for industry: Certification meets formal analysis
51mPete LeVasseur, Lead, Safety-Critical Rust Consortium [Rust Project Content