B.2.2:4.3 - System Trigger Interpretation
When a receiving use has materialized B.2’s optional MHTTriggerProfile, read its cues for a system case as follows:
Cue recorded in MHTTriggerProfile | System-case reading | Subject pattern kept visible |
|---|---|---|
| Delimitation change | The operating whole now has an external delimitation and crossing relations that differ from the old aggregate. | A.1, B.1.2, A.14, C.13 |
| Objective or evaluation change | Recover the system-level objective, mission, or SLO used as an evaluation criterion; distinguish any safety case or viability claim from that criterion. | C.16, E.13, A.10, decision or assurance patterns |
| Supervision or coordination change | Recover how constituent behavior is regulated for the result whole, including controller or distributed-coordination facts; name any protocol or governance claim separately. | B.2.5 only for supervisor-subholon feedback; A.12, A.3.4, A.15.1 for their separately current claims |
| Capability or closure claim | Recover the exact capability envelope and closure relations of the proposed new whole after recognition under U.System; keep supporting evidence separate. | A.2.2, C.16, A.10 for evidence use, and B.2.4 when whole reidentification is current |
| Agency threshold | The result whole crosses a concern-specific agency threshold in characteristic space. | A.13, A.19, C.16 |
| Temporal consolidation | A commissioning, phase, release, or operating-time consolidation changes the current system identity claim. | C.27, A.15.1, temporal patterns |
| Context reframe | A changed question or selected model-use structure changes which exact whole is under concern; it does not itself change that whole’s identity. | A.1.1, A.22, B.2, and the whole’s direct identity pattern |
No cue is enough by itself. Each row points to facts and claims to inspect; B.2’s direct existing-whole/new-whole comparison, complete A.1 recognition, and the system-kind criterion decide the result.