Automotive Certifications Research & Strategy

[bottha123]

Research and evaluate automotive industry certifications (MISRA, CISRA, and related standards) to understand how Boost libraries can align with or support automotive/embedded software development requirements.

Context:

• Mentioned by Vinnie after conversation with Khalil Estel (Jan 13, 2026)
• Khalil is working on coroutines for embedded systems
• Automotive/embedded systems represent a major C++ market segment

Objectives:

1. Research MISRA, CISRA, and other automotive certification standards
2. Assess which Boost libraries are used in automotive/embedded contexts
3. Identify opportunities to better serve the automotive market
4. Explore collaboration with Khalil Estel on embedded systems requirements

Research Areas:

• MISRA C++ coding guidelines
• CISRA (need to identify)
• ISO 26262 (functional safety for vehicles)
• AUTOSAR standards
• Embedded systems requirements

[bottha123]

Harry and Mark met with Michael Wong on Friday, January 16 at 11am ET.

Summary for Vinnie (not yet sent)
I dug into the MISRA idea with Michael Wong and Mark. It’s not a ‘certify Boost’ project—it’s a defensive survival move. If we try to make ‘Boost MISRA compliant’ as a whole, it’s basically impossible: Boost is template/macro/pointer-heavy and we’ll drown in deviations and tool false-positives. The only plausible path is MISRA C++ 2023, and even then it’s a small ‘MISRA-safe subset’ lane, not 100% compliance. Also, we shouldn’t assume NVIDIA (or anyone) will adopt Boost just because we do this. Recommendation: don’t commit big resources yet—do a feasibility + vendor/tool reality check first, pick a handful of candidate libs, and see what the actual findings look like before we decide whether this is worth it.
The three caution points to emphasize
Scope trap: “Subset only; whole-Boost certification is a non-starter.”
Tool maturity risk: “MISRA 2023 tooling may be incomplete; template-heavy code will generate noise.”
ROI uncertainty: “No guarantee this wins new users; many safety orgs still roll their own non-template libs.”
Concrete next step (low-risk)
Let’s commission a short feasibility report: identify 5–10 candidate libraries, run a real MISRA-2023-capable tool trial, quantify deviations/false positives, and then decide.