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.
| Operation | Question to try | Difference to retain |
|---|---|---|
| Develop available material | What can we change or recombine with the means we have, and what difference could we examine? | Use C.40 to perform and examine the change. Retain a useful local result and any application or next question it suggests. |
| Substitute a receiving use | Where else does this difficulty occur, and what changes with the receiver, timing, scale, environment, or acceptance expectation? | A different worthwhile result or a condition that makes the original contribution useful. |
| Substitute a technology or Method | Could manual, organizational, technical, provider, or mixed support supply the contribution differently? | A different mechanism, burden, limitation, or dependency, not just a new brand. |
| Vary a characteristic | Could lower latency, clearer limits, better accessibility, reversibility, or a different burden make a contribution worthwhile? | An action-changing characteristic and the question about its meaning or evidence. |
| Combine or change support | Could access, feedback, review, interfaces, resources, or a different division of contributions make an existing capability usable? | The support change and the dependency it would remove or introduce. |
| Challenge an assumed constraint | Is this restriction a fact, an authoritative limit, a chosen premise, or an untested assumption? | A conditional alternative and the exact premise that must be resolved. |
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.