Section 31 of 103
30. Recommendation, Permission and Prohibition
Stable section ID: S05-CON-015-SECTION-31 · 6 content blocks
A Recommendation expresses a preferred course of action using “should” or “should not.” An alternative may be used when it is technically justified and does not violate an applicable requirement or rule.
A Permission authorizes an option using “may.” Permission allows an action but does not require it. A conditional permission applies only when all stated conditions are satisfied.
A Prohibition establishes an action, state, condition, or interpretation that is not allowed. It shall be expressed using “shall not.”
Recommendations shall not be presented as mandatory requirements unless they have been formally incorporated into an applicable requirement, standard, specification, contract, regulation, or project baseline.
Permission from System05 does not override applicable law, professional responsibility, safety obligations, interface restrictions, or authority having jurisdiction.
The absence of a recommendation does not imply prohibition. The absence of permission shall not be interpreted as authorization where explicit approval is required for safety-critical, security-critical, certification, or governance actions.