Library / Systems Engineering Principles Framework
Jump to passage
In this reading

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 10:39:28 UTC · snapshot created 2026-10-03 10:40:04 UTC · last check 2026-10-03 11:35:10 UTC

SYSE.10:12 - Relations

  • C.2.1, A.3.1, A.3.2, A.3.3, and C.29 distinguish source and result epistemes, Methods, MethodDescriptions, dynamics, and mathematical-lens use without making them physical results.
  • C.11 governs the choice of one next local probe among available options. A specialist experimental-design Method governs a set or sequence of experiments. An authorized Agent applies one of those Methods in separate decision or experimental-design Work and supplies its result to assessment Work. The Agent performing assessment Work applies SYSE.10; that assessment Work does not include the distinct Work that chooses the probe or produces the experiment plan.
  • A.15.1, A.15.2, F.6, and A.15.PROD distinguish planned Work, dated Work, performer attribution, and result production. A procedure, model, report, or status does not establish Work.
  • C.16, C.16.P, and A.18 govern measurement, characteristics, scales, units, uncertainty, and admissible operations. A.10, G.6, and G.11 govern evidence use, provenance, and currentness; C.28 governs causal and counterfactual support.
  • B.3, A.21, G.4, and the applicable acceptance and permission patterns govern assurance, gates, and consequence-bearing reliance. An engineering claim assessment emits none of those results.
  • Assessment Work can produce evidence for SYSE.6, SYSE.4, or SYSE.19 only when the claim, configuration, horizon, and receiving decision match. Evidence neither authorizes nor entails those decisions.
  • Results from engineering Work—for example realization, integration, operation, configuration change, specialist Work, or affected-System inquiry—become evidence only through their source and evidence-use relations. Adjacency between pattern names creates no such relation or temporal order.
  • Applied engineering profiles should specialize Methods for modeling, simulation, experiments, tests, trials, or evidence use only when a domain-specific fact—such as the engineered-System kind, physical mechanism, regulation, characteristic, scale, or consequence—changes the working move. A domain noun by itself adds no profile pattern.