DOCA.5 - Qualify Development-Direction Dependencies and Bound Joint Reachability
Type: DPF pattern
Status: Released; evolving
Normativity: Normative unless marked informative.
DOCA.5:1 - Problem Frame
Use this when a development direction looks worthwhile, but it is not yet clear that its necessary changes, resources, support, and permissions can hold together for this subject and horizon. The warning sign is “each step is possible” without an answer to “can these steps work together here?”
Start with the proposed direction and name the condition most likely to defeat its reachability. Inspect the existing result for that condition, then check how it interacts with the other necessary conditions. The first useful result is a bounded reachability claim, a conditional direction with an exact missing premise, or rejection of the affected transition.
This is the joint-qualification question within development-opportunity construction or development-direction advising. Reachability means that the proposed transition is supported as possible under stated conditions; it is not an observed effect, a recommendation, or permission to perform it. A person exploring their own direction can use this pattern without an adviser.
Ordinary non-use boundary. Reuse an adequate current reachability account when only retention, recommendation, choice, or execution remains. Enter directly from adequate direction descriptions; no earlier DOCA pass is compulsory. If the change itself is unspecified, return that gap to DOCA.4 or the practice constructing it. If a domain practice already owns the complete feasibility question, request or reuse its result rather than building a second feasibility model here.
DOCA.5:2 - Problem
Necessary conditions can be credible separately and incompatible together. Two directions consume the same scarce specialist hours. Access exists for one environment but not the proposed receiving use. A later step requires a capability that an earlier step merely hopes to develop. A nominally reversible trial creates an irreversible disclosure or leaves continuing maintenance.
A checklist of obtained premises can therefore give false confidence. It can also cause needless exclusion: one unavailable route is mistaken for an impossible contribution, or one missing premise makes an otherwise independent direction disappear.
The practitioner needs to determine which combination is supported, which claim remains conditional, and exactly where new evidence or a revised configuration would change the answer.
DOCA.5:3 - Forces
| Force | Tension |
|---|---|
| Separate and joint support | Individually qualified transitions may compete, interfere, or rely on the same uncertain source. |
| Opportunity and assurance | A useful possibility can be retained before all premises are qualified, but it must not be presented as reachable now. |
| Missing and negative evidence | An unknown condition calls for qualification; a ruled-out condition calls for rejection or revision of the affected route. |
| Apparent simplicity | A small change may require substantial transition Work, scarce access, or irreversible exposure. |
| Holder specificity | Human, organizational, AI, and engineered-system premises come from different practices and do not transfer by analogy. |
| Effort and consequence | A short account can settle an ordinary conflict; a high-consequence feasibility claim may require substantial domain assurance. |
DOCA.5:4 - Solution
Qualify the necessary conditions together for one named transition or combination. Keep the work proportional to the claim that someone will rely on; do not turn every possible dependency into a new investigation.
DOCA.5:4.1 - Bind the claim before testing its dependencies
Name the identified subject, receiving use, actual or currently relied-on starting configuration, proposed finite change, candidate configuration, horizon, and protected conditions. Recover an adequate direction/support description when one exists. For a path, name the particular step and the starting configuration it inherits.
State the claim being qualified: one direction alone, several directions together, a sequence, or one branch under a stated contingency. Those are different claims. “A or B is available” does not establish “A and B can both be realized,” and two separately possible endpoints do not establish a possible transition between them.
Select dependencies by consequence. Ask what absence or failure would block the proposed transition, breach a protection, or materially change its contribution. Include dependencies on capability, access, evidence, acceptance, support, time, resources, authority, and continuing Work only where they affect this claim. An unstated material dependency is a gap, not a satisfied condition.
DOCA.5:4.2 - Use the supplying practice’s qualified result
For each material dependency, state the required result and why it matters to this transition. Use A.15.9 — Request and Use a Bounded Result from Another Practice to inspect an existing result and use it at its supported strength for this receiving question. Retain a conditional direction where the needed premise is absent. Select a further request through A.15.9 and C.11.DUA only when its obtainable contribution warrants formulation, qualification, performance, delivery, interpretation, delay, and displaced work.
A provider’s offer, a published MethodDescription, and a qualified result about this subject answer different questions. Recover the result’s subject and configuration, characteristic or condition, receiving use, evidence window, limitations, and uncertainty. If new Work is needed, the supplying practice retains its Method, competent performer, authority, and conclusion. Assess evidence-bearing reliance through the applicable A.10 result; a citation alone does not qualify the premise.
Use ordinary wording that preserves the difference between supported, conditional, unknown, and ruled out. Keep these distinctions at the claim they affect. If authorized access is absent, an access-dependent route cannot be described as available. That fact need not defeat a contribution obtainable without that access.
An existing result for another holder or configuration is not automatically a result for this one. Use the direct practice’s qualified transfer basis, covering the receiving bearer and configuration, characteristic meaning and scale, intended use, evidence window, and uncertainty as required by DOCA.1.CHR. Otherwise leave the receiving premise unknown.
DOCA.5:4.3 - Test the combination, not just its ingredients
Put jointly necessary conditions on one compatible basis. Recover the relevant time intervals, resource quantities, operating and transition demands, availability restrictions, and protection limits. Do not add estimates from incompatible scenarios or treat the same resource as available twice.
Ask which conditions compete, complement, substitute for, or interfere with one another. Inspect common causes and shared suppliers, thresholds, congestion, delays, continuing obligations, and evidence dependencies where they can change the result. Two claims derived from the same unqualified assumption do not independently support the combination.
For a sequence, check whether the earlier transition can establish the next step’s starting conditions within the declared horizon. A planned learning result remains a condition on the later step until the relevant human-development evidence supports it. A later resource estimate must include continuing demands inherited from earlier steps. For alternatives, preserve their separate bases: a conflict between them may rule out simultaneous realization without ruling out either alone.
Use the direct domain analysis when the joint question needs scheduling, engineering, safety, organizational allocation, finance, or another specialized result. An ordinary arithmetic conflict can be stated directly when the underlying quantities and limits are qualified. Do not infer independence, additivity, or a probability of completion from the shape of a dependency diagram.
DOCA.5:4.4 - Include transition burden, recovery, and future options
Check what must happen to move from the starting configuration to the candidate, not just what could hold after arrival. Include material setup, learning, migration, evaluation, coordination, temporary loss of service, and continuing support. Distinguish the resources needed to find out whether a transition is possible from those needed to realize it.
When comparing the finite change’s contribution, use C.11.CRC: actual or relied-on starting configuration, finite change, candidate configuration, common horizon and scenarios, and the complete relevant result, resource, affected-System/distributional, and protected coordinates. Each coordinate keeps its declared scale and polarity. A gain in the intended result does not cancel a protected loss or establish Pareto improvement.
Name what reversal would require and what it would not restore. Removing a tool may restore the earlier operating arrangement while leaving setup time spent, information disclosed, or a supplier relationship changed. State whether the transition opens, preserves, closes, or delays a later option, and which part of that claim is evidenced or conditional.
A proposed probe is itself a finite change when it consumes resources, exposes people or data, or changes later possibilities. Return its question and missing feasibility or authority result before treating it as an admissible recommendation or performed Work.
DOCA.5:4.5 - Return the strongest supported reachability claim
Write the result at the smallest affected scope.
| What the qualification establishes | Useful return |
|---|---|
| Necessary transitions and their joint limits are supported for this subject, configuration, use, and horizon | State bounded reachability, the supporting conditions, residual uncertainty, and the event that would reopen it. |
| A material premise is still missing but the candidate is specified well enough to qualify | Retain a conditional opportunity; name the exact claim withheld, supplying practice, and result that could support or defeat it. |
| A qualified constraint defeats the proposed transition or combination | Reject that route for the stated use, or construct a revised candidate; retain independently supported alternatives. |
| The starting condition, finite change, or jointly necessary conditions are too unclear to test | Return an unresolved candidate and the missing description or evidence, without asserting reachability or impossibility. |
“Conditional” is useful only when the condition changes the result. State what a positive and a negative answer would do. Do not retain a known-infeasible direction as merely awaiting more evidence, or call an unanswered question a negative result.
An ordinary return can be two sentences:
Each support direction can operate alone during the eight-week inquiry, but both require the same engineer for two hours each week and only two hours are available. The joint direction is ruled out under the no-overtime protection; retain the separate candidates, and qualify a shared-support configuration only if its actual combined demand could change that result.
This return need not become a large dependency register. Expand it when several recipients, delayed reuse, disagreement, or consequence makes the basis hard to recover.
Recognition and assurance. A reader can recognize a usable account from the named transition, joint limits, qualified or missing premises, and bounded return. Trust in the reachability claim requires the relevant domain evidence and uncertainty assessment; high-consequence use retains its additional safety, authority, and assurance requirements. A clear account makes those requirements visible without satisfying them by description.
DOCA.5:4.6 - Return to the next actual use
Supply the qualified direction or exact gap to the current inquiry. DOCA.6 may retain the candidate or reconstruct its path; DOCA.7 bounds an actual advising engagement, and PSD supplies decision-support results when recommendation is requested. HCD, organization, AI, engineering, operations, and other direct practices retain programme construction, allocation, realization, and evidence.
Reopen only the affected claim when its subject, starting configuration, use, horizon, resource, support, permission, protection, or evidence changes. Use DOCA.8 to trace that change through dependent opportunities and advice. Preserve an unchanged independent result.
DOCA.5:5 - Archetypal Grounding
DOCA.5:5.1 - Two feasible support directions cannot share the same hours
Consider a constructed engineering-organization case. Two departments want better acceptance preparation during an eight-week period. The current arrangement is manual review. Candidate A supports one department with a qualified reviewer; candidate B supports the other with the same specialist. The following are stipulated case premises, not reported field evidence.
The relevant practice has qualified each direction separately for its own use. Each needs two specialist hours every week for all eight weeks. The organization has confirmed only two hours per week for this inquiry, after existing obligations. The protected condition is no overtime or loss of urgent operating cover. Setup and the remaining dependencies are covered in each separate qualification.
| Claim | Joint test and result |
|---|---|
| A alone | Its two weekly hours fit the qualified availability; retain its bounded individual reachability. |
| B alone | Its two weekly hours fit the same availability when A is absent; retain its bounded individual reachability. |
| A and B together | Four hours are required in each overlapping week, against two available; the combination is ruled out for this horizon and protection. |
| A followed by B | Both need eight weeks, so moving B after A does not fit the original eight-week horizon. A longer horizon would be a revised claim requiring its own availability and continuing-demand basis. |
| Shared support for A and B | “The specialist can cover both at once” is an unqualified new configuration, not a consequence of the individual results. |
The useful answer is not “development is impossible.” Both separate directions remain candidates. The organization can request the exact combined-work estimate for a genuinely shared-support configuration, examine another provider, or later consider a different horizon. Those possibilities require their own qualification. Choosing between A and B remains a separate decision.
DOCA.5:5.2 - Mira needs a transfer premise, not another label
In this constructed case, Mira, an engineer-manager, is exploring better review contributions over four months. A human-development result identifies what she can already do under specified support. A separate access inquiry finds that some representative examples are unavailable. A small recovery test shows improved performance with permitted examples and feedback.
Those results answer different questions. A capability envelope bounds current performance conditions; an access/expression differential concerns whether a capability can be expressed under changed conditions; a particular recovery test concerns that tested recovery. None alone establishes learning transfer to later independent review or selects an intervention.
If the direction requires independent later review, retain it conditionally while HCD supplies the result about feasible development, practice, feedback, and transfer for Mira’s intended use. If a different direction requires continuing specialist support, qualify that arrangement on its own basis. Do not silently replace independent capability with supported performance.
The exact return might be: “Supported review with the permitted examples is evidenced within the tested conditions. Independent transfer in the intended work remains unknown; this blocks the independent-review claim, not the supported route or the usefulness of the receiving problem.”
DOCA.5:5.3 - Data access does not complete an AI reachability claim
In this constructed case, a team has a model benchmark result and permission to inspect a small data sample. Its proposed direction is a retrieval-assisted review arrangement using a different configuration and representative operational data.
The benchmark does not establish the receiving configuration’s performance. Sample inspection does not establish permission for operational processing, continuing data access, evaluation coverage, or adequate human oversight. Use the AI, data-governance, and operating practices’ specific results through A.15.9. Until the required transfer and support results exist, retain the arrangement as conditional.
If the qualified data result excludes that operational use, reject the access-dependent route for that use. Preserve a permitted manual route when its evidence is independent. A population or lineage can likewise be the subject of a scientist’s reachability hypothesis, but it is not thereby an advice recipient or authorized chooser; a proposed intervention remains the scientist’s or organization’s separately governed case.
DOCA.5:6 - Bias-Annotation
Optimism favors possible endpoints and hides the transition. Availability bias favors the one provider already known. Schedule and resource arithmetic can look precise while using unqualified quantities. Success in a supported test can be overread as independent capability or general transfer.
Ask which condition would defeat the combination, whose burden is missing, and whether two premises share the same unsupported source. Keep qualified contradiction, uncertainty, and absence of evidence different. These checks expose assumptions; domain evidence still determines the reachability claim.
DOCA.5:7 - Conformance Checklist
- MUST bind the subject, receiving use, starting configuration, finite change, candidate configuration, horizon, and protected conditions.
- MUST state whether the claim concerns one direction, a joint combination, a sequence, or a conditional branch.
- MUST qualify material external premises through A.15.9 and preserve their supplying practice, use limits, currentness, and uncertainty.
- MUST test shared resources, timing, interactions, and inherited obligations where they can change joint reachability.
- MUST include material transition burden, reversibility, and supported or conditional option effects.
- MUST preserve C.11.CRC’s complete coordinate basis when asserting finite contribution or dominance relations.
- MUST distinguish supported reachability, a conditional opportunity, a ruled-out transition, and an unresolved candidate.
- MUST localize a missing or defeated premise and retain unaffected independent alternatives.
- MUST NOT infer holder transfer, learning, capability, authority, observed effect, or choice from a label, source description, benchmark, or reachability account.
- SHOULD use a short result when the claim and its decisive limits are readily recoverable.
DOCA.5:8 - Common Anti-Patterns and How to Avoid Them
| Anti-pattern | Why it fails | Repair |
|---|---|---|
| Every box is feasible, so the chain is feasible | Boxes may consume the same resource or fail to establish the next starting condition. | Qualify the joint transition on one timing and resource basis. |
| Missing evidence means impossible | An unanswered premise is treated as a negative result. | Return the exact conditional claim and qualifying question. |
| Known conflict remains “conditional” | A ruled-out combination keeps circulating as if confirmation alone could rescue it. | Reject or revise the affected configuration explicitly. |
| Delay one step and the conflict disappears | Earlier steps may leave continuing demands, and the original horizon may no longer fit. | Reconstruct the later starting configuration and joint limits. |
| A test proves development | Supported recovery or benchmark success is treated as transferable capability. | Return to the holder practice for the exact development or transfer result. |
| Reachable means authorized | Feasibility is used as permission or recommendation. | Keep the choice, mandate, probe exposure, and execution result separate. |
DOCA.5:9 - Consequences
Practitioners can stop making whole-direction claims from isolated premises. A conflict can narrow one combination while leaving useful alternatives intact. A selected worthwhile request becomes specific enough for the supplying practice to answer, while a useful conditional result can finish without one.
The cost is recovering compatible conditions and exposing burdens that a direction label omitted. Some candidates remain conditional, and a high-consequence claim may require specialist analysis. This pattern reduces neither that assurance obligation nor the uncertainty of an unperformed transition.
DOCA.5:10 - Rationale
Reachability depends on conditions holding together, not merely being individually conceivable. Binding the claim first makes both rejection and retention more precise: evidence can defeat one combination without defeating every use of the contribution.
Separating the qualification of each premise from the joint test also makes work reusable. A current access, capability, or support result can serve several candidates, while each candidate still needs its own compatible combination and transition basis.
DOCA.5:11 - SoTA-Echoing
Practice question. How can a practitioner qualify a development direction’s joint reachability without mistaking individually credible ingredients for a realizable combination?
Best-known line for this use. Reuse holder-qualified results, then test their finite configuration and joint constraints. This pattern adopts A.15.9’s single result-acquisition method in :4.2 and adapts C.11.CRC’s finite-change, interaction, transition, and option-effect analysis in :4.3–:4.4. The supplying domain retains the feasibility model and evidence. This division makes the relevant resource conflict visible without requiring a second domain investigation.
Serious alternatives and trade-off. A list of separately qualified premises is cheaper to maintain, but in the eight-week case it admits a combination that requires twice the available support. At comparable reading effort, the joint row reveals the decisive conflict. A complete domain schedule or feasibility analysis is the stronger direct alternative when the question is already an implementation problem and its conditions are stable; reuse that result. For an early opportunity inquiry, constructing such a model for every candidate can cost more than the bounded rejection or exact gap requires. This is a proportionality judgement, not a measured efficiency result.
AI-specific source return. The current NIST AI RMF Playbook, MAP 1.1 and MAP 4.1 is an answer-bearing source for mapping receiving context, non-AI alternatives, third-party components, and continuing support risks. This pattern adapts that line in :4.2 and :5.3: a model result and data access are ingredients whose receiving-use limits still matter. Its AI risk guidance does not supply the missing client results or establish a common human/AI development mechanism.
Limits and reopen. The cases are constructed demonstrations, not evidence of intervention success. Reopen the affected move when domain practice supplies a less burdensome account preserving the same joint constraints and protections, a real use reveals a missed interaction, or a relied-on holder, configuration, evidence, or source meaning changes.
DOCA.5:12 - Relations
- Receives from DOCA.1, DOCA.1.CHR, and DOCA.4: the inquiry, relevant characterization, and direction/support candidates; adequate direct inputs suffice.
- Uses A.15.9: the single method for obtaining and qualifying a bounded external result; source reliance retains its applicable A.10 qualification.
- Uses C.11.CRC: finite configuration-relative contribution, complete coordinates, constraints, interactions, transition burden, reversibility, and option effects.
- Returns to holder and domain practices: capability, access, support, transfer, feasibility, safety, authority, allocation, and realization results.
- Supplies DOCA.6: bounded reachability, conditional or rejected combinations, and the exact gaps that change retained paths.
- Supplies DOCA.7 and PSD: qualified premises or localized blockers for a bounded advising engagement and its decision-support question.
- Uses DOCA.8: affected requalification when a relied-on condition changes.