SYSE.4:12 - Relations

• A practitioner can recover the named claim and decision question from results produced through SYSE.1, SYSE.2, C.30, C.32, C.32.PAD, SYSE.3, or a specialist practice. The engineering-assurance account states changed reliance and the smallest affected answer; the practitioner decides whether to revise that answer.
• A compatible SYSE.10 engineering claim assessment may contain evidence-use relations only for the same load-bearing claim, decision question, subject, configuration, use, conditions, interval, and evidence window. The practitioner uses SYSE.4 to select any further challenge, qualify the evidence use, and record an assurance or reliance judgement. If the assessment is unavailable, stale, outside scope, or incompatible, use qualified direct evidence sources or record the missing assessment. Using the assessment gives no experiment choice, technical decision, assurance conclusion, acceptance, permission, or release authority.
• A compatible SYSE.11 result may contain integration and observed-use evidence only for the same actual System, configuration, use, conditions, interval, and evidence window. The practitioner uses SYSE.4 to qualify that evidence through A.10 and record an assurance or reliance conclusion. If the result is unavailable, stale, outside scope, or incompatible, use a qualified direct source or record the missing integration or use evidence. Using the result gives no modernization choice, release, permission, or assurance authority.
• A compatible SYSE.14 change-and-release decision may cite evidence for individual claims, configuration and effectivity basis, and unresolved conditions only for the same release question, configuration, effectivity, interval, and evidence window. The practitioner uses SYSE.4 to qualify that evidence and may narrow reliance, abstain, or record the blocker. If the result is unavailable, stale, outside scope, or incompatible, use qualified direct evidence and configuration sources or record the missing change-and-release result. Using the decision episteme as a source gives no release authority, permission, or assurance conclusion; it also does not substitute for the evidence it cites.
• Use A.15.2 for the intended challenge WorkPlan. Use A.15.1, the applicable system-role assignment pattern, and Work-attribution patterns when the challenge Work actually occurs. Naming the DPF plan or account does not establish an assignment, performer capability, resource availability, performed Work, result, or obtaining transformation.
• Use C.16 for measurement, C.32.ACE for architecture-characteristic evaluation, A.1.1 for model applicability and use, and C.28 for causal use. Each result retains its subject, Method, configuration, uncertainty, applicability, and validity limits before it can be used as evidence.
• Use A.10 to recover the descriptive claim-bound evidence/provenance path. Use G.11 and C.27.TA when currentness, decay, calibration, configuration time, or an observation window changes admissible use. Use B.3 only for a named assurance use or material-reliance threshold.
• Use C.11 for a local decision, A.21 for a gate decision, and A.2.8.PER for permission when those claims are current. Acceptance, certification, release, obligation, responsibility, authority, safety, security, ethics, law, compliance, and finance remain with their direct patterns and specialist practices.
• The engineering-assurance plan and account are C.2.1 epistemes carrying the working claims and references used to plan a challenge or reassess reliance. Use the direct patterns for tests, evidence bundles, assurance results, decisions, gates, and lifecycle structures.