SYSE.6:12 - Relations

• SYSE.5 describes how to produce explicit allocation choices and conflicts. Practitioners using SYSE.6 recheck a compatible result’s subject, configuration, horizon, evidence, and conditions before using it as a candidate-set input; generation does not select.
• A compatible SYSE.8 account can supply provider-arrangement constraints that change this architecture decision. Recheck its subject, configuration, use, horizon, evidence window, and availability. If it does not fit, use a qualified direct source or record the missing result. Keep the described offering or arrangement, provider Systems, performed Work, consequences, responsibility, and authority as distinct objects.
• A compatible SYSE.7 account or SYSE.10 assessment supplies evidence only when it can change this decision at the same configuration and horizon. A compatible SYSE.9 account supplies a specialist result for its receiving question and conditions. During decision Work, a conditional SYSE.9 request names the question, subject, conditions, authority, and desired result. Evidence and specialist results inform the choice; the decision subject retains the authority to make it. If an input does not fit, use a qualified direct source or record the missing result.
• C.32.PAD supplies the decision relation and the distinction among selected option, affected structures, Method and Work consequences, publication projection, and reopen conditions. C.32.ACS defines criteria rows; C.32.ACE defines eval programs and results; direct comparison and choice patterns govern their own claims.
• SYSE.6 can supply selected-structure constraints and reconsideration conditions to SYSE.3, SYSE.13, and SYSE.18 when they constrain the receiving design choice. The Agent performing each receiving Work applies its Method to generate and compare that Work’s own alternatives and checks subject, configuration, horizon, and compatibility. If the decision result does not fit, use a qualified direct source or record the missing result.
• Practitioners use SYSE.4 in assurance Work to qualify the engineering decision or identify the basis it still lacks. That assurance result is separate from architecture selection and from later acceptance, permission, release, and observed use success.
• C.32.ADR, C.30.AD, E.17, and E.24.PUB govern decision projection, architecture description, source-backed publication, and audience availability. A current decision can exist without one particular file, and a file can persist after the decision is superseded.
• Application DPFs retain subject-specific architecture Methods and safeguards for engineered-System profiles—for example, software, electrical, mechanical, civil, ship, medical, manufacturing, or human–AI engineering.