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 20:05:03 UTC

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.