Design goals: safety shall take precedence over backward compatibility

When safety reasons call for a change to API in the safety environment, the change is typically rejected if it does not maintain backward compatibility. A compatibility-breaking change to API should be rejected only if safety analysis shows that maintaining compatibility is actually safer.

For reference, general issue "Design goals" is defined as issue #26.

Start by reading the referenced general “Design goals” issue #26 and compare its structure with this proposed safety-versus-compatibility principle. Identify where the design goals are maintained, then confirm that the documented rule makes safety analysis the deciding criterion; done means the requirement is recorded consistently with the general goals.

Written by the indexing model from the issue text.