SYSE.2:12 - Relations

• A SYSE.1 project-system choice account supplies the selected actual System or intended System referent, current reason, boundary question, alternatives, and reopen condition used here. A changed use or boundary returns to SYSE.1 only when it changes the project focus.
• A compatible SYSE.16 result supplies selected operational structures, conditions, and unsupported assumptions; a compatible SYSE.17 result supplies qualified consequence claims and unresolved representation or protection needs; a compatible SYSE.8 account supplies only its supported provider-arrangement claims and design constraints. Use each result only for a compatible subject, configuration, use, horizon, evidence window, and decision. These relations do not prescribe an order of engineering Work.
• Use A.3.4 for the identity and boundary test of an actual bounded transformation. Intended, required, and simulated transformations remain claims or representations until that test applies.
• Use A.6.F to recover the object or claim meant by function-like wording and select the direct subject pattern. Use A.6.M only when a module or interface claim is current.
• Use A.22 for selected-structure identity in decision-relevant environment structures. Use C.30.ASV for structural-view adequacy only when a description is relied on for a selected architecture use.
• The linked use-and-system concept proposal supplies functioning, operating conditions, outside effects, selected environment structures, assumptions, and evidence limits to the architecture question. C.30 defines grounded architecture claims and relations; C.32 guides candidate synthesis over selected structures.
• Architecture, realization, operation, or assurance evidence returns to the smallest linked claim it can change. Practitioners in organization change, Operations Management, Platform Engineering, Governance, safety, security, ethics, law, finance, and other specialist practices keep their Methods and supply only the results consumed by the linked proposal.