A.1.STM - Connect Project Reasoning (System-Thinking Long Mantra)
Type: Part A practitioner application pattern Status: Stable Normativity: Normative unless marked informative
Plain name. Use the system-thinking long mantra.
Long mantra and attention map are Plain names for a repeatable reminder and its readable display of connected questions. The developed account connects knowledge about use, functioning, construction, creation and cooperation. Its short wording helps keep that account in attention; it does not supply the knowledge that the account needs.
A.1.STM:0 - Practitioner entry
Use this when. Use this pattern when participants have knowledge about parts of a project but need to connect it into one systemic account: what should change in use, which system can make that difference, how it could function and be constructed, how it can be obtained, and how its creators can work together. Their answers must fit together, not merely be plausible separately. Identify the product system-of-interest (SoI), the extended enterprise in which it has that role, and the receiving use relevant to the decision. Retain several SoIs when their uses or shared commitments matter. Use the pattern also when participants say “our system” but leave its project context, contribution or receiving use unclear. A narrower use is to locate the first unsupported dependency when the connected account is already sufficient.
First useful move. You may arrive with a felt difficulty, a proposed change or a project account worth examining before trouble is noticed. Section 4.0 connects those entries. For a systemic project question, recover what should become different or remain possible in use, for whom and when. From the system’s boundary, look upward to the larger functioning whole and the joint action of its parts. Use that account to derive the system’s needed contribution before justifying its internal construction and the work needed to obtain it. Reuse a sufficient existing account; when the larger whole is unknown, investigate that question. Sections 4.1–4.3 develop this order, 4.3.1 connects the answers, and 4.4 locates a bounded gap.
Memorable reminder.
First look toward use: what should change, for whom and when? From the system’s boundary, look upward: of which larger functioning whole is it a part, and what do those parts accomplish together? Investigate an unknown whole. Derive what the system must do there and name the system sought by that function. Then look inward to possible constructions and backward to ways of obtaining them, needed contributions and capable creators. Organize their work and means so the contributions can be used together. Repeat for needed creators while retaining the results they serve. Follow what happens and revise the answers whose grounds change.
This is the Plain long mantra. Its first moves establish the use that gives the later choices their reason. Section 4 explains the two directions, the returns after changed knowledge, and the difference between this reasoning order and a schedule of work.
Not this pattern when. A known local system-recognition, service/access, architecture, Method, Work, transformation, evidence or closure question can be answered through its subject pattern. Such a result need not reopen the whole project account. Use this pattern when the common basis or the connection to it is itself at issue.
What this buys. Participants can form and criticize a connected project account, justify why its choices belong together, find a consequential incompatibility or missing answer, and revise the affected part without losing the whole. They distinguish a System’s product role in an extended enterprise, the current local subject and the receiving connections between undertakings, while preserving valid local results. The account can remain ordinary prose and existing project descriptions; no new universal project record is required.
A.1.STM:1 - Problem
Division of labour lets different participants work on components, methods, descriptions, tools and provider organizations. Their local choices become coherent only if they can explain what common outcome those choices are intended to obtain. A component may meet its specification while the whole remains unusable; a provider may become efficient at producing something its intended users do not need. Local completion alone cannot settle the shared project purpose.
The system-of-interest (SoI) is the product System that a particular extended enterprise is organized to create, change, sustain in use or retire. An extended enterprise organizes participating enterprises and other organizations through agreements about their work, supplied results, decisions and means. Agents acting for those organizations establish or accept the objectives and commitments. Intended use, expected benefit and the effects of ending use give reasons for those decisions. A participant can undertake only a bounded part, such as a commissioned alteration or a period of maintenance. A project account can carry this common SoI through one temporary body of work; each supporting project need not acquire a separate SoI. The same machine can be the SoI of its manufacturer’s product undertaking and a means of production for a component manufacturer. Its identity need not change when that relation differs. Before a future system exists, describe the intended system and use without asserting an actual holder.
The current subject of inquiry or local work answers a different question: what must this participant understand, obtain or change now? It can be a component, test rig, creator organization, Method or episteme. For a system, system-in-hand or our system can identify that local subject once the participant’s relation to it is clear.
In organizational work the organization remains the creator being engineered, while its products supply the SoI and the use that justifies its capabilities. Treating the firm itself as the common purpose can make necessary product work appear to be a dispensable expense. Conversely, a product design that ignores the creators’ means, rights and commitments may never become usable. The connected account must make both consequences visible in the decisions that allocate and provide work.
A project can also get every nearby statement locally right and lose the long dependency. A functioning argument can assume one construction while the creation plan can supply only another; capable contributors can require incompatible shared resources. Agreement on the SoI does not by itself make these answers jointly usable. One team improves a component, another produces a builder, and another measures operation, yet nobody can show how those results are expected to reach the SoI’s use or which actual relations now connect them. A diagram arrow, the word creates, or a calendar sequence can hide that gap.
The opposite failure is to turn the reminder into a universal route. Then every result becomes a System, a plan becomes an existing holder, project Work becomes a network, and every arrow appears to be the same relation. A.1.STM develops the shared systemic reasoning while leaving each local truth with its subject pattern.
A.1.STM:2 - Forces
| Force | Tension |
|---|---|
| Whole-project coherence | Participants need a compatible basis for a joint decision while their project scopes, systems-of-interest, interests and local results may differ. |
| Use and encompassing functioning first | Intended use and the wider functioning at the operating time give reasons for construction and provision; discovery and feedback can reopen that basis. |
| Backward justification | Reading from value toward missing support is useful, but it is not temporal order or transformation direction. |
| Forward actuality | Work and changes must be traced through facts that obtain, not through planned arrows or shared names. |
| Local contribution | A team needs to know how its result matters without inventing a universal contribution relation. |
| Recursive builders | Build-the-builder reasoning must recur without a creator kind, fixed levels, or a generic creates edge. |
| Evidence and return | A supported answer may later become stale or fail; reopening should be local rather than restarting the whole map. |
A.1.STM:3 - The attention map
Keep these connected questions available while reasoning about the project. Begin the justification with receiving use and the wider functioning in which the system participates, then examine its construction and creation. Reuse answers already sufficient for the current decision and investigate a gap where it can change that decision. The rows are reminders, not mandatory fields or work stages. One ordinary sentence can answer more than one question.
| Region | Plain question | What the answer enables |
|---|---|---|
| Outside change and use | What should become different or remain possible for whom, in which operating situation and time? | Establish the result sought, receiving transformations and success conditions, including a proposed future use. |
| Wider functioning at that time | Of which larger functioning whole is the system a part, and how does the joint action of the parts produce the result sought? | Establish the relevant part–whole relations at the operating time, moving through the levels and inclusions that affect the decision. An unknown whole leaves an inquiry to resolve. Keep use, interaction, ownership and creation distinct from containment. |
| Project systems-of-interest and uses | Which systems and receiving results matter to this decision, in which projects, and which boundaries and connections must the participants agree? | Connect contributions to the relevant uses and shared conditions through section 4.1. A future system can be described before an actual holder exists. |
| Functioning and the system sought | What must the system do in use? What kind of system are we seeking by that function? | State the required behaviour, then a functional description such as “coolant circulator” and the conditions for a suitable candidate. Section 4.3 explains how this opens the choice of constructions. |
| Construction | What organization, parts or materials could provide that functioning? | Compare possible constructions and their operating conditions through C.32.P2S and the C.30 family. |
| Ways of obtaining the system | How could the chosen construction be produced, changed, verified and kept usable? | Identify applicable Methods and what they require. A.3.1 and the A.15 family distinguish a way of doing from its plan, performance and result. |
| Creator contributions and fit | What work and results do those Methods require, and which people, teams, equipment or other systems can supply them here? | Select or develop capable creators. A.2.2 compares their qualified abilities with the demand; an occupation name or assignment does not settle that comparison. |
| Cooperation and needed creators | How can the contributions be available together, and which creators must themselves be obtained or changed? | Resolve shared resources, access, authority, timing and handovers; repeat the reasoning for a missing builder while retaining the results its contribution must serve. Section 4.3 develops these connections. |
| Local result and receiving use | What is our present subject, who or what uses the result next, and how does that use serve the SoI? | Preserve a useful component, instrument, description or argument at its own scope and establish the relation the next use needs. |
| Grounds and revision | What supports the answers relied on together, what remains unknown, and what changed condition sends us back? | Use section 4.3.1 to compare whole proposals and revise affected answers. Use A.10 when evidence support is the question and B.3 for a named assurance use. |
First follow the anticipated contribution toward receiving use and examine the relevant containing whole upward, at the operating time. With that basis available, reason backward along the providing flow to what must be obtained and downward into construction to what could realize the functioning. These are two axes: a creator can provide a system without containing it. Test the proposed causal connections forward, then follow actual results as they become available. Reasoning direction, subject relations and planned or performed Work order remain distinct.
When actual relations or a network are the question. A proposal can be compared before it has been realized. An actuality claim needs the facts for that claim. For an actual runtime change, identify the environment or input referent that changed under A.3.4 separately from the existing system’s functioning, causal, interaction or participation claim. Add an assignment, Method or Work claim only when it is needed and independently supported. A required effect or an observed output alone does not establish that change or those system-side relations.
For an actual production account, distinguish Work, changes of continuing materials or parts, production participation, the new entity’s identity inception, completion and later use through A.15.PROD and the relevant subject patterns. A system cannot undergo a change before it exists. Use an available recognition result for an actual system; section 7 supplies the return when systemhood is unresolved.
When the receiving question needs a transformation-flow structure or a network of such structures, use E.18 to identify each TFS and E.18.NET for the network. The latter requires independently identified members, exact obtaining cross-member relation occurrences, complete endpoint bindings, applied constraints and the use frame. Production, operation, verification, feedback and recursive builder branches can concern different members.
A shared entity, temporal adjacency or a drawn arrow supplies no relation between them. Keep a proposed network provisional and name the missing member, governor, predicate result, occurrence or binding. An ordinary project explanation need not make this network claim.
A.1.STM:4 - Solution
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.
A.1.STM:4.1 - Establish the project system-of-interest, its use and the participants’ agreement
Start with the intended use because it tells the participants what their internal choices must accomplish. Describe the operating situation, its time or period, the affected participants and the changes or maintained conditions that matter to them. Ask what would be lost if the proposed system were absent, unusable or no longer maintained. The answer can concern a desired change, a condition that must continue, or a harmful effect that should cease. “Produce the deliverable” is insufficient while nobody can say what obtaining that deliverable is supposed to enable.
Recover the extended enterprise alongside that use. Identify which enterprises and other organizations have agreed to create, change, sustain in use or retire the product, what each has undertaken, and which agents may establish or accept the relevant objectives and commitments. Existing agreements and knowledge of the work can supply this account. A supplier can contribute one alteration without undertaking the whole product’s creation or later operation. Distinguish the organization of joint work from the projects performed within it and from the product System.
For sustaining in use, state the condition or availability to be maintained, the period and the agreed acceptance. For retirement, state which use ends and what condition the assigned work must achieve. Those are different undertakings, and either can have a finite obligation. The organizations now maintaining or retiring a product need not be its original creators. A role claim about an actual holder remains bound to the time at which that System exists.
If the enterprise or some commitments are still proposed or unknown, retain their prospective or unresolved status. Investigate the missing organization or agreement where designation depends on it; continue independently supported engineering on the system-in-hand. A shared product name, supplier list or contract title alone does not establish an organized joint undertaking.
Follow the intended contribution toward its recipients: what will use the result next, and what will that use change or keep possible? Set out the boundary of the system being considered at the operating time, provisionally when the design is still open. From that boundary, move upward to the larger physically embodied whole of which it is, or is intended to be, a part. Identify the other parts and explain how their joint functioning produces the receiving result. For a pump, examine the water-supply installation: the pump’s contribution depends on the inlet supply, downstream path, power and control arrangements that make delivery possible. This account gives reasons for the pump’s required function before the choice of its internal construction.
Continue through the levels and supported inclusions whose conditions can change the decision. A pump can be part of a pump assembly that is itself part of a station; demands on the station can constrain both the assembly and the pump. One tree need not represent every relevant inclusion. State the whole, part relation and operating time for each relied-on connection, and reuse an adequate account already obtained for it.
Keep the two relations visible. Moving along receiving transformations follows what affects or enables what. Moving upward through system composition follows which system is part of which larger system at the time considered. A using system need not contain the used system, and a manufacturer is not its product’s suprasystem merely because it makes the product. A manager, owner or larger project is also not an encompassing System by title or scope. A.1 and A.14 govern a relied-on composition claim; C.30.STRAT helps when a level word still hides its meaning.
When the larger functioning whole or its composition is unknown, keep that question open and obtain the missing account. Inspect the operating arrangement, consult those who understand it, or investigate a proposed configuration. Describing neighbouring objects and their interactions can supply evidence for this work; it does not complete the upward move. State which function or construction judgement remains unsupported and continue inquiry or other work whose grounds are available. A.1:4.2’s possible participation in a larger assembly is a recognition condition; it does not identify the containing system and functioning needed for this project decision. Neither that condition nor the absence of current knowledge removes this inquiry.
Use the larger whole’s functioning to propose how the system’s functioning or other intended trajectory could meet the need. Refine the proposed SoI and its boundary, and describe it as a black box: what it encounters, what it does or permits, which conditions it must tolerate, and what its users or other affected participants regard as success. A functional name such as pump, learning aid or diagnostic instrument is a useful hypothesis; it does not settle the physical boundary or the A.1 system criterion.
For a system still to be created, this is a possible future operating situation. Describe the proposed holder, interactions, receiving changes and conditions without asserting that the holder or effects already exist. A desirable outcome gives a reason to investigate a design. Explaining how it could occur requires a mechanism and conditions: for example, how flow, pressure and the surrounding installation together could deliver water at the required outlet. Qualify that hypothesis with suitable engineering grounds and revise it when tests or later use disagree. The purpose alone supplies no causal connection.
Compare the participants’ accounts. Ask each relevant team and external participant to explain the proposed SoI in the same use situation and to locate its own contribution. Differences become actionable: one team may describe the provider organization, another the delivered system, and another the report about it; two teams may intend incompatible configurations under the same name. Resolve the consequential differences through inquiry, conversation, option comparison and, when needed, experiments or prototypes. C.11 helps choose among formed alternatives; it supplies neither the creative formation of those alternatives nor proof that several participants understand and accept the same choice.
Seek a working agreement adequate for the decisions being made: the product Systems and extended enterprises involved, intended use or withdrawal from use, relevant boundaries, success conditions and each organization’s commitments. Identify the agents entitled to settle or revise them. Participants may retain different interests. State a consequential unresolved disagreement and who can settle the affected decision; do not present a single chooser’s designation or a shared document title as evidence that agreement already exists. The useful result is a supported, revisable basis that the participants can use together. Inquiry and negotiation may still leave an important designation or agreement unresolved.
A project can seek several systems and other results. For example, a project may supply independently identifiable instruments to two laboratories, together with explanations and operator preparation. Recover each receiving use and the shared conditions that constrain the current decision. Neither the project label nor this plurality makes the instruments, explanations and preparation one System. When the question concerns one instrument, ordinary reasoning can follow that SoI alone while retaining any dependency that matters.
Different product undertakings can have different SoIs and boundaries. A supplier’s engine, an integrator’s aircraft and an operator’s transport installation need not be the same entity. Recover the extended enterprise for each product undertaking, its usable supply, recipients, product decisions and fitness obligations. Agree the contributions and conditions used in joint work; a supplier can participate in more than one such enterprise. The customer may specify the engine’s whole design and intended use; the supplier need not control the customer’s product strategy. The engine’s receiving use constrains its fitness without making its supplier responsible for every later aircraft. A separate project, budget or contractor for the same organizational work leaves its product-use basis in place.
Keep these answers distinguishable:
| Expression | What it selects | Practical consequence |
|---|---|---|
| System-of-interest (SoI) | The product System that a named extended enterprise is organized to create, change, sustain in use or retire. | Recover the participating organizations, their agreements, the agents’ objectives and the intended use or withdrawal from use. One or several product SoIs can constrain organizational work; each future system remains described until it exists. |
| Current subject of inquiry or local work; system-in-hand for a system | Whatever must be understood, obtained or changed for the present decision. | A creator can be fully engineered and locally accepted while the product SoI and its use continue to justify that work. Methods, epistemes and other subjects retain their own names. |
| Required functioning | The behaviour or contribution needed in use, such as circulating coolant at a required rate under stated conditions. | Supplies a demand to investigate; it does not yet select a construction or establish an actual effect. |
| System named by its function | The kind of system sought for that contribution, such as a coolant circulator. | Opens the search for suitable systems and constructions. This functional classification differs from the System’s product role in an extended enterprise. |
This Library uses system-of-interest (SoI) for this product role in an extended enterprise. The product and that organization are different Systems; the role relation alone makes neither a constituent of the other. When another source uses system-of-interest merely for whichever system an observer investigates, recover that source meaning explicitly; use system-in-hand for the local system in the present account. “Our system” needs the relation that makes it ours: what we make, change, operate or provide.
A component, instrument or machine can be the SoI of a distinct product undertaking when an extended enterprise is organized to supply it for use to identified recipients or a known class of recipients, with a bounded product decision and obligations for its fitness. For example, a test-rig manufacturer supplies a usable instrument to laboratories. In the pump cooperation, a laboratory developing its test capability remains a creator, and its rig can be the local system-in-hand. The actual supply and obligations explain the distinction; incorporation, internal transfer prices, a contract or the word project do not settle it.
An organization being created or changed remains a creator with its own engineering object. A new team, factory or business can have a complete design, agreed boundaries, a budget, a contract and finite acceptance. Its product or products still supply the SoI for this work. This applies equally to an internal team, an external consultant and a supplier of a ready-to-operate enterprise. Valuing or selling the organization makes it an object of an investment or transaction; its price, asset value and ownership rights do not replace the useful use of its products.
A changed product purpose requires reconsidering the sought results, recipients, boundaries, funding basis and dependent agreements with those entitled to change them. Participants may develop another offering or end one that is no longer justified. Make that decision explicit. A new label for the same organizational work changes none of those grounds.
A.1.STM:4.1.1 - Develop a creator from the use its products must support
For work that creates or develops an organization, connect three answers: what product use and benefit must become possible or remain possible; what the creator must be able to do for it; and what local result this work will deliver and how it will be accepted. Use this connection in the choice and provision of work. Reuse adequate existing answers; a separate form or a fresh account of the entire enterprise is unnecessary.
- Name the product use that gives the work its reason. State the required change or preserved condition in use, the recipients and conditions that can alter the decision. For a shared creator, name the products or application classes whose demands affect this choice. Necessary accounting, maintenance, learning, funding and future capability can deserve provision through the work they enable; proximity to a product drawing is not the test.
- Derive the needed capability. Explain what the creator must reliably provide under the expected workload and conditions: relevant Methods, people, means, access, cooperation and authority. Retain the creator’s own boundary and architecture questions. An agreed purpose gives a reason for that capability; it does not establish the mechanism, available resources or people’s ability to perform.
- Choose a finite local result and its acceptance. State which capability, or bounded contribution to it, this work must establish and what evidence can establish it now. Acceptance of an installed machine, a research report, a prepared team and a functioning workshop answers different questions. If workshop capability is promised, establish that the needed Methods, means, people and handovers can work together under the agreed conditions. A component delivery can close while the wider capability remains open.
- Make provision and trade-offs real. Obtain the resources, access, time and authorized agreements that the chosen capability requires. Where products compete for shared capacity, compare the affected uses and commitments together. State who may change the allocation or accept the loss; a local manager can decide within delegated authority, while a loss outside it goes to those entitled to decide. Neither one product’s improvement nor one department’s metric settles what happens to the others.
- Close this work at its agreed scope and retain the receiving connection. Judge the local result against its actual acceptance basis, including the evidence sufficient for the promised capability and the declared uncertainty. Do not wait for every future product to operate. Keep the expected product effect conditional on its remaining contributions and use conditions, and state which later observation would reopen the capability or product decision.
Unknown future uses can be represented by application classes, scenarios and explicit hypotheses. When the receiving result is an episteme or another non-System subject, keep that result and its use explicit; leave a needed systemic designation open instead of filling it with the creator.
Research may establish that a proposed benefit or capability is infeasible; a well-grounded negative result can support revision or stopping. Judge an independent research result by its epistemic question and acceptance criteria. When commissioned to inform a capability decision, also assess its fitness for that decision. Accepted knowledge does not itself establish the capability it investigates. A theorem, historical explanation or openly reusable knowledge needs no invented physical SoI or immediate commercial application.
Keep provision and benefit connected but distinguishable. A customer, user, payer and investor can be different participants. Funding, an internal allocation, income or an asset sale can make work possible without establishing product usefulness; a justified useful result can precede revenue or rely on subsidy. Give those who decide resources and acceptance the relevant product-use and capability consequences, together with the rights and financial conditions of the choice.
A.1.STM:4.2 - Keep role, holder and future description distinct
The SoI role relates the product System to the extended enterprise organized for the agreed creation, change, sustaining in use or retirement explained in section 4.1. A holder is the actual System occupying that place; a description states what the participants intend or believe about it. These can be discussed together without treating them as the same object. An existing pump remains the project’s SoI when it fails a performance test: success is what the participants seek, not a condition that makes a failed SoI disappear from the undertaking.
Use ordinary role wording under A.2:4.9 while it is enough. If classification matters, define the local system-role kind under A.2 and C.3 through its System candidate domain and the work-facing distinction the project needs. For a SoI classification, the criterion must identify the extended enterprise, its agreed undertaking for the product and the designation grounds. A rig investigated only to support another system does not thereby take that other system’s role in the wider project. A criterion that selects merely whatever an observer studies answers a different question. If the needed criterion or its governing relations are unavailable, retain the ordinary project account and leave that technical classification unresolved.
If assignment identity matters, A.2.1 requires an obtaining occurrence with an actual System holder under a declared species. System recognition, project designation, classification and assignment remain different claims; none is created by writing the role’s name.
A new system can be intended before any holder exists. Agree the SoI role, intended use, required characteristics and boundary hypothesis in a plan or description. Describe the intended holder, its proposed identity rule and how later instances would be recognized. Before identity inception, this is prospective content, not an actual System or assignment occurrence. A.15.PROD separates production participation, the first satisfaction of the entity’s identity rule, and completion. After inception, relate the actual holder to the earlier description and evaluate the claims needed now.
Design reasoning also works with types, variants and repeated provision. A project may intend a series of systems satisfying a common specification rather than one already named individual. State the common intended use, the distinguishing requirements and what counts as one resulting instance; track actual holders as they become identifiable. The specification, the kind it describes and a collection of instances do not thereby become one System. Where materially different SoI families have different users or use conditions, preserve their separate SoI accounts before comparing shared builders. A vague umbrella such as “equipment” does not supply that comparison.
A.1.STM:4.3 - Derive the long mantra from the intended use
The order below gives the direction of project justification: establish intended use and the wider functioning first; then investigate construction and the ways of obtaining it. An answer supplies requirements, possibilities or limits for other answers; it need not determine them uniquely. Reuse an adequate outside-use basis. Later construction or capability knowledge can reopen it. Resolving these mutual constraints, including such returns, makes the account usable.
-
From the system boundary upward to encompassing functioning, then to the SoI contribution. Describe the required receiving change or maintained condition in a selected operating situation. From the proposed SoI boundary, identify the larger functioning whole, the other parts and the joint functioning in which the SoI contributes. Follow the relevant levels and supported inclusions as section 4.1 explains. Derive what the SoI must do, through which interactions and under which conditions, for that result to be possible. An unknown containing whole leaves this derivation open and calls for inquiry. Work through the scenario before justifying an internal solution. If the SoI does not yet exist, retain this as a future-use hypothesis; investigate its mechanism and conditions.
-
From functioning to the system sought, then inward to possible constructions. Name the kind of system being sought by what it must do in use. For example, after stating the required circulation of coolant, “coolant circulator” names the sought thing by that function. Use the functional description and operating conditions to identify suitable candidates before choosing their construction. Compare why different arrangements could meet the same demand and where they would fail. The name helps search and communication; suitability needs an argument about the candidate under those conditions. Starting with a favourite component can conceal an alternative construction that would serve the use better. C.32.P2S and the C.30 family develop that architecture choice; A.1.SCR tests an actual proposed whole when systemhood matters.
Required behaviour and the system sought are different answers even when one phrase expresses both. “Circulate coolant” states an action; “a coolant circulator suitable for this circuit” identifies what is being sought. Neither requires an extra field or a different word when the existing explanation is clear. Informal functional role wording may express this functional consideration. It does not by itself establish an assignable system-role kind under A.2. Use A.2 when classification by a stable, assignable contribution to work is needed; use A.2.1 for a claimed assignment. The functional description, chosen construction and proposed or actual system remain distinguishable.
-
Backward from the needed construction to ways of obtaining it. Determine what must be produced, assembled, changed, learned, verified or maintained for the proposed construction to support the intended use. Compare the necessary Methods and their subject matter. For example, choosing a welded assembly, a learned controller or a different service arrangement changes the ways and capabilities needed to obtain it. A.3.1 and the A.15 family distinguish the reusable way, intended work, performed work and its results.
-
From Methods to creator contributions and capable performers. First state the kind of work and result required by the chosen Method: for example, joining the selected material by welding, producing a learned controller, or calibrating the assembled instrument. Name the corresponding creator contribution in familiar professional terms when this helps find the needed practice. The Method and its subject matter give that name its meaning; a job title alone does not supply the way of doing.
Then compare concrete people, teams, equipment or other systems that could provide the contribution under the required conditions. A change from welding to another way of joining can change the needed contribution, tools and capable performers even while the intended product stays the same.
Use A.2 for a needed system-role classification or assignment question and A.2.2 to establish qualified ability and fit. An able candidate can be considered before it is assigned. Tools can participate in production without being independent agential performers; A.13 and A.15.1 govern any actual performer and Work claims.
-
From capable creators to their cooperation. Determine how their contributions can be made usable together. What must each receive from another, what shared conditions must remain true, and which decisions or changes must be agreed? Separate capability from availability and authority: each contributor may know how to perform its part while their combined work cannot obtain the result. Develop candidate arrangements of contributions, information, resources and decisions through C.32; use B.1.5.EW when the constituent and encompassing work is unclear. A common aim explains why to cooperate but does not settle how. If organization or supporting equipment must change, that becomes another creation question rather than a promise supplied by a team name.
-
Repeat for the creators that must themselves be obtained. A missing instrument may need manufacture; a team may need training or organization; a production installation may need redesign. Apply the same questions to that local system while retaining its contribution to the original SoI. A builder’s period of use can be a period in which another system is produced or changed. This connection is not composition: a factory is not a constituent of its product.
-
Follow each local result into its receiving use. State what receives it next and what that use is expected to enable on the way to the common SoI. Inspect the resulting facts as work proceeds. Failed tests, new interests or an unworkable method may reopen the construction, functioning, SoI boundary or even the original purpose. Reopen the premise that failed rather than protect the earlier choice because work has already been spent.
When the SoI, intended use, boundary or expected contribution materially changes, compare the affected participants’ accounts again and trace which decisions rely on the changed premise. Restore the agreement needed by those decisions and make its revised basis available to the participants who must use it. Agreement between two teams does not update other dependent teams’ decisions; resolve or expose that remaining difference before relying on their combined work. Unaffected decisions need not be reopened.
An inverse inquiry can begin with an available person, tool or scientific result and seek a worthwhile use. Once a possible application is found, recover its receiving effects and wider functioning before justifying the construction or provision proposal. This preserves the same direction of justification without pretending that use was known at the start. Negotiation, exploration, fabrication and testing may overlap or repeat. Use a WorkPlan for intended execution order and actual histories for what happened.
A local result keeps its own kind and closure. A drawing’s content or a research argument can be an episteme; a measurement result can concern a characteristic; a completed workpiece is a separately identified entity. Show the connection through the relation needed by the next receiver, such as use of a description in design, installation of a component, or evidence supporting a decision. A.15.6 recovers the result and closure question; A.15.PROD distinguishes entity inception and production completion from later acceptance or use. The local result need not be a System to matter to the SoI.
Also separate two questions: is this Work part of the project Work, and does its result help obtain the SoI? Actual Work parthood uses A.15.1. A purchased instrument or a published theory may be useful even though the work that produced it was outside the project; an admitted project Work part may fail to make the expected contribution. Prospective dependencies justify plans under their stated assumptions. Actual relations and outcomes need their own evidence as they occur.
A.1.STM:4.3.1 - Assemble and revise a jointly workable account
Take the question reached through section 4.0 and recover the intended use and wider functioning that give it significance. Reuse that basis when sufficient; otherwise develop it before justifying a construction or a choice about its creators. Then recover the other answers already available and the conditions under which each is supported. A required use, a proposed construction, a demonstrated capability, an agreed resource allocation and an observed result have different grounds. Keep an important unknown or disagreement visible. A drawing that leaves it blank is not evidence that the condition is satisfied.
Explain how the subject matter of each answer constrains the others. The expected outside effect constrains the needed functioning; a construction makes some functioning possible and rules out other functioning; a creation Method requires particular subjects, capabilities and conditions; a cooperation arrangement determines whether those contributions can be available together. These relations need the relevant engineering, research, economic and organizational knowledge. The mantra recalls where that knowledge matters; it cannot deduce an unknown material law or create a missing production technique. Obtain the missing subject answer and bring back its conditions as well as its conclusion.
Compare coherent combinations. Do not combine the performance of one design with the cost of another, the capability of a fully prepared team with the schedule of an unprepared one, or a successful test with a later configuration the test did not examine. For the candidate under consideration, ask why its functioning, construction, obtaining Methods and creator arrangement can jointly serve the intended use. A supported local answer becomes part of this account only with the conditions needed for its use in that combination. The whole may remain a justified proposal; compatibility of the proposal does not establish that it has been realized.
Challenge the connection where a different allowed answer could matter. If a component, operating condition or creator changes, which other answers still hold, which must change and which become uncertain? Follow the material dependencies rather than changing every document or defending every earlier choice. A single defect can have several repairs: revise a construction, obtain another capability, change a way of producing it, or reconsider the promised use with those entitled to make that decision. Each repair has its own conditions and cost. Merely moving to the next phrase of the mantra chooses none of them.
Choose the next inquiry or construction for the consequence it can have. A missing fact may require measurement; incompatible answers may require a new alternative; disagreement may require clarification or negotiation; unavailable capability may require provision or development. Use the relevant subject Method and compare consequential alternatives when necessary. An unresolved release condition can leave release unavailable while inquiry, prototyping or obtaining support remains possible. Several independent questions may be pursued at once. Their results must return to the same candidate assumptions before being relied on together.
This is the useful sense of the analogy with solving simultaneous equations: partial answers restrict one another, and changing one can require changing others. It does not say that all questions have numerical variables, that normative agreement is an equation, or that a unique solution exists. Some hypotheses may remain unresolved; some sets of requirements may be incompatible. A project can narrow or reject a proposal rather than fill every line with an unsupported answer.
The compact mantra makes the direction of justification easy to recall. Attention may first be drawn to any consequential answer, and inquiry can explore alternatives or develop answers together. Use and encompassing functioning nevertheless provide the basis for the inward and creation-side choices; changed knowledge returns to that basis when necessary. Use A.22.CGUS when the available continuations and their conditions need explicit treatment. Its ordinary branch makes those alternatives and unknowns clear; a formal CGUS claim additionally needs the structure and qualification that pattern defines. A teaching traversal of that structure still does not prescribe the order of Work.
When the connected account changes a provision decision, carry the result to the participants who can make it effective. Establish which work, means, access, authority and timing the chosen combination requires; obtain the needed decisions and support through their subject Methods. A named capable creator or an approved allocation does not by itself make a resource available. Follow actual provision, performance, the next receiver’s acceptance and later use separately. Reopen the premise contradicted by the returned result while retaining valid local closures.
Keep other project inquiries connected through their shared subjects and assumptions. A choice of creation Method affects capability and resource needs; an operational proposal can expose a capacity limit; a strategic change can reopen which result is worth obtaining. These inquiries do not all have the same purpose or one mandatory ordering. Carry a changed answer to the other inquiry only when it changes a premise used there. The result is one mutually intelligible account, not identical documents or one person deciding every question.
For the decision now being made, stop when the necessary answers and their relevant joint conditions are supported, or when the unresolved condition and its consequence are explicit. Make the resulting reasoning available in the project’s ordinary prose, drawing or table: what changed in the proposal, why, and what each affected participant, including yourself, needs to do next. When working on one creator-to-result connection, show how it reaches the common SoI; extend the inquiry only as far as the current decision needs. Preserve accepted local results whose grounds still hold. Continued project reasoning, later operation and further development can open new questions without making every completed local result unfinished.
A.1.STM:4.4 - Locate the first unsupported dependency
Use this narrower mode when the shared SoI and intended-use basis is already sufficient for the current question. It also helps name a precise next inquiry when one part of that basis remains disputed.
-
Choose by the result needed now. Name the decision or question and its connection to the common project SoI: for example, choosing a boundary, comparing constructions, obtaining a missing capability or deciding whether a result is ready for its next use. If a local result is current, say what it is about and what receiving work needs from it. If another long mantra better answers the local question, use it while retaining the shared SoI basis.
-
Place supported answers and the current scope. Keep the answers already available, their grounds and the conditions for using them together. Distinguish a prospective hypothesis from a fact and make an important unknown or disagreement visible. An ordinary explanation or existing project note is enough. Use the conditional network branch in section 3 only when that stronger claim is needed; the network is not project Work.
If the receiving question is whether a local case can be closed, state four things in ordinary language: the exact subject or claim; the bounded references and direct claims needed to answer this closure question; the separately governed closure basis; and one named downstream receiving use that remains outside the closed case. A.15.6 supplies any technical reference form that this question needs. A design inquiry can end with a supported proposal or a next inquiry without making a production-completion claim.
-
Find the first unsupported dependency. Work backward from the answer needed now to the missing, stale, disputed or unsupported answer that prevents the next justified move. First means first on that logical dependency, not earliest in the calendar.
-
Use the subject pattern. Obtain the missing answer through the Method whose
Use this whenfits the question. Retain the answer with its conditions, or the named stop. -
Return what the next use needs. Reconsider the affected combination using the returned answer. Individual answers can suffice. Select an E.18.NET network only with its independently identified members, obtaining relations, constraints, use frame and complete endpoint bindings. Select another A.22 structure only when one named use needs their organization and all four identity discriminators pass. Otherwise retain the direct plurality or Plain provisional map.
-
Follow the consequence and revise. For a proposal, test whether the answers could be used together under their stated assumptions. As work and use occur, follow the actual Work, production, identity, change and participation claims through their subject patterns, including each relevant builder branch. Bind evidence to the claim it supports. A missing direct link blocks the claim that needs it; preserve independent results and reopen the smallest affected earlier answer.
Four orders remain separate throughout: the order used to teach the map; the logical dependency read backward; planned or actual Work order; and the subject relations that obtain. One ordering establishes none of the others.
A.1.STM:5 - Worked uses
A.1.STM:5.1 - Common pump SoI, separate organizational contributions
The intended operating situation requires reliable water delivery at the user’s outlet. Start there and, from the pump boundary, examine the water-supply installation of which the pump is a part at that time. Explain how the pump, inlet supply, downstream path, power and control equipment work together to maintain delivery. Demand and the required continuity of that whole determine the pump’s needed flow and pressure under the stated conditions. “Water-delivery unit” names the sought system by that contribution. The claimed mechanism needs engineering grounds; the desired outlet result alone cannot establish it.
Suppose only the pump drawing and desired outlet flow are initially available. The team cannot yet derive the pump requirements from the installation’s functioning. It obtains the installation arrangement and operating information, identifies the other parts and checks how they cooperate to supply the outlet. If the missing fact concerns upstream storage or control, that becomes the next inquiry. A list of nearby pipes or the pump manufacturer’s name would leave this account unfinished. Once the required account is supported, the team can reuse it when comparing internal pump constructions.
In this constructed modernization case, the operator, controller supplier and maintenance organization have agreed their alteration, provision, qualification and continuing-use responsibilities. Those agreements organize their joint work as an extended enterprise. Their authorized representatives designate the existing PumpUnit-3 as its SoI for the selected use. A supplier offering a usable controller under its own bounded delivery obligations can also have the controller as its product SoI. A separate project to develop the test laboratory has the laboratory as its engineering subject, with pump qualification providing the use basis. The water-supply installation is relevant through composition and operation; the supplier and laboratory are relevant through creation and provision. A.1 recognition, project designation, any local system-role classification and any assignment remain separate questions.
With the use basis available, compare constructions such as variable-speed regulation or a pressure-regulated bypass, with their different energy, operating and maintenance conditions. Then reason backward to how each could be produced and qualified. These are proposals whose suitability must be investigated. The following inquiry concerns a construction with a controller and sensor; its test arrangement must fit that construction.
A.1.STM:5.1.1 - Locally plausible answers that do not fit together
Suppose a proposed pump assembly must meet a stated delivery condition after installation. A functioning argument assumes a calibrated sensor in the completed assembly. The construction encloses that sensor, the production Method closes the housing before the proposed calibration, and the available calibration instrument needs physical access that the closed housing does not provide. Each team’s answer may have worked in another configuration. Together, these particular answers leave the proposed qualification impossible as described. A common SoI and three signed local documents would not repair that incompatibility.
The team can now compare different whole proposals. It could change the housing to preserve calibration access, provided the changed construction still meets its operating requirements. It could propose calibration before closure, but then must establish why closure and installation would preserve the calibrated condition or how a later check can detect a consequential change. It could obtain another measurement arrangement, provided that arrangement can establish the required claim in the completed assembly and can actually be supplied. None is established merely by being imaginable.
The teaching explanation may run from required delivery through functioning, construction, production and calibration capability. The actual discovery began at a calibration question and returned to construction. A drawing, experiment or qualified measurement may supply the missing answer. If the team changes the housing, it reopens the affected operating and production assumptions; if it changes the instrument, it reopens the measurement and provision assumptions. It retains unaffected knowledge and restores agreement among the contributors whose decisions changed.
This case shows why the mantra must connect whole bodies of subject knowledge. Repeating “function, construction, method, creator” cannot supply the missing measurement argument. Conversely, a complete measurement argument for an inaccessible configuration cannot settle the project question. The connected account identifies what must be explained, which alternatives remain open, and where the answer will matter.
For the next project step, suppose the proposed housing can still be revised, but no alternative calibration instrument with demonstrated fit is available. The team chooses to investigate an access feature in the housing: the designer develops an option, the production specialist checks whether it can be made, and the calibration specialist checks whether it permits the required measurement. Their next result is a jointly supported option or a reason to return to the other repairs, not a claim that the pump is already qualified. If sealing or strength rules out the access feature, that result reopens the pre-closure calibration or alternative-instrument question. The operating requirement remains in force until those entitled to change it agree otherwise.
This also distinguishes a creator contribution from its performer. The chosen option may require housing redesign, manufacture and a calibration argument. Those descriptions guide the search for suitable people and equipment; naming a designer or assigning a laboratory does not establish their fit. If the measurement Method changes, compare its required access, range and conditions with the proposed laboratory and instrument again, then check that design, fabrication and calibration can obtain their shared inputs in time.
A.1.STM:5.1.2 - When actual production and use must be established
The design inquiry above can finish at its supported option. Later, an installation decision may ask whether the controller has actually been produced and is ready. Use A.15.PROD for the particular question: production participation, identity inception or completion. ControllerSubassembly-7 and other pre-existing materials can be continuing subjects of changes; the future controller is not transformed before it exists. Identify the actual controller under its applicable identity rule when it first exists, and assess completion or readiness separately. Recover any claimed dated fabrication Work through A.13 and A.15.1; F.6 is needed only for precise assignment-bound attribution.
For a closure claim about this controller-production case, state its subject, the claims and references needed for that question, and the applicable closure basis. The case closes only when the production, identity, completion or readiness claims required by its question are supported, including the required evidence and decisions, and its closure rule is satisfied. Installation and later operation in PumpUnit-3 remain the named receiving use outside this local closure. The ordinary positive branch of A.15.PROD:4.7 can return a readable answer or a precise gap; its stronger semantic or assurance branch opens when the receiving claim requires it.
If the project now needs a network of controller-production, pump-modification, qualification and operation flows, identify each member through E.18 and apply E.18.NET. Establish the actual production, installation, participation, use or feedback occurrences and their endpoint bindings; keep applied constraints and the use frame explicit. Until those conditions hold, retain the proposed network and its named missing link. A successful fabrication step does not provide a missing installation or feedback relation.
Follow actual facts from fabrication and changes of existing subjects through controller inception and pump modification to pump operation. For a runtime claim, keep the existing PumpUnit-3 and its functioning, causal, interaction or participation claim separate from an A.3.4 change of the identified continuing delivery-side environment or input referent. If dated runtime Work is also claimed, use A.13 and A.15.1 for that claim, adding F.6 only for precise assignment-bound attribution. The reliable-delivery hypothesis establishes neither actual claim. A failed relation or missing binding stops the dependent claim while preserving valid local results.
If later operation shows that reliable water delivery depends on an upstream reservoir-control assembly outside the proposed PumpUnit-3 boundary, the team reopens the outside-use, project designation and boundary hypotheses before revising the architecture and any network selection. Work already spent does not make the old boundary adequate.
A.1.STM:5.1.3 - Two products sharing one creator
A shared laboratory has agreed test commitments to the extended enterprises supplying water-supply pumps and irrigation pumps. Water-supply pumps face frequent starts; irrigation pumps run continuously. These product uses require different test conditions. The laboratory has eight available bench-hours tomorrow, with four promised to each product line. A water-supply failure now needs four additional diagnostic hours. Renaming that work a priority project would not supply twelve hours or settle the irrigation commitment.
The laboratory manager compares the consequences: delaying diagnosis blocks the water-supply commissioning decision; displacing the irrigation test delays its delivery. No qualified extra shift is available. A qualified external laboratory can perform the irrigation Method and return the required result before its deadline, including sample transport. Outsourcing is allowed for that result, and the manager has authority to buy it within a reserve that covers the confirmed price.
The manager obtains that commitment, informs the affected receivers and keeps the eight internal hours for the promised water-supply test and the additional diagnosis. Both product requirements and deadlines remain explicit. The decision is local because the manager’s delegated authority covers the changed provision and expenditure. Without a suitable external commitment or that authority, the manager would have to return the unresolved trade-off to those entitled to change the product commitments; calling the laboratory the SoI would not settle it.
This one-off allocation does not establish a case for permanent expansion. If expected demand justifies developing the laboratory, a temporary organizational project can provide a defined capacity for both test classes. Its acceptance can establish compatible Methods, equipment, qualified people, sample access, handovers and capacity limits. The project can then close before future pumps operate. The test report, the laboratory’s demonstrated capability and each pump’s fitness remain distinct results. An internal budget transfer provides means; it is neither external customer income nor evidence of product usefulness.
A.1.STM:5.2 - One-off service: a usable hairstyle
A client and a stylist first describe the intended use: the appearance the client seeks while moving through an event and later ordinary conditions, including possible rain. Starting at the proposed hair-and-fastener assembly’s boundary, they examine the larger physical whole in use: the client with the worn hairstyle, including its attachment and the bodily movements it must accommodate. They must establish the claimed composition and explain how those parts function together. If that account is missing, they investigate it before treating an internal arrangement as justified. The event and other people also matter through interaction and reception. They then compare arrangements of hair and fasteners, cutting and styling Methods, a capable stylist and suitable tools. The salon contributes through creation; it is not a containing whole of the worn hairstyle. Merely completing the hair operations would leave the purpose unmet if the result cannot survive the agreed use.
The embodied hairstyle is the proposed product System; the salon is a provider, the sketch is a description, and the appointment’s Work has its own boundary. A proposed SoI designation also leaves the extended enterprise to be established from agreements among the salon and other participating organizations. The appointment alone supplies no such organization; the service and design inquiry can continue while that designation remains open. Before the hairstyle exists, its designator belongs to the agreed description. For an actual system claim, A.1.SCR evaluates that exact proposed hair-and-fastener whole, its identity and physical organization; it does not substitute the client merely because the client is already a recognized System.
If the whole is established not to satisfy the System criterion, reject that System interpretation. If necessary facts are missing, leave recognition unresolved and name the missing basis. In either case, preserve the supported service and result claims; do not treat those claims as settling the project’s common SoI. The ordinary hairstyle name alone settles no systemhood question.
The sketch can be complete before styling; styling Work can end before the later use has been observed. Each local closure remains available at its own scope. A later failure under the agreed use conditions can reopen the design or service decision without making the earlier sketch an unfinished episteme or erasing the Work that happened.
A.1.STM:5.3 - Knowledge development with an epistemic result
An instrument manufacturer and research organization have agreed to develop a diagnostic installation for laboratories. Their extended enterprise has that installation as its product SoI, intended to distinguish two material failure mechanisms. A bounded research project investigates an explanatory model and produces an account of experiments; those results are epistemes. The shared systemic account connects model construction, test design and instrument changes to the diagnostic use. The argument and publication can reach their own acceptance before the installation is changed or the improved diagnosis is demonstrated.
This choice depends on the stated research purpose. A project seeking a theorem, historical explanation or openly reusable knowledge must not invent an arbitrary laboratory, reader or computer as its SoI merely to fill a position. Its epistemic result can be legitimate and locally complete.
For the diagnostic research, a supported finding that the proposed model cannot distinguish the mechanisms can finish the agreed inquiry and justify another approach; it does not establish improved diagnostic capability. If participants need a systemic account, they must still establish which system’s useful use supplies their common purpose and how knowledge development contributes to it. An unknown or contested receiving use leaves that systemic basis open without invalidating the separate epistemic result.
A.1.STM:5.4 - The same machine as product and means of production
A manufacturer proposes a cutting machine that does not yet exist. First describe its future use at the customer’s plant: which component transformations are needed, what the next operation must receive, and under which operating conditions. Look upward to the production cell in which the machine is intended to be installed and explain how its functioning depends on the machine’s contribution. These are proposed use and composition relations at the future operating time. The manufacturer’s organization is a creator, not that production cell.
The manufacturer, its contributing organizations and customer agree the work and fitness obligations for supplying that usable machine. In the extended enterprise established by those agreements, the machine is the SoI. The customer can supply the design and use requirements. Recover that use basis before comparing construction, manufacture and qualification, needed creator contributions and their provision. The control software, calibration rig and manufacturer organization are distinct local subjects. Work to develop the manufacturer has its own result and acceptance, judged by the agreed creator capability; the machine remains the product SoI.
The customer’s component-production work uses the machine as a means of production. In the extended enterprise organized to supply components for a receiving use, the components are the product SoIs. That use gives the construction and provision choices their reason. In work maintaining this capability, the machine is the local system-in-hand. Its repair can finish under its own acceptance conditions before another component is produced. Moving that repair to another contractor preserves both its finite completion and the component-use basis for providing it.
If the customer undertakes to supply refurbished machines to other users, recover those recipients and their use before comparing the refurbishment. Recover the agreements that organize the refurbisher, suppliers and receiving organizations into an extended enterprise; it can select the machine as its SoI too. Explain the resulting requirements and commitments rather than infer a new purpose from the object currently under inspection. Several products, users or linked projects can constrain one decision; use their actual relations instead of assigning them a single universal boundary.
A.1.STM:5.5 - Sustaining use and retiring a product
An operator, maintenance company and parts supplier agree to keep a pumping installation available at a specified capacity for the coming year. Their agreements organize the relevant joint work as an extended enterprise; the installation is its SoI. Each company retains its own boundary and other commitments. The maintenance company’s obligation can end at the agreed period and acceptance without changing the installation’s identity or making that company responsible for all later use.
Later, the operator and a removal company agree to withdraw the installation from service and leave the site in a specified condition. Recover this undertaking’s participants, decisions and commitments separately. The installation is the SoI of the retirement work while its identity persists; its removal, the end of its identity and acceptance of the site condition require their own grounds. Neither the maintenance contract nor completion of removal establishes those other facts.
A.1.STM:6 - Direct exits and near misses
| Current question | Leave through | Near miss blocked here |
|---|---|---|
| Is this exact existing entity a system? | A.1 and A.1.SCR | A noun, diagram box, plan, system-role label or assignment, or capability does not establish systemhood. |
| Which omitted Systems may undergo relevant changes that alter the current decision or investigation? | A.1.CSD | Use the current frame as a starting point for A.1.CSD’s bounded search; keep modal path claims distinct and add a separate actuality claim only when the direct predicate and its case conditions are supported. |
| Which system is the project’s SoI, and what is the current local subject? | A.15.6 for designation; section 4.1 here when the shared basis is unresolved | Distinguish the product role in an extended enterprise from local attention, the actual holder from a future description, and designation from agreement, classification and assignment. |
| What is promised, provided, connected, permitted, or stopped? | A.6.P §4.11a, then its subject pattern | Service or access does not select a system or one service bundle. |
| Which inside could support the outside use? | C.32.P2S and C.30 family | Architecture chosen before a stated outside-use hypothesis must return to that missing basis. |
| What actual runtime change and system participation obtain? | A.3.4 and the dynamics, interaction, causality, participation, assignment, Method, or Work pattern needed by the claim | An expected effect, required behaviour, observed output, or project designation proves neither an actual change nor an actor-side or Work claim. |
| What reusable way, performed occurrence, or actual change is current? | A.3.1, A.15.1, or A.3.4 | Method, Work, and Transformation are different objects and none proves the others. |
| Did production, identity inception, completion, or readiness occur? | A.15.PROD, A.15.5, and A.21 as applicable | A final visible step, result label, or DesignRunTag proves none of these claims. |
| Is this one TFS, an internal subflow, or a network? | E.18 and E.18.NET | A graph shape, shared entity, or creates label does not identify a network or relation. |
| Does evidence support this claim, and may a receiver rely on it? | A.10; B.3 only for a named assurance use | Evidence availability and assurance are not truth, actuality, or map completion. |
A.1.STM:7 - Recognition before relying on a system
Before relying on an acting system or changed-system boundary in the map, use an adequate available A.1 recognition result for that entity. Use A.1.SCR when a system-dependent question remains unresolved.
A.1.STM consumes only the returned recognition result. It does not repeat the six-component test, replace the exact entity with a convenient neighboring bearer, infer a system-role assignment from causal participation, or infer Method, Work, transformation, promise, permission, project designation, or a system-role kind from systemhood.
A.1.STM:8 - Conformance checklist
| ID | Check |
|---|---|
CC-A1-STM-1 | Participants can recover each product SoI, its actual or proposed extended enterprise, the participating organizations’ agreements, agents’ objectives and the intended use or withdrawal from use. Bounded creation, change, sustaining in use and retirement retain their own commitments and acceptance. Local project subjects and results retain their identities and acceptance bases. In the narrower gap-finding mode, the result needed now and first unsupported dependency are readable without a technical record. |
CC-A1-STM-2 | At the operating time, reasoning moves from the system boundary upward to the larger functioning whole and the joint action of its parts, through the levels and supported inclusions that affect the decision. This account grounds the required function before inward construction and backward creation/provision reasoning. An unknown whole remains an inquiry; adequate earlier reasoning can be reused. Transformation-flow and part–whole directions stay distinct. A proposed future use retains its assumptions; actual changes and participation require their own grounds. |
CC-A1-STM-3 | Project SoI, current subject, required behaviour, system named by its function, selected construction and proposed or actual system remain distinguishable where they change the decision. Functional classification alone does not establish an A.2 system-role kind or an assignment. Creator contributions and the fit of concrete performers are considered separately. |
CC-A1-STM-4 | Project Work, an admitted project-level network selection or Plain provisional map, and one minimal case placement retain their own identities. |
CC-A1-STM-5 | The point where attention starts is connected to the order of project justification. A noticed difficulty and proactive use of the mantra can reach the same consequential question; an independent non-project inquiry keeps its own scope. Inquiry returns, Work order and obtaining subject relations retain their different meanings. |
CC-A1-STM-6 | Each local answer states the claims and conditions needed by its receiving use, retaining the subject predicates that govern those claims and any unresolved stop. A cited pattern locates the governing content. |
CC-A1-STM-7 | When a local closure claim is needed, the case states four things in ordinary language: the exact subject or claim; the bounded references and direct claims needed to answer this closure question; the separately governed closure basis; and one named downstream receiving use that remains outside the closed case. Ordinary design inquiry keeps its question, supported answers, joint conditions and next useful action without requiring that closure claim. |
CC-A1-STM-8 | An admitted network has independently identified members, exact obtaining cross-member relations, applied constraints, a use frame, and complete endpoint bindings; otherwise that network proposal stays provisional. A shared systemic account does not by itself require this stronger claim. |
CC-A1-STM-9 | Expected environmental effect, actual runtime transformation and system participation, production, identity inception, completion, later change, and use are separately grounded; required behaviour is not actuality, and no not-yet-existing system is transformed. |
CC-A1-STM-10 | Evidence is bound to its claim, assurance is limited to a named reliance use, and changed grounds reopen only the smallest affected answer. |
CC-A1-STM-11 | The account explains why the chosen answers can be used together under their actual shared conditions; it does not combine locally supported answers from incompatible variants. |
CC-A1-STM-12 | The reader can follow a consequential change to the answers it affects, distinguish possible repairs and their conditions, and recover the difference between the teaching unfolding and performed Work. |
CC-A1-STM-13 | Organizational work connects product use, needed creator capability and a finite locally accepted result under section 4.1.1. Resource choices and acceptance use that connection, including affected products, real provision and decision rights. Remaining uncertainty, research acceptance and later product-use evidence retain their own scope. A new contract or sale of the organization does not replace the product SoI. |
A.1.STM:9 - Common anti-patterns
| Anti-pattern | Repair |
|---|---|
| Mantra as fixed work sequence | Use its connected questions to construct and criticize hypotheses; use direct patterns for local truth and WorkPlan for planned order. |
| Correct parts, unsupported whole | Recover the conditions under which the particular answers can be used together; revise the failed connection or candidate rather than counting completed questions. |
| Short formula replaces knowledge | Return to the developed subject explanation and bring its premises and limits into the common account. |
| A new contract hides an unchanged purpose | For the same organizational work, retain the product use, creator capability and finite local acceptance under section 4.1.1. A new product supply needs its own usable result, recipients and fitness obligations; a new budget or contractor does not provide them. |
| Role becomes an intrinsic system type | Separate the SoI role from its holder and description; test the actual System under A.1 and any technical role claim under A.2/A.2.1. |
| Project equals network | Keep actual project as composite U.Work and E.18.NET as a selected non-agentive U.Structure. |
| Case equals subnetwork | Keep the local question and its receiving use clear. Recover the closure basis when closure is at issue; select a structure only when one receiving use needs the whole organization. |
| Creator graph import | Explain the required creator contributions and their relations. When a TFS network is claimed, identify its members and obtaining cross-member occurrences; an arrow adds no creator kind or generic creates relation. |
| Shared entity as edge | Name the directly governed production, inception, participation, use, feedback, or other occurrence and bind its participants. |
| Architecture or provision chosen before its use basis | Recover receiving changes and the joint functioning of the containing whole at the operating time, then derive the system’s contribution and justify inward and creation-side choices. |
| Environment description substitutes for the upward move | Identify the larger functioning whole and the system’s part relation; when either is unknown, investigate it and retain the resulting limit on the dependent design judgement. |
| Maker treated as suprasystem | Recover the creation or provision relation; use a containing-system claim only where the product is actually or prospectively a proper part at the stated time. |
| Intended system acts | Keep it in plan or description content until identity inception; only an existing admitted system can perform Work. |
| Systemhood proves Work | Test causal participation, system-role assignment, Method, Work, and transformation separately. |
A.1.STM:10 - Consequences
Benefits. Participants can justify local choices by the relevant SoIs and receiving uses, expose incompatible understandings, and preserve those connections while developing builders and other enabling systems. The mantra prompts examination of consequential dependencies before a complaint arises; the developed account connects an already noticed difficulty to the same reasoning. The narrower mode locates a missing dependency without requiring the whole account to be rebuilt.
Costs. Establishing usable project designations and agreements can require domain inquiry, negotiation and experiments. Keeping local subjects, prospective dependencies and actual outcomes distinct adds work, especially across organizations and future product variants.
Limits. This pattern supplies the common systemic reasoning and its return paths. It does not guarantee a correct SoI choice or settled agreement, and does not independently identify a System, admit Work or transformation, close a case, identify a TFS network, or establish evidence or assurance. A local result can be complete while the common system basis or a downstream use remains open.
A.1.STM:11 - SoTA-Echoing
Informative. These source contributions inform use of the long attention map. The named subject patterns remain authoritative for kinds, relations, participants, and pass conditions.
| Source | Contribution to the pattern | A.1.STM use and boundary |
|---|---|---|
Levenchuk, Systems Thinking (R5; source manuscript SystemsThinking2026_guide_with_assignments_27nov25.docx), “System-thinking mantra”; Systems Modeling (R6; source manuscript SystemsModeling2026_guide_with_assignments_27nov25.docx), “System-of-interest and collective systems thinking”, “The system-of-interest depends on who seeks it”, and “Hair-salon example as a service provider” | A common SoI sustains collective reasoning across division of labour. R5, “Variants of the systems approach”, and R6, the black-box and pump-assembly discussion, require moving from the system boundary upward to larger functioning wholes before considering its parts. The source moves from the needed outside change and that encompassing functioning to behaviour, the system named by its function, possible constructions, ways of obtaining them, creator contributions and suitable concrete creators. It calls for written reasoning on a project, consequential changes and actions, iteration and bounded recurrence. | Sections 3–4 retain these operations under current FPF distinctions. A functional classification is not automatically an assignable system-role kind; a description is not an actual holder, and creation is not composition. The source’s physical-role ontology and broad function/Method/service equivalences are not adopted. Its accounts of learning and success are not independent evidence that this pattern improves either. |
| Levenchuk, R5, “The temptation of complexity”; R6, the creator, tool and provider discussion in “Common errors”; R8, Systems Engineering (2025 manuscript), use/construction/business-case discussion; R10, Systems Management (2023 manuscript), organization, system-of-interest and investor concerns | The managerial attention problem connects the creator’s design and provision to the products’ useful use. The corpus also calls a company the target system in investor discussions, while its management argument warns against replacing the product with its creator. | Adapt as a deliberate attention rule. In organizational work, sections 4.1–4.3 retain the products as SoIs and give the creator its full engineering subject, capability grounds and finite acceptance. This selects a consistent practical norm from heterogeneous source usage; it is not a claim that organizations cannot be Systems, engineered or sold. The account supplies a way to examine decisions, not demonstrated psychological, commercial or learning success. |
Levenchuk, Methodology for Engineers and Managers (R7; source manuscript Methodology2025_guide_with_assignments_22apr25.docx), the system-mantra passage in “Life cycle 2.0: from work stages to development methods” and “Creator graph” | Creator graphs connect a builder’s period of use with work that creates or develops another system, and include both enterprises and simple tools. | The recursive step in 4.3 preserves this connection; actual production, participation, performer and Work claims keep their respective FPF predicates. |
| Levenchuk, “Organizational-development mantras”, 13 March 2025; Checklists/canvases/“systems of equations”/mantras/plots for organizational development, slide-deck edition dated 15 May 2025 on its cover, slide 12 | The article explains that mantras retain a logical direction while inquiry is continuously refined; its short system-thinking mantra connects intended value, construction, ways of obtaining it, capable contributors and their cooperation. Slide 12 explains the equation analogy: answers constrain one another across several mantras and creator systems, and changes in the situation require revisiting their joint fit. | Section 4.3.1 adapts this account into an FPF method for assembling and revising a jointly workable account across connected inquiries. The teaching order remains distinct from actual inquiry and Work. FPF uses the equation analogy for mutual constraints; it does not adopt the source’s restriction of mantra answers to types or claim a universal solver. The source’s fixed ordering of particular improvement priorities is not generalized here. |
| E.18 and E.18.NET | Build-the-builder reasoning must consider operation, production, identity inception, later change, feedback, and builder branches together, while independently identifying the TFS or nested-network members and relations behind any diagram. | The conditional network branch in section 3, section 4.4 and the production continuation in 5.1.2 require exact cross-member occurrences and endpoint bindings when that network claim is needed. Shared identity, a creates label, or temporal adjacency does not admit a network or connect two members. |
| A.15.6, E.18, and E.18.NET | A project team needs both the longer project dependency and a bounded local concern, with separate claims for project Work, network selection, case subject, closure, and later use. | When closure is the receiving question, section 4.4 step 2 and section 5.1.2 name the exact subject or claim, only the references and direct claims needed now, a separately governed closure basis, and one downstream receiving use that remains outside the closed case. Project-level reasoning may continue to that later use without reopening the closed case. |
| Deutsch, Constructor Theory, arXiv:1210.7439v1 (2012), §1.1, pp. 1–4, read with current A.3.4, A.15.PROD, and E.18 | Possible production or change depends on substrate attributes and constructor conditions. | The conditional actual-relations branch in section 3, forward trace and section 5.1.2 distinguish one continuing changed referent, production participation, identity inception, later use and system-side participation. Do not infer actual production or change from a requirement, Method, or Work alone. A not-yet-existing system is not transformed. |
The combination used by this attention map is an FPF synthesis.
A.1.STM:12 - Rationale
The account of the product’s role in the extended enterprise and its use makes division of labour intelligible: it lets a participant explain why a local choice matters to people outside that task. The larger whole’s functioning at the operating time explains what contribution the system must make together with the other parts of that whole. Requirements derived from that account constrain plausible internal construction; construction constrains the Methods and capabilities needed to obtain it. Merely naming neighbours or desired effects leaves the reason for those requirements incomplete. These dependencies explain the mantra’s order. A complaint can lead back to the same grounds, while proactive examination can reveal an unanswered question before its consequences are felt. Criticism and experience explain the returns.
The same reasoning applies recursively to builders without making creation a composition relation or every builder a Work performer. Separating the product role in an extended enterprise from System identity preserves this organizing principle across different projects and before a holder exists. Separating local completion from receiving use lets a team finish bounded work without mistaking that completion for success of the whole undertaking.
A.1.STM:13 - Relations
- Builds on: the Plain long/local boundary in the Architectural Reference;
A.1andA.1.SCRfor system recognition; andA.15.6for project SoI designation and local-subject recovery, actual project Work, and subject- or claim-centred case recovery. - Coordinates with:
B.5.PIfor the general use of a suitable mantra to initiate inquiry before a difficulty is recognized.C.22.2when a signal or a question found through the mantra needs a reviewable problem-side account.A.14for relied-on part–whole relations.C.30.STRATfor unresolved level wording.C.32.P2Sand the C.30 family for outside-use-to-architecture reasoning.A.3.4and the patterns for dynamics, interaction, causality, participation, assignment, Method, and Work claims in runtime change and system participation.A.2andA.2.1for system-role-kind interpretation and assignment.A.3.1,A.12, the A.15 family,A.15.PROD,A.15.5, andA.21for Method, Work, production, identity, readiness, and gates.E.18andE.18.NETfor TFS and project-level network selection.A.15.6for the minimal case recovery and closure boundary.A.10andB.3for evidence and assurance.A.1.CSDwhen the missing answer is which other Systems may undergo relevant changes.C.28only for actual causal-use claims.
- Logical unfolding and continuation:
A.22.CGUSsupplies the account of alternatives and conditions when the reasoning structure’s continuations matter, and qualification for a formal CGUS or its demonstrative slice. The reminder, developed explanation, described structure and actual Work remain distinct. Ordinary use requires no new F.17 row, durable card or registration. - Does not replace: any direct pattern named above. A.1.STM connects their results to a shared systemic project account and returns each result or stop to the attention map; it defines no additional world-side predicate.