HCD.8:4.4 - Expose Only Blocking Dependencies
Read backward from the missing contribution to the first unsupported dependency. A teacher may need a calibrated answer key from a domain specialist; the specialist may need an approved test result; the practice environment may need an isolated data set and a reset function. Ask for the direct result that closes that dependency.
Use A.1.STM’s plain long-mantra map when the builder chain is not yet established: keep the final contribution visible, name supported answers, and stop at the first missing one. Use E.18.NET only when the current question truly needs independently identified transformation-flow structures and exact cross-boundary relation occurrences. A diagram, shared resource, calendar sequence, or word such as “creates” or “enables” does not establish that network.
Stop recursion when:
- an already qualified and available contribution satisfies the dependency;
- a direct owner returns the required result under compatible conditions;
- the current build can proceed without the optional dependency; or
- an exact unsupported dependency, owner, consequence, and retry condition have been returned.
Do not build a provider because that provider appears in the dependency map. Build only a missing result whose absence blocks the selected operating contribution.