Part II — Construct opportunities

DOCA.2 - Search Neighboring Uses, Technologies, Characteristics, and Supports for Development Opportunities

Type: DPF pattern

Status: Released; evolving

Normativity: Normative unless marked informative.

DOCA.2:1 - Problem Frame

Use this when a development inquiry keeps returning to one course, provider, technology, role, or familiar future, while a different receiving use or support could reveal a more useful contribution. Also use it when idea generation is expanding but nobody can say what difference the next search should expose or when to stop.

Start with one bounded subject, a question worth investigating, a horizon, protected conditions, and an effort limit. The question may concern a known receiver or what a change to available material could reveal. Ask what could change if the receiving use, the way of contributing, a relevant characteristic, or the support were different. The first useful result can be a small set of materially different leads with their generating operations, sources and next question. An examined local result can also be enough to stop this branch.

This is opportunity-generating search: the worthwhile problem and target contribution may still be provisional. A lead is a possibility worth examining, not yet a supported need, complete direction, or reachable change. A separate adviser is unnecessary.

Ordinary non-use boundary. Reuse an adequate lead or direction set when another search is unlikely to change the current inquiry. If a bounded decision-support question already needs a finite alternative set, use PSD.8. If one domain practice owns the whole discovery question, use it directly. If the only question is a requirement’s justification, use C.11.DUA with its direct domain basis without reopening opportunity search. Do not open a generation archive merely to remember two possibilities.

DOCA.2:2 - Problem

A search can inherit its answer from the first suggestion. Searching for better courses still assumes that learning is the needed change; searching for better models still assumes that the model is the limiting part. Different brands then masquerade as different opportunities.

Unbounded brainstorming fails differently. It accumulates possibilities without a recoverable receiving use, generating operation, source limit, or next discriminating question. Idea count and novelty replace usefulness; checking every lead consumes the time intended for development.

The practitioner needs enough contrast to expose consequential unknowns, without claiming an exhaustive possibility space or making evidence qualification a prerequisite for imagining anything.

DOCA.2:3 - Forces

DOCA.2:4 - Solution

Vary the few dimensions that could change the opportunity, make the resulting differences inspectable, and stop once the inquiry has a useful result or a specific limit.

DOCA.2:4.1 - Choose the search question and its limit

Recover the subject and configuration, the receiving concern when known, the local question, horizon, protections, and effort boundary. Use DOCA.1 only if these are still too loose to distinguish a useful lead from a slogan. Use DOCA.1.CHR when an unclear characteristic, scale, or current reading prevents a productive contrast.

Write a question such as: “What different contribution could help the receiving engineer recover unsupported acceptance claims within this quarter?” The question may explore what is worthwhile; it need not name one fixed target or preferred solution.

Name what may be investigated at the chosen effort and with the available permissions. A short source search and a permitted conversation may be enough. If protected records, experiments, or professional assessments are needed, return the corresponding access or specialist request before doing that work.

DOCA.2:4.2 - Search from more than one direction when it can change the answer

Use the following prompts selectively. They are search operations, not a required taxonomy or a four-step sequence.

Do not lift a binding safety, confidentiality, legal, or authority condition merely to generate a convenient lead. If the requirement’s own justification is the live question, use C.11.DUA §4.3 with the competent domain contribution. Identify the protected person or System and outcome, governed quantity or activity, evidence and threshold basis, marginal protection, full burden and displaced protective work. Compare retaining, tightening, revising or replacing it only where those are meaningful alternatives.

Return the supported requirement recommendation and the reason or limit needed for this opportunity inquiry. Keep its present force, amendment authority and feasible window distinct. The appraisal can finish when timely amendment is unavailable; current leads still inherit the original binding limit. A possible later revision does not restore the opportunity lost under the present conditions.

Use explicit value questions: what would matter to a receiver, what burden should diminish, and what must remain protected? When group advocacy could anchor the search, let participants first propose possibilities independently, then use their differences to extend the set. Neither a workshop nor a separate group is mandatory.

DOCA.2:4.3 - Keep the operation, source, and claim status together

For each retained lead, say what was varied, where the idea came from, what concrete difference might matter, and what remains unsupported. Preserve a source date or edition when its currentness affects the next use. Distinguish the source’s actual claim from the inference made for this subject.

For example: “The supplier describes long-record retrieval; changing the receiving use from automatic approval to claim-to-evidence recovery suggests a possible review aid. We have no result establishing its accuracy or permitted use with these records.” That is a search lead with a testable connection, not a supplier-validated opportunity.

Independent-looking pages that repeat one announcement supply one lineage of suggestion. A demonstration for another person, organization, model configuration, or environment is an analogy until the receiving practice qualifies its use. Use DOCA.1.CHR for a relied-on characteristic transfer and DOCA.5 for a material reachability premise.

DOCA.2:4.4 - Retain meaningful contrasts without prematurely ranking them

Keep a lead when its difference could change the receiving problem, proposed contribution, support, burden, protection, horizon, or next evidence request. Merge duplicates whose differences change none of those. Do not discard a distinct useful question solely because another lead has a more impressive demonstration.

Keep the current way, a smaller repair, or no new development when each is a serious answer. “No new development” still has the continuing Work, costs, and exposure of the actual baseline.

Mark leads as ready for problem/contribution inquiry, conditional on a named premise, rejected for this use, or retained for a separately stated future question. These are working descriptions, not scores or a universal classification. The strongest available result may be that none of the searched leads yet identifies a worthwhile contribution.

DOCA.2:4.5 - Stop at a useful difference or an exact gap

Stop widening when the retained contrasts expose the unknowns that can change the inquiry at its chosen effort, when an adequate set already exists, or when a missing premise makes further generation uninformative. If the effort limit is reached first, report that limit and any consequential unsearched area; do not describe the search as sufficient merely because the time was spent.

State the next discriminating question and how plausible answers would change the leads. Use DOCA.3 when the missing result is the receiver’s worthwhile problem or proposed contribution, and DOCA.4 when that result is already adequate and directions need support configurations. A return to one missing frame or characteristic is also a complete outcome.

A two-sentence return can suffice: “Changing the use and support exposed claim-to-evidence recovery and shift-exception handoff as different leads; three other products repeat the first mechanism. We stopped after the agreed source search because the next difference depends on whether receivers need either contribution; accessibility beyond the current office use remains unsearched.”

DOCA.2:4.6 - Use formal search machinery only for its actual question

Use C.17 when novelty, creativity, or value must be characterized for a named bearer, comparison basis, and objective. A novelty result alone does not establish worth for this development inquiry. Use C.18 when an actual generation archive or front needs its generator, operators, descriptors, lineage, retention, or comparison basis. Use C.19 when the question is how to treat a still-live pool under its declared policy: widen it, keep its frontier, narrow it to a subset, or sunset a line. Selecting the next local candidate or probe under an unchanged policy is not that question.

Visiting a new region does not by itself expand the admissible possibility space. A stronger expansion claim needs the earlier and changed generation conditions and evidence of what a new operator, access relation, or building block makes available. Ordinary neighboring search need not make that claim.

Reopen only the affected search when a source, protected condition, receiving use, or generating assumption changes. DOCA.8 traces the effect into retained opportunities and downstream advice.

An available construction can therefore be an entry before a receiver or final contribution is known. Use C.40 when examining a feasible variation can disclose a useful continuation. Use C.40.CD when a changed question requires changing the way of answering it, and the attempted way can change the next question. Bring a suggested application back to DOCA.3 for its receiving-use inquiry. Neither route requires performing a variation when an adequate lead already exists.

DOCA.2:5 - Archetypal Grounding

DOCA.2:5.1 - A model announcement becomes two different questions

This constructed case stipulates an engineering-services unit’s ninety-day inquiry and a two-hour source-search allowance. Confidentiality, independent acceptance, and continuing service are protected. An announcement says a model can process long records; the unit has not established a worthwhile development problem.

The first search finds three model products with similar advertised retrieval functions. This changes a possible supplier, not the receiving contribution. A use contrast then separates two possibilities: helping an acceptance engineer recover unsupported claims, and helping shift staff recover unresolved exceptions. A support contrast adds a manual index to the first and a clearer human handoff to the second.

The return is two leads, each with a non-model possibility and a distinct missing premise. The acceptance lead needs a receiver’s account of the qualification gap and purpose-specific record access. The shift lead needs the relevant exception problem, receiving-holder support, and attention limits. Neither demonstration establishes those premises.

The team stops widening within its allowance because receiver inquiry can now distinguish the two leads more usefully than another product search. It records that non-office accessibility uses were not explored. The next question—whether either receiver identifies a consequential unmet contribution—is the DOCA.3 problem/contribution inquiry, unless an adequate existing account already answers it. Its answer can qualify, narrow, or reject the hypothesis. A positive answer alone establishes neither a feasible direction nor a commitment; rejection concerns this use, not every possible use of the technology.

DOCA.2:5.2 - A person searches contributions, not course names

Mira has four months to explore a next contribution in engineering Work. She contrasts evidence review, where the receiver needs unsupported claim-to-test links found, with interface coordination, where specialists need incompatible assumptions surfaced. Reading technical documents occurs in both; their receiving results differ.

She also varies support. For evidence review, permitted examples exist but representative capability and transfer evidence are missing. For coordination, access to participants and competent feedback are not established. The two leads retain different missing premises. Either conditional lead can finish this inquiry; request further evidence only when its obtainable contribution warrants acquisition through A.15.9 and C.11.DUA. A course catalogue may suggest a resource, but cannot merge the contributions or fill either gap. Mira can stop with these questions without engaging an adviser.

DOCA.2:5.3 - An adequate facility set is reused

A facility team already has current manual-repair, sensor-replacement, and changed-maintenance candidates for the same service concern. The remaining uncertainty is the safe outage window. Another technology search would not change that question, so the team requests the outage result and does not use this pattern to enlarge the set.

DOCA.2:5.4 - A useful question emerges from available material

A constructed workshop has permission to examine four records and an available sorting operation. The records are ordered by job: A starts at 09:00 and finishes at 09:08; B starts at 09:03 and finishes at 09:07. No future service or customer has been selected. A five-minute exploration can ask what a chronological view exposes.

Sorting by time produces A-start, B-start, B-finish, A-finish. The view makes a four-minute overlap visible. Keep the view and its sorting rule for the next question: could seeing overlapping jobs help someone coordinate the workshop? DOCA.3 can investigate that possible receiving use. The overlap alone establishes neither a coordination problem nor competition for one resource.

If the workshop already has an adequate view and no worthwhile further question emerges, stop this branch. The examined result remains a local answer; no opportunity account or service proposal is needed to complete it.

DOCA.2:6 - Bias-Annotation

• Supplier anchoring: product variety hides the unchanged receiving-use assumption.
• Novelty preference: an unfamiliar idea displaces a useful small repair without a value reason.
• Source-count illusion: repeated announcements look like independent evidence.
• Available-support bias: an offered course or tool defines the future before the needed contribution is understood.
• Constraint wishfulness: an inconvenient protection is treated as removable without its owner’s result.
• Search-completion bias: a spent budget or full table is mistaken for adequate coverage.

DOCA.2:7 - Conformance Checklist

A conforming search return:

1. MUST name the subject, local question, horizon, relevant protections, and effort boundary, together with the receiving concern when known.
2. MUST identify the generating operations and the differences that make retained leads consequential.
3. MUST distinguish source claims, local inferences, analogy, and missing evidence.
4. MUST NOT equate source count, idea count, novelty, or a supplier demonstration with local worth or reachability.
5. MUST preserve binding constraints while separately identifying assumptions that may be investigated. A live merits question returns its supported judgement of protection and burden and the actual amendment limit, without treating the recommendation as a changed rule.
6. MUST state the stopping reason and any unsearched area whose omission can change the receiving use.
7. MUST return a useful local answer, a next question with action-changing answers, an adequate lead set, rejection, or a specific gap.
8. MUST NOT require a workshop, exhaustive search, archive, live pool, recommendation, or selected direction for an ordinary search result.
9. SHOULD reuse an adequate set and retain a serious baseline or smaller repair when relevant.

DOCA.2:8 - Common Anti-Patterns and How to Avoid Them

DOCA.2:9 - Consequences

The practitioner can explain how a search changed the possibilities under consideration and why it stopped. An old capability with better support can remain alongside a new technology. Rejected or unresolved leads retain reasons that make later reconsideration local.

The cost is a small amount of source and difference tracking. Search can end without a positive opportunity, and relevant unsearched areas may remain. The result supports the next inquiry; it supplies neither the receiver’s value evidence nor the subject’s feasible development change.

DOCA.2:10 - Rationale

Searching along several consequential dimensions loosens the first proposed solution without requiring limitless creativity. Naming the generating operation makes a lead criticizable: a receiver can question the use, a specialist can challenge the transferred characteristic, and a support owner can identify the unavailable relation.

Stopping at the next discriminating question converts breadth into a usable return. A missing premise then guides work instead of being hidden by more suggestions.

DOCA.2:11 - SoTA-Echoing

Practice question. How can a development inquiry discover useful possibilities before its problem and target result are fixed, while keeping effort and reliance bounded?

Best-known line for this use. Value-guided contrastive search, coupled to source-qualified return, supplies the useful move. ISO 56007:2023 places opportunity and concept work before solution development and deployment and rejects one universal tool set. Its public scope supplies a normative boundary, not evidence that this search succeeds. Keeney’s value-focused brainstorming supplies the historical generation anchor: use explicit values to generate alternatives and, when groups are involved, obtain individual ideas before group anchoring. This pattern adapts those contributions in :4.1–:4.5 to provisional receiving uses, explicit operations, protected constraints, and proportional stopping.

Comparison at comparable effort. A short supplier-menu search is efficient when the needed contribution is settled. In the constructed model case, the same bounded inquiry obtains more consequential differences by varying use and support than by retaining three brands. Unstructured brainstorming can reveal surprises but leaves the practitioner to reconstruct source limits and the next question. Adopt the contrastive move for that unresolved-use situation; retain a menu or direct domain Method when it already answers the question. The cost is explaining each retained difference instead of reporting only names.

Current neighboring contribution. PSD.8 supplies a finite alternative set for a bounded decision-support question; C.18 supplies archive/front stewardship. Neither result is required merely to perform this earlier search. Their boundaries prevent a search lead from being promoted by its position in a list or archive.

Source limits and reopen. The source combination is guidance, not comparative effectiveness evidence or a universal development mechanism. Reopen the affected move if a stronger current generation practice produces useful contrasts with less burden while preserving source limits, protected conditions, and a discriminating stop, or if a relied-on source changes those obligations.

DOCA.2:12 - Relations

• Receives from DOCA.1: inquiry scope, protections, horizon, and effort when missing.
• Uses DOCA.1.CHR: characteristic meanings and qualified readings that make a search contrast interpretable.
• Supplies DOCA.3: leads whose worthwhile problem and proposed contribution need inquiry.
• Supplies DOCA.4: leads with an adequate contribution premise that need distinct support configurations.
• Uses PSD.8: finite alternative generation when a bounded decision-support question is the receiving use; this is a conditional return, not the next numbered stage.
• Uses C.17, C.18, or C.19: only for the actual novelty/value characterization, archive/front stewardship, or live-pool treatment policy each governs; local candidate/probe selection is a different question.
• Uses DOCA.5 and DOCA.8: qualification of a material reachability premise and tracing of changed premises into retained uses.
• Returns to domain and holder practices: local need, feasibility, capability, access, safety, and other substantive results that search cannot supply.

DOCA.2:End

DOCA.3 - Construct a Worthwhile Problem and Proposed Contribution

Type: DPF pattern

Status: Released; evolving

Normativity: Normative unless marked informative.

DOCA.3:1 - Problem Frame

Use this when a development lead names an attractive niche, technology, course, service, or provider promise, but the receiving use and the reason to change it remain unclear. Someone may say “we need AI,” “become a leader,” or “offer faster analysis” without identifying whose result is unsatisfactory, what difference matters, or what could actually be supplied.

Start by asking the receiver what is missing or foregone in one bounded use. Relate that problem to a proposed contribution and an inspectable acceptance expectation. The first useful result is a supported worthwhile problem or an explicitly unconfirmed problem hypothesis, together with the proposed contribution, its limits, and the question that could confirm, narrow, or reject it.

The subject that might develop and the receiver of its later contribution can differ. A person may explore their own future Work without an adviser; an organization may investigate a contribution for a client; a research programme may seek an epistemic contribution rather than a commercial offer.

Ordinary non-use boundary. Reuse an adequate problem/contribution account when its receiving use, evidence, protections, and horizon remain current. Proceed to DOCA.4 if only the way of obtaining that contribution is missing. Use PSD.3 when a bounded decision-support inquiry needs materially different problem formulations. This pattern does not establish an actual commitment, choose a direction, or justify intervention by itself.

DOCA.3:2 - Problem

A niche, a worthwhile problem, and a proposed contribution answer different questions. A niche is a possible fit between a contribution and a use. The problem explains why an inadequate or foregone result matters there. The contribution says what could be supplied and how the receiver would recognize it.

If these are collapsed, a supplier’s enthusiasm becomes demand, a proposed offer becomes a commitment, and a useful intermediate result becomes a promise of benefit. “Recover missing evidence” turns into “approve faster,” although neither the time saving nor the approval is established. Alternatively, a practitioner rejects a useful problem merely because no feasible way to address it is known yet.

The needed move is to make the value and contribution claims separately inspectable, preserving uncertainty without losing a worthwhile next question.

DOCA.3:3 - Forces

DOCA.3:4 - Solution

Write a small, source-qualified account of why a change could be worth pursuing and what contribution would answer it. Keep a supported problem, an open hypothesis, and a rejected lead visibly different.

DOCA.3:4.1 - Recover the receiver’s situation

Name the developing subject, the prospective receiver, the later Work or use, the horizon, and the relevant conditions. Ask what result is currently inadequate or unavailable, what happens if nothing changes, and which evidence or participant account supports that description.

Use qualified evidence about actual Work or receiving demand when it exists. A receiver’s report can establish their stated concern; its causal explanation, scale, representativeness, and effects on others may still need qualification. Do not infer organization-wide demand from one person’s preference.

If the inquiry cannot yet identify a receiving situation, use DOCA.1 or DOCA.2 to recover a worthwhile next question. When usable material and an available operation permit a revealing local change, their C.40 entry lets that inquiry proceed before its future application is settled. A use suggested by the result is then a problem hypothesis to examine here. Keep an unknown receiver explicit; do not invent a customer to complete the account.

DOCA.3:4.2 - Separate the problem from the proposed answer

Describe the missing or inadequate result without building in one technology, provider, training programme, or staffing answer. Then state the proposed contribution separately.

For example:

• Problem: an acceptance engineer cannot recover which submitted claims lack a sufficient evidence basis before the handoff review.
• Proposed contribution: an inspectable claim-to-evidence account that identifies supported claims, missing premises, and qualification limits in the permitted source set.
• Acceptance expectation: the receiver can trace each entry to its source and identify unresolved claims under the applicable review criteria.

Faster approval is a different benefit claim; automatic approval is a different contribution and authority question. Preserve those differences if they become live rather than silently extending the proposal.

If rival problem formulations change the subject, boundary, evidence, intervention family, or affected interests, keep them distinct. PSD.3 supplies plural formulation work when a decision-support engagement is current. A change of wording that leaves those consequences identical does not create another worthwhile problem.

DOCA.3:4.3 - Establish what makes the problem worthwhile

Ask who is affected, why the missing result matters, at what scale and horizon, and under what burdens and protections addressing it could be worth pursuing. Include material contrary evidence and consequences for affected people or Systems, not only the proposed beneficiary.

Use the domain practice that owns each relied-on claim. A human capability need belongs with current HCD and representative later-Work evidence; a service failure belongs with the relevant operations and domain evidence; safety, access, finance, legal, and other specialist claims retain their own qualification. Use DOCA.1.CHR when the value account relies on unclear or incompatible characteristics.

Return the strongest supported statement:

• a worthwhile problem for this receiving use under stated conditions;
• an attributed or contested value claim requiring a named resolution;
• an unconfirmed problem hypothesis with the exact confirming question; or
• rejection or revision of the lead because no worthwhile problem is supported at the chosen scale.

A receiver’s desire alone does not defeat a binding protection. Conversely, missing feasibility does not disprove the problem: retain the worthwhile problem and name the unresolved way of addressing it. For a comparative claim such as “worth the transition cost,” obtain the applicable comparison rather than treating this inquiry as its proof.

DOCA.3:4.4 - State the proposed contribution and its acceptance expectation

Say what could be supplied, for which receiving use, under what conditions, with what exclusions, and what the receiver could inspect to determine whether that contribution was supplied as proposed. Keep the proposed result, the acceptance criterion, and any actual acceptance separate.

Use A.2.3 when a promise’s content must be identified or relied on. Read an existing provider promise from its actual source; mark a newly constructed promise as proposed. Neither description establishes a provider commitment, capability, access, provision, fulfilment, or achieved benefit.

A research contribution can be a criticism, discriminating experiment, reproducible comparison, or clarification of an unresolved claim. It need not be sold, but its intended epistemic result and evidence standard must still be inspectable. Do not impose a commercial service model on that use.

DOCA.3:4.5 - Link the contribution to the problem without assuming success

Explain why the proposed result could address the missing receiving result. Mark that connection as supported, conditional, disputed, or hypothetical according to its evidence. Identify what a plausible contrary answer would change.

Ask the smallest question that distinguishes the live possibilities. “Does the reviewer need a source-traceable account of unsupported claims, or is the delay actually caused by unavailable acceptance authority?” can redirect the contribution. “Would you like better AI?” cannot distinguish the problem from the preferred solution.

Use existing adequate results before requesting new Work. When another practice must supply an answer, use A.15.9 for the bounded result request and reliance boundary. The supplying practice answers its own substantive question. A proposed interview, measurement, or experiment still needs the permissions and conditions applicable to that activity.

DOCA.3:4.6 - Return the account at the strength it supports

Ordinary prose is enough when the receiver can recover the situation, worthwhile difference or hypothesis, contribution, acceptance expectation, evidence limits, and next question. For example:

The case’s acceptance engineer reports that unsupported claims cannot be recovered reliably from the incoming package, and the stipulated review records support that concern. We propose a source-traceable claim-to-evidence account, not approval; the next question is whether the available records and review criteria cover a representative package without breaching confidentiality.

Use DOCA.4 when the contribution premise is adequate and materially different directions need construction. Return to DOCA.2 when the lead must change. Stop with a problem hypothesis or rejection when that is the truthful result. If an adequate direction already exists, proceed directly to the missing reachability, comparison, or advising result; no mandatory cycle through earlier PatternIDs follows.

Reopen the affected problem or contribution under DOCA.8 when the receiving use, value evidence, acceptance expectation, source, horizon, or protected condition changes. A narrower permitted source set can narrow one proposed contribution while leaving the receiver’s problem and another direction intact.

DOCA.3:5 - Archetypal Grounding

DOCA.3:5.1 - Qualification support is not faster approval

This constructed example stipulates an engineering-services unit’s ninety-day inquiry. Its acceptance engineer reports repeated difficulty finding unsupported claims in incoming evidence packages; the example’s review records corroborate that bounded concern. Confidentiality, traceability, independent acceptance, and tolerable review burden are protected.

The technology lead was “use a long-record model.” The problem/contribution account instead proposes a claim-to-evidence account for one class of package. The acceptance expectation is that the reviewer can recover each included claim’s cited support and identify unresolved premises under the relevant criteria. A manual index and bounded retrieval assistance could both serve that proposal.

No result yet establishes faster approval or representative model accuracy. The first useful return preserves the worthwhile qualification problem while marking the processing route as conditional on purpose-specific access and evaluation. If the data owner permits only public, non-representative samples, a narrow demonstration remains possible; the original representative-use claim remains unsupported.

A rival lead concerns shift exceptions and the next authorized handoff action. That is a different receiving problem, not a second implementation of the same qualification account. The two remain distinct for later direction construction.

DOCA.3:5.2 - Receiver inquiry rejects a supplier lead

A supplier offers a dashboard to a small unit as an “AI transformation.” In this constructed case, the unit’s current result meets its acceptance needs, its receivers identify no consequential unmet result at the proposed scale, and the proposal adds review burden. No independent protected or foregone-result concern is established.

The inquiry rejects this lead for the current use. It does not claim that the technology is universally useless. Retaining the idea for a different receiving question would require that question and a retention reason, not relabelling the rejected proposal as a worthwhile opportunity.

DOCA.3:5.3 - A research problem remains a hypothesis

A research group suspects that an evaluation loses important failure cases when several task types are pooled. The proposed contribution is a reproducible comparison between the pooled and separated analyses, with explicit limits on what any difference would establish.

The problem is provisional: no result yet shows that the suspected loss changes the relevant scientific conclusion. The next question is whether the comparison exposes a conclusion-changing discrepancy on an admissible dataset. A negative answer closes or narrows the hypothesis; a positive answer motivates further research. Publication, funding, and improved model performance are not part of the proposed epistemic result.

DOCA.3:6 - Bias-Annotation

• Solution-first framing: the supposed problem contains the technology or intervention it is meant to justify.
• Receiver-preference inflation: one person’s interest is treated as established demand at another scale.
• Benefit inflation: an inspectable intermediate contribution is described as a guaranteed downstream improvement.
• Supplier authority: an offer is taken as evidence of need, capability, or fulfilment.
• Commercial projection: a research or community contribution is forced into a sales promise.
• Feasibility contamination: an unknown solution causes rejection of a still-worthwhile problem, or a feasible tool creates a supposed need.

DOCA.3:7 - Conformance Checklist

A conforming problem/contribution account:

1. MUST identify the developing subject, receiving use, horizon, and relevant protected conditions.
2. MUST distinguish the inadequate or foregone result, why it matters, and the proposed contribution.
3. MUST distinguish a supported worthwhile problem, an attributed or disputed claim, an unconfirmed hypothesis, and rejection where those outcomes are live.
4. MUST preserve material contrary evidence, affected-System consequences, and burdens that can reverse the worth claim.
5. MUST state an inspectable acceptance expectation without reporting actual acceptance or achieved benefit.
6. MUST distinguish a proposed promise from an existing promise and both from commitment, provision, and fulfilment.
7. MUST expose the evidence or hypothesis linking the contribution to the problem and the next discriminating question.
8. MUST NOT infer need from novelty, a supplier offer, or solution feasibility, or reject a supported receiving problem solely because solution evidence is missing.
9. MUST return to the next missing result or stop; a direction, recommendation, choice, or intervention is not required to complete this account.

DOCA.3:8 - Common Anti-Patterns and How to Avoid Them

DOCA.3:9 - Consequences

The practitioner can distinguish what might be worth addressing from what could be supplied. A useful hypothesis can survive without invented evidence, and a supplier lead can be rejected before it consumes a development programme or procurement budget. Later direction construction has an inspectable premise rather than a slogan.

The cost is receiver and evidence inquiry. Different people may value the proposed change differently, and the available evidence may justify only a narrower problem or an unanswered question. This pattern makes those limits visible; it does not settle domain truth, comparative value, or authority by naming an opportunity.

DOCA.3:10 - Rationale

Separating problem, proposed contribution, and acceptance expectation lets each be challenged without discarding the others. A receiving difficulty can remain valid when one delivery route fails. A contribution can be precisely described while its worth remains hypothetical. The distinction prevents both premature commitment and premature rejection.

An explicit confirming question gives provisional value a practical use. It says what the next answer would change instead of treating uncertainty as either permission to promise or a reason for indefinite research.

DOCA.3:11 - SoTA-Echoing

Practice question. How can a promising lead become a worthwhile receiving problem and proposed contribution without importing the supplier’s preferred solution or overstating benefit?

Best-known line for this use. Combine receiver-grounded problem inquiry with an explicit problem/contribution distinction. ISO 56007:2023 supplies the bounded opportunity/concept front-end before solution development. Current PSD.3 supplies materially different formulations and their evidence consequences; A.2.3 supplies promise-content identity without conflating commitment and fulfilment. This pattern adapts those contributions in :4.1–:4.6 to one prospective development contribution and its confirming return. Domain evidence, rather than the source combination, supports the actual worth claim.

Serious alternative and trade-off. An offer-led brief is cheaper when a qualified receiving need and acceptance basis already exist. When they do not, it hides the problem inside the offered answer. At comparable bounded inquiry effort, asking what result is missing and what would count as a supplied contribution can distinguish qualification support from faster approval and from shift handoff in :5.1. A full decision-modeling engagement can handle richer competing values, but is unnecessary when a short receiver account or a negative answer resolves the lead. Use that fuller work when it changes the decision rather than making it an entry requirement.

Source roles and limits. ISO supplies normative scope, PSD.3 formulation guidance, and A.2.3 semantic distinctions. None establishes this receiver’s need, a causal benefit, professional authority, or the empirical effectiveness of this cross-holder inquiry. A commercial promise is one possible use, not the template for every epistemic or community contribution.

Reopen. Reopen the affected move if current practice supplies a better low-burden way to expose false need, overpromised benefit, or consequential missing participants while preserving a usable first return; or if a relied-on source changes the problem, value, or promise boundary.

DOCA.3:12 - Relations

• Receives from DOCA.1 and DOCA.2: the bounded inquiry and leads whose receiving contribution remains uncertain; adequate direct inputs may be reused.
• Uses DOCA.1.CHR: characteristics and scales needed to make a worth or contribution claim interpretable.
• Uses PSD.3: plural formulations when their structural differences change a bounded decision-support inquiry.
• Uses A.2.3: identity and conditions of relied-on promise content, distinct from commitment and provision.
• Uses A.15.9: the smallest missing outside-practice result and its reliance boundary, without performing the supplier’s Method.
• Supplies DOCA.4: worthwhile problem/proposed-contribution accounts, including explicit hypotheses and acceptance expectations.
• Supplies DOCA.5: the value and contribution claims whose necessary transitions still need qualification; a worthwhile problem is not a reachability verdict.
• Uses DOCA.8: local requalification when receiving need, source, acceptance, protection, or horizon changes.

DOCA.3:End

DOCA.4 - Construct Development Directions with Their Support Configurations

Type: DPF pattern

Status: Released; evolving

Normativity: Normative unless marked informative.

DOCA.4:1 - Problem Frame

Use this when a worthwhile problem or proposed contribution is clear enough to explore, but the proposed direction is still “train,” “buy,” “automate,” “hire,” or “learn Pattern X.” Those labels omit the change, later Work, access, support, transition burden, and evidence that would make the contribution possible.

Start by describing one finite change from the actual situation, together with the support needed to obtain the proposed contribution. Construct a materially different way when it could change the inquiry. The first useful result is a small set of contribution-bearing direction/support configurations, or one such candidate with an exact missing alternative or premise.

A direction here is a prospective change in contribution, capability, use, or enabling conditions over a declared horizon. Its description is not an obtaining arrangement, selected programme, WorkPlan, performed Work, or choice. A person exploring their own development can use it without asking for advice.

Ordinary non-use boundary. Reuse adequate directions when only reachability or comparison remains. If the receiving problem or contribution is still missing, use DOCA.3; do not complete a training or tool configuration around an unexamined need. If a domain practice owns the whole configuration question, use it directly. Once one organization result, use, and acceptance premise are stable and whole obtaining arrangements are the decision, OCE.8 supplies that comparison and its authorized return.

DOCA.4:2 - Problem

A direction can sound concrete because it names a product, course, Method, or person. Yet the proposed intervention may address only one fragment of what makes the later contribution possible. Training alone does not establish access; naming a model does not establish evaluation or receiving-holder support; a provider offer does not establish a usable result or a continuing arrangement.

Another failure compares fragments under different assumptions. One direction includes feedback and transition time while another is credited with its advertised benefit alone. A path compares every later step with today’s baseline, hiding the configuration and costs that earlier steps create. “Learn this pattern” supplies no usable next development step when neither its complete contribution nor representative use is recoverable.

The practitioner needs possible configurations that expose what changes, what must support the change, what may worsen, and what remains to be established before reliance.

DOCA.4:3 - Forces

DOCA.4:4 - Solution

Construct whole-enough prospective directions around the receiving contribution. Preserve their finite changes, supports, consequences, and unresolved premises before asking which is reachable or preferable.

DOCA.4:4.1 - Recover the contribution and the actual starting condition

Name the developing subject and configuration, receiving Work or use, proposed result, acceptance expectation, horizon, scenarios, and protected conditions. Use the current problem/contribution account from DOCA.3 or an adequate direct source. Preserve an unconfirmed problem as a hypothesis rather than strengthening it through detailed design.

Recover the actual starting configuration S0: relevant capability, access, support, Work, interfaces, resources, and current readings. Mark unknowns. A job title, organization chart, tool inventory, or source publication is not that baseline.

Use DOCA.1.CHR for the characteristic meanings, scales, current/intended/protected/unknown readings, and evidence window needed by the inquiry. Characterize only what could change the direction or its qualification; do not commission a complete diagnosis by default.

DOCA.4:4.2 - Turn a label into a complete contribution

For every serious proposal, explain what the subject or supported arrangement could contribute in the receiving situation. State the recognizable situation, useful move, first result, and stop or non-use boundary. Include the support and substantive conditions that change how the contribution is obtained.

When a pattern is the proposed address, cite its complete current body and recover the action-bearing contribution from it. Do not substitute its title, PatternID, a summary card, or a list of topics for that contribution. Keep the body’s relevant applicability, assurance, and stopping conditions; the direction need not copy the entire source.

If the receiving claim depends on a Method or MethodDescription, preserve its established relation under A.3.1 and A.3.2. A pattern is a MethodDescription only when it describes an already admitted Method as its EntityOfConcern. Otherwise use its content as pattern guidance and leave that stronger relation unasserted. In neither case does reading or publishing the description establish the subject’s capability.

For a person, connect the contribution to representative later Work. “Use A.15.9 to formulate and rely on a bounded outside-practice result in evidence review” can specify a contribution; “finish A.15.9” cannot specify capability or transfer. Current HCD and the relevant domain practice supply those results.

DOCA.4:4.3 - Construct materially different directions

Vary the change that could make the contribution possible. Useful contrasts include developing a capability, making an existing capability usable through access or support, obtaining a qualified external contribution, changing the work or interface, or changing the proposed contribution itself. They are prompts, not mandatory candidate families.

Distinguish two questions:

• Different contribution premises: directions address different worthwhile problems, results, uses, or acceptance expectations. Preserve those differences for the receiving comparison.
• Different ways of obtaining one contribution: candidates hold the result premise stable but vary the supporting arrangement. For organization-change decisions, use OCE.8 when that whole same-result question is current.

Use PSD.8 when the receiving work is a bounded decision-support alternative set. PSD.8 can retain alternatives for different live formulations; same-result parity is not its universal entry condition.

Retain the actual baseline, a smaller repair, a staged direction, or no new development when each genuinely answers the inquiry. No change still carries continuing Work, resource use, and exposure. A missing alternative is an honest return; do not invent a weak candidate to make a preferred one win.

DOCA.4:4.4 - Specify the finite change and support configuration

For each retained direction, state the finite change Delta and candidate configuration S1 relative to S0. Give enough support detail to identify the material dependencies and contradictions:

• what contribution or Work would change, and who or what would perform or support it;
• required capability, access, feedback, tools, Methods, interfaces, provider contributions, resources, and authority where each is consequential;
• prerequisites, sequence or coexistence conditions, constraints, and interactions;
• transition and implementation Work, including migration, setup, evaluation, recovery, and continuing-service needs;
• what can be reversed, at what burden, and what remains irreversible; and
• later options that the change could open, close, delay, or preserve, with the basis and uncertainty of those claims.

Describe how the proposed performers, supports, and relations fit together under these conditions. A feedback provider needed by two candidates may have capacity for only one. A combined model-and-human arrangement may add review or recovery Work that neither component proposal named.

Use direct holder, engineering, operations, organization, provider, safety, and other practices for their mechanisms and quantities. Unknown support does not establish realizability. Keep the direction conditional, identifying the result needed to construct a realizable candidate; reject or revise it when a qualified condition rules out its necessary support. Do not discard the worthwhile contribution merely because this way fails.

DOCA.4:4.5 - Preserve the complete finite-comparison basis

When making a finite contribution comparison, use C.11.CRC. Compare actual or relied-on S0, finite Delta, and realizable candidate S1 under one system boundary, receiving decision, horizon, scenarios, constraints, interactions, transition basis, uncertainty, and evidence window.

Keep four coordinate families visible: useful results; consumed resources; consequences for affected Systems and the distribution of gains and burdens; and explicitly protected conditions. Retain each characteristic’s scale and polarity. Do not hide one family in another or average incompatible scales.

For a Pareto-improvement claim, no coordinate in the declared complete set may worsen and at least one must improve under that same basis. Otherwise state only the supported relation, such as beneficial under a stated value judgement, harmful, dominated, non-dominated, or indeterminate. A direction with a possible gain and an unresolved protected condition is not thereby a Pareto improvement or a selected option.

If reachability or another necessary premise is missing, give the conditional configuration and comparison question to DOCA.5; do not manufacture a complete comparison. A numerical or analytical result from elsewhere remains limited to the configuration and use its supplying practice qualified.

For a later step, use its stage-specific S_i, finite Delta_i, and candidate S_i+1, not the original baseline by default. DOCA.6 maintains the resulting finite path or branch account, including each step’s burden, reversibility, option effects, and reopen condition. Neither the path nor its separate comparisons select a programme.

DOCA.4:4.6 - Return a usable candidate or the exact gap

An ordinary direction account can say:

For this receiving Work and horizon, change this part of the current configuration to obtain this contribution, with these supports and protected conditions. The material transition and consequences are these; this premise remains unknown, and its positive, negative, or narrower answer would change the candidate in these ways.

Expand only what the next use needs. A complete enough direction may still be conditional; distinguish a qualified proposed configuration, a conditional direction with a named premise, an incomplete fragment, and a direction ruled out for the current use.

Use DOCA.5 for jointly necessary transitions and competing support. Use DOCA.6 for retention or a finite path when that is the question. If comparison or advice is current, provide the direction and its qualified premises to the appropriate PSD or domain use; DOCA.7 supplies the development-advice relationship boundary only when advice is requested.

For human development, a direction choice may become an input to HCD.2, which composes and compares programme candidates without choosing. A programme-level advice request starts with those comparable candidates; it does not relabel a DOCA path as a programme. Learning Product realizes a Guide from an authorized selected programme and focal pattern contributions. A Guide is not produced by rearranging direction labels.

Reopen only the affected contribution, support, transition, comparison, or downstream use under DOCA.8 when its premises change.

DOCA.4:5 - Archetypal Grounding

DOCA.4:5.1 - A complete pattern contribution for a person’s later Work