A.1.STM:4.0 - Connect a noticed difficulty with the project account
B.5.PI:4.1–4.5 supplies the general way to initiate inquiry before a problem is felt; its section 4.2.1 explains how a suitable mantra can expose an unexamined connection. Here that operation uses the system-thinking account.
A difficulty, opportunity or task can be the point at which attention starts. Recover what happened or is proposed, whose result or condition matters, and what question a useful answer must settle. A complaint such as “the calculation takes too long” is a signal: it leaves open whether the difficulty concerns a needed product decision, an unsuitable calculation, unavailable means or another purpose. Use C.22.2 when the continuation needs a reviewable problem-side account. If a direct subject Method already answers the question, use it; an ordinary difficulty does not have to become a project or acquire a system-of-interest.
Move into systemic project reasoning when that question depends on how a system’s use, construction or creation contributes to a project result. Follow the concern to the receiving use that gives it significance. The slow calculation may matter because it prevents a construction decision needed for the machine’s intended operation; the inquiry must then recover that operation before selecting faster equipment. This transition turns the initial signal into a more discriminating question or hypothesis: which required result is unavailable, through which dependency, and what would change the answer? Sections 4.1–4.3 supply the connected reasoning. If the use basis is already adequate, section 4.4 can locate the particular gap without reconstructing it.
The mantra enters the same reasoning from the project account. It prompts examination of use, functioning, construction and provision even when nobody reports a difficulty. For example, it can reveal that a new sensor will be inaccessible for calibration although every team is content with its local design. The missing joint condition becomes a question to investigate; it is not a diagnosis proved by the reminder. Starting from a complaint can reconstruct that same dependency without prior knowledge of the mantra. The reminder makes the consequential questions available directly, while the developed account explains why those questions matter.
Thus the point where attention starts and the order of justification have different jobs. The entry reveals a candidate question. In a systemic project comparison, use and encompassing functioning supply the first grounds for deciding what to construct and provide. A discovered constraint can send the reasoning back to those grounds. Return a supported answer, a changed proposal or a precise uncertainty to the original concern, then obtain the needed subject contribution and follow its receiving use. If no project dependency is material, finish the direct inquiry at its own scope.