Question: How should the ASIL_B OCI requirement in Lifecycle be satisfied?

[fortunaLim]

feat_req__lifecycle__oci_compliant is rated ASIL_B, while the related stakeholder requirement
stkh_req__hardware_support__container_tech is QM (valid from v2.0.0). As discussed in #2934,

As far as I know, no functional-safety-qualified OCI runtime exists today (crun/runc are not developed to ISO 26262.

Which direction does S-CORE intend to take?

• (a) Develop an OCI runtime (a safety-relevant subset of runc/crun functionality) inside S-CORE
  according to the S-CORE process, so it can be qualified at ASIL B — e.g. in Rust per DR-001
• (b) Treat the OCI runtime as an external element (OS vendor responsibility, e.g. QNX, Red Hat)
  and cover it with assumptions of use
• (c) Limit container execution to QM and align the feature requirement accordingly

If (a) is considered in scope, would S-CORE accept such a runtime as a module or incubator
repository if contributors come forward?