Jump to text
On this page
Copy and source
Published source confirmed at last check

Source changed 2026-11-18 21:11:39 UTC · snapshot created 2026-11-18 21:12:35 UTC · last check 2026-11-18 22:30:10 UTC

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:

ExpressionWhat it selectsPractical 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 systemWhatever 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 functioningThe 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 functionThe 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.

  1. 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.
  2. 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.
  3. 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.
  4. 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.
  5. 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.

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

  6. 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.

  7. 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.

  1. 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.

  2. 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.

  3. 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.

  4. Use the subject pattern. Obtain the missing answer through the Method whose Use this when fits the question. Retain the answer with its conditions, or the named stop.

  5. 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.

  6. 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.