HCD.8:0.1 - Working Terms
| Name in this pattern | What it denotes |
|---|---|
| missing development contribution | The exact provider, assessment, environment, access, coordination, or support result that an HCD.7 arrangement needs but cannot currently obtain under its required conditions. |
| provider target task | The concrete work a provider must perform to supply that contribution, including recipient, input, output, criteria, protected errors, support, timing, and authority. It is different from the learner’s later-Work target. |
| obtain route | Use of an already capable and available provider or environment after its fit and operation for this contribution have been checked. |
| build route | Preparation or change intended to make a person, group, organization, tool, or environment able to supply the missing contribution. Each direct owner retains its own correctness and authorization decisions. |
| operating test | A representative enactment in which the intended provider or environment supplies the exact contribution under material service conditions, with observable criteria, timing, handoffs, and failure signals. |
| blocking dependency | A missing provider or enabling result without which the current build cannot produce or operate the required contribution. |
| recursive build question | The same bounded question applied to a blocking dependency: what exact result is missing, should it be obtained or built, and what operating evidence would close it? |
| bounded operating development arrangement | The tested provider or environment contribution, its dependencies, access, capacity, authority, evidence, fallback, limits, and continuation into HCD.7. It establishes neither learner participation nor learning effect. |
Recursion here is a finite search for the first unsupported provider or enabling result. It is not a generic claim that one capability creates another, a fixed hierarchy of teachers, or a reason to model every participant and tool.