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

Source changed 2026-11-16 21:18:08 UTC · snapshot created 2026-11-16 21:19:40 UTC · last check 2026-11-17 19:55:19 UTC

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.