DOCA.6 - Maintain an Opportunity Portfolio and Preserve Stepping Stones

Type: DPF pattern

Status: Released; evolving

Normativity: Normative unless marked informative.

DOCA.6:1 - Problem Frame

Use this when useful development opportunities would otherwise disappear because they are not today’s strongest candidate, depend on a later condition, or require a preliminary step whose immediate result is modest. The working question is “what is worth keeping available, for which later use, and at what cost?”

For an opportunity portfolio, name the later option that retention is meant to preserve, together with its contribution, conditions, lineage and next reconsideration. The first useful result can be two retained alternatives with one reason and reopen condition each; a large portfolio system is unnecessary. When no later opportunity can yet be named, the C.40 return in :4.2 handles retaining material for a worthwhile further inquiry.

This pattern governs opportunity retention and path construction within Development Opportunity Construction. A portfolio here is the maintained set of opportunity descriptions and their relevant relations. It is not a funding allocation, selected development programme, recommendation, or permission to realize every member. A stepping stone is a candidate step retained for what it may enable later, not necessarily for being best now.

Ordinary non-use boundary. Do not create a portfolio when one current question needs only a direct qualification or choice and there is no useful later retention. Reuse an adequate set with its current conditions. Enter directly from existing opportunities; no complete earlier DOCA sequence is required. When an authorized programme and its implementation are already the subject, use the owning programme or work practice. If an actual search archive, front, or live-pool treatment is the question, use C.18 or C.19 at the specific return in :4.5.

DOCA.6:2 - Problem

A current ranking can discard an opportunity that preserves a valuable later route. Conversely, retaining everything creates a costly collection with no reason to revisit or discard anything. A “roadmap” can make a conditional sequence look committed before its dependencies are qualified.

Path descriptions introduce another error: every later step is compared with the original situation. Earlier benefits are counted again, transition costs disappear, and the next step inherits capabilities, access, or evidence that have never been established. A preliminary inquiry can be called a stepping stone even when no supported link connects it to the later option.

The practitioner needs a small, revisable set in which retention has a reason, each step begins from its own configuration, and uncertainty does not become an implied choice.

DOCA.6:3 - Forces

DOCA.6:4 - Solution

Retain an opportunity when its expected use or learning value justifies the burden of keeping it. Describe paths as conditional finite transitions; qualify them before making a reachability claim.

DOCA.6:4.1 - State why and for how long something is retained

Name the subject, receiving use, protected conditions, and the horizon or horizons that actually affect this inquiry. Use the horizon needed by the opportunity; do not impose universal near-, medium-, and long-term buckets. When horizons differ, preserve that difference rather than merging their anticipated results into one comparison.

For each retained opportunity, keep its contribution and support configuration, present qualification, source or parent candidate, retention reason, material retention burden, and revisit or discard condition recoverable. Name who will reconsider it when someone has accepted that responsibility. A source pointer may suffice for an unchanged description.

Distinguish preserving an account from preserving an obtainable option. Saving a direction in a note does not reserve a provider, renew data rights, maintain a skill, or keep equipment ready. If retention needs resources or continuing Work, identify that burden and the actual authority or arrangement. Without it, retain a conditional possibility or description, not a claim that the option remains available.

An ordinary two-sentence account is enough:

Keep the permitted manual-review route as the current reference and the retrieval-assisted route as conditional on representative data use and evaluation. Revisit the second when those results arrive or at the end of the ninety-day inquiry; saving its description reserves no data, supplier time, or implementation budget.

DOCA.6:4.2 - Make each stepping-stone claim testable

Name the later option or reachable region, the proposed enabling transition, and the evidence connecting the step to that later use. Ask what becomes possible, less costly, or better qualified because of this step, and what could show that the connection fails.

When a later opportunity is still unknown, a smaller retention claim may suffice: keep an examined construction for an affordable next question. C.40 supplies the development and continuation Method. Preserve the material, operation and conditions that let someone try that continuation. Judge its burden against what the next answer could change; do not invent a distant payoff or call this a qualified path to an unnamed opportunity.

Keep a candidate stepping stone distinct from one whose retention is justified under the stated policy. A plausible connection may justify a bounded inquiry, but does not by itself justify performing the step. State the value, burden, delay, uncertainty, and protected conditions that make retention worthwhile for this use.

A data-access question can be a candidate stepping stone toward representative evaluation. Its possible answers change which evaluation routes remain available. The question itself grants no access and establishes no model capability. A useful course, preliminary project, archive variant, or “zone of proximal development” label likewise needs the particular enabling relation and holder-owned evidence.

Do not require immediate dominance. Retention can be justified by later reachability, coverage, learning, or reversibility even when another candidate has a stronger current result. Conversely, novelty or diversity alone is not proof of future usefulness.

DOCA.6:4.3 - Construct paths from their stage-specific configurations

For every material step in a path or branch, name its own starting configuration, finite change, and resulting candidate configuration. Write S_i -> Δ_i -> S_i+1 only as compact notation for those three descriptions, not as evidence that the transition is feasible.

Recover what the starting configuration inherits: established or still-conditional capability, support, access, ongoing Work, resource demand, remaining uncertainty, and effects of earlier choices. If the earlier step has not occurred, the later starting configuration is conditional too. If the path can branch, name the condition that distinguishes the continuations and the stop when neither is supported.

State each step’s transition burden, reversibility, and effects on later options. Do not repeatedly credit the full difference from the original configuration as each later step’s contribution. Use C.11.CRC for finite comparisons with the complete relevant result, resource, affected-System/distributional, and protected coordinates. Each coordinate keeps its own scale and polarity under the common comparison basis. When step horizons or scenarios differ, obtain an adequate mapping or keep those comparison claims separate.

Use DOCA.5 to qualify the jointly necessary transitions, shared resources, timing, and inherited obligations. A sequence of individually plausible steps remains a conditional path until the necessary joint basis exists. Return a missing holder, access, support, or implementation result through A.15.9. Do not substitute a path diagram for the supplying practice’s conclusion.

A path can preserve alternatives without selecting a programme. Human capability-development programmes remain HCD.2’s composition and comparison question; authorized participants retain programme choice, and Learning Product work realizes the selected programme and pattern contributions as a Guide.

DOCA.6:4.4 - Keep the set inspectable without forcing a winner

Preserve materially different candidates, including conditional directions and a useful baseline, when their retention reasons remain current. Keep a candidate ruled out for this use outside its live opportunity set, with enough explanation to avoid rediscovering the same defeated claim. Preserve other uses separately when their basis remains supported. A historical record can remain useful without being a live option.

Use a comparison only for the question it answers. A result about non-domination requires a declared comparator, complete relevant coordinates, and admissibility basis. A retained candidate need not be non-dominated now. Different contribution premises or horizons may support only a partial comparison; do not invent one scalar ranking to make the portfolio look settled.

Make resource interactions visible when retention itself competes for scarce attention, expertise, access, or maintenance. If the available retention allowance cannot support the set, return the needed allocation or reduction decision to its authorized owner. Meanwhile, describe only what the available maintenance actually supports. Do not silently make every member “available” by naming it in the portfolio.

Stop expanding the account when the next missing result belongs to a holder practice, an actual pool-treatment decision, or a local choice. The inquiry can return a useful partial set.

DOCA.6:4.5 - Use archive, front, and pool treatment only for their actual questions

Use C.18 — Open-Ended Search Archive and Front Stewardship when generation or retention actually needs a search archive, front, descriptor space, lineage, or exploration policy. Its archive preserves exploration or stepping-stone value; its front reports current non-domination under a declared comparator and admissibility. Neither return is a recommendation, selected-set declaration, or work permission.

For generation, recover the generator, operators, descriptors, source/lineage, and retention basis that matter. Claim a changed possibility space only when that stronger claim changes the inquiry. A newly visited region under the same effective generation conditions is exploration, not evidence of expansion. Use C.18 for the earlier and candidate space declarations, changed component, supported mode, evidence, and blocked overread; causal claims require the direct causal result.

Use C.19 — Explore–Exploit Governor when the current 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. The policy may remain unchanged while that treatment question becomes current. Selecting the next local candidate or probe is a different question, as are generating a variant, declaring a selected set, and enacting Work.

Ordinary opportunity retention does not require all those practices. A few descriptions with recoverable reasons and conditions can be enough.

DOCA.6:4.6 - Return a discriminating question and reconsider locally

Name the next question whose plausible answers would retain, narrow, reject, or open a particular opportunity or path. Use the declared receiving policy to consider relevant value, inquiry burden, delay, protections, and uncertainty. Reuse a sufficient partial comparison; no complete ranking is needed merely to state the question.

If the question becomes “which candidate or probe should we choose now?”, return to the actual local choice or PSD decision-support question. A proposed probe needs its own feasibility, exposure, authority, and execution basis before it becomes recommended or performed. An information request is not that authorization.

Revisit at the declared trigger, including a material source, use, horizon, resource, support, permission, or evidence change. Use DOCA.8 to update the smallest affected opportunity and its dependent paths or advice. Preserve unaffected candidates and source lineage; retire a retention claim when its later use disappears, its cost no longer fits, or a qualified result defeats its enabling connection.

Recognition and assurance. A usable account shows what is retained, why, for how long, under which conditions, and what changes next. Whether a path is reachable, a step causes a later possibility, or a retained option will remain obtainable requires the appropriate domain evidence, DOCA.5 qualification, and actual resource or authority basis. The clarity of the account supplies none of those assurances.

DOCA.6:5 - Archetypal Grounding

DOCA.6:5.1 - An index changes the starting point of the later model step

Consider a constructed review-support inquiry over ninety days. The actual case baseline is manual qualification, with sixty minutes per representative case and no separate index-maintenance allocation. A candidate index might reduce this to forty minutes, at two maintainer hours each week and six setup hours. A later retrieval-assisted configuration might reduce it to thirty minutes, with total maintenance of three hours weekly and four additional setup hours.

These are stipulated illustrative estimates under the same representative case type and compatible service assumptions, not observed effects. Data custody, representative verification, acceptance quality, and the feasibility of fitting the transitions within ninety days remain unqualified.

The second transition’s marginal estimate is ten minutes per case, not thirty. A full path comparison against S0 can still be made separately, but it must include the whole path’s transition burden and time-dependent operating costs without counting the first gain again.

The table is not a Pareto-improvement claim: maintenance demand increases and the protection/quality coordinates remain unqualified. Nor does it show that the index enables retrieval merely because it comes first. The relevant engineering result must establish whether the particular index and its data representation are actually reusable for the proposed retrieval configuration.

If that connection is absent, the index can remain a manual-support candidate on its independent contribution, while its stepping-stone claim remains unknown or is rejected. The team returns that exact reuse question rather than treating the three labels as a committed roadmap.

DOCA.6:5.2 - A retained question can cease to be a stepping stone

In another constructed case, a team retains a representative-data access question because its answer could open a bounded model-evaluation route. The local retention policy permits keeping the question and its existing source notes until the data steward answers, at negligible additional burden. It authorizes no processing or trial.

An affirmative, use-specific result would allow the team to qualify that evaluation route’s remaining conditions. A refusal for the proposed processing would close the data-dependent branch. A narrower permission would create a narrower candidate requiring its own receiving-use qualification.

The steward rules out the proposed use. The team retires the stepping-stone claim for that route; saving the historical answer can prevent the same unsupported request from recurring. It retains the independently permitted manual-support direction and the receiving problem. The changed premise does not erase the whole portfolio.

DOCA.6:5.3 - Mira retains directions before choosing a programme

In this constructed case, Mira is exploring review contributions over four months. She keeps two directions: develop more independent review capability, or improve the conditions for supported contribution. The first needs HCD evidence about representative practice, feedback, and transfer; the second needs an actual continuing support arrangement. Both can remain described while those questions are open.

A preliminary exercise is only a candidate stepping stone toward independent review until its enabling relation and feasible development conditions are supported. Being the first item in a course sequence is not that evidence. Retaining its description does not reserve Mira’s practice time or a specialist’s attention.

When direction advice is requested, the bounded engagement and PSD results remain separate from the authorized direction choice. HCD.2 then composes and compares human capability-development programmes when that is the selected question. An optional PSD programme recommendation, authorized programme choice, and Learning Product Guide remain further distinct results. If an adequate programme comparison already exists, the programme-level question can begin there; Mira need not reconstruct an opportunity portfolio to use it.

DOCA.6:6 - Bias-Annotation

Immediate-performance bias can discard a useful stepping stone; novelty bias can retain an attractive but unsupported one. Sunk-cost reasoning can keep a branch alive after its enabling condition disappears. A tidy stage sequence can conceal conditional starting states.

Ask what later use justifies retention now, what continuing burden it creates, and what answer would end it. Keep “worth remembering,” “worth maintaining,” and “chosen to perform” distinct. These distinctions make retention inspectable without guaranteeing future value.

DOCA.6:7 - Conformance Checklist

1. For a retained opportunity or proposed path, MUST bind the subject, receiving use, relevant horizon or horizons, and protected conditions. Retaining material for further inquiry without a known later opportunity uses the C.40 return in :4.2.
2. MUST preserve each retained opportunity’s contribution, conditions, lineage, retention reason, material burden, and revisit or discard condition.
3. MUST distinguish preserving a description from maintaining an obtainable option and identify actual resources or authority where the latter requires them.
4. MUST state the later option or region, enabling transition, and evidence for a stepping-stone claim; a candidate connection may remain explicitly unqualified.
5. MUST describe each material path step from its own starting configuration, finite change, and candidate result, including inherited uncertainty and continuing obligations.
6. MUST preserve step-specific transition burden, reversibility, option effects, and the complete C.11.CRC basis when making finite comparison claims.
7. MUST qualify joint reachability through DOCA.5 or the adequate direct domain result before asserting it.
8. MUST distinguish archive retention, current-front membership, live-pool treatment, local choice, and actual Work when those questions occur.
9. MUST NOT force one scalar winner, universal horizon taxonomy, selected programme, or work permission from a retained set.
10. MUST localize changed-premise effects, retire defeated retention claims, and preserve unaffected independent opportunities.
11. SHOULD return the next discriminating question and keep the account no larger than its receiving use requires.

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

DOCA.6:9 - Consequences

Practitioners can preserve a weaker current candidate for a specific later use without pretending it is best now. A path exposes what each step inherits and which premise would change the next continuation. A defeated branch can be retired without losing the receiving problem or an independent route.

Retention has a cost, even when only attention is scarce. Some later options remain conditional, and stronger claims need domain evidence. The portfolio can inform recommendation or programme work without deciding either.

DOCA.6:10 - Rationale

Immediate comparison and future retention answer different questions. Keeping their reasons separate lets a practitioner avoid both premature elimination and an indefinitely growing list.

Stage-specific configurations make the retained path intelligible. A later step can be valuable because of the conditions an earlier step creates, but that connection and its continuing burdens must be recoverable. Otherwise a path is only an ordered set of attractive labels.

DOCA.6:11 - SoTA-Echoing

Practice question. How can development inquiry retain later possibilities and useful intermediate steps without forcing a current winner or disguising an unqualified sequence as a programme?

Best-known line for this use. Retain candidates for an explicit later use, while comparing each finite step from its own inherited configuration. This pattern adapts C.18’s distinction between archive exploration/stepping-stone value and current-front non-domination in :4.1–:4.2 and :4.5. It adopts C.11.CRC’s finite comparison and option-effect discipline in :4.3. C.19 supplies actual live-pool treatment, not a local next-probe choice.

Serious alternative and trade-off. Retaining only the current front is useful when immediate comparison is the whole question. It loses a presently weaker candidate whose supported enabling relation matters to a later use. Keeping an unrestricted backlog avoids that loss but hides retention costs and defeated premises. At the modest effort of the index case, adding a retention reason and a stage-specific increment exposes both the possible later use and the extra maintenance burden. The cost is reconsidering conditions that a static list ignores; comparative efficiency has not been measured.

Organization-specific source return. Proactive portfolio management in mission-oriented innovation policy, OECD, 2025, sections 2–4, supplies a current answer-bearing line on complementary activities, development-stage dependencies, resource distribution, adaptation, and termination. This pattern adapts those interdependence and reconsideration concerns in :4.1, :4.3, and :4.6. The source’s mission-management scope includes selection and funding; opportunity retention here supplies inputs to those separately authorized moves. It establishes neither a universal three-horizon rule nor a person- or AI-development mechanism.

Limits and reopen. The constructed cases show what must be distinguished; they do not demonstrate future option value or intervention effectiveness. This is not a complete comparison of investment-portfolio or real-options methods. Return such a specialist comparison when the receiving use requires valuation or allocation. Reopen the affected retention rule when a serious alternative preserves the needed possibilities at lower burden, the enabling evidence fails, or the governing use, source, horizon, or resource condition changes.

DOCA.6:12 - Relations

• Receives from DOCA.2–DOCA.4 or adequate direct sources: searched leads, proposed contributions, and direction/support candidates with source lineage.
• Uses DOCA.5 and A.15.9: joint reachability and exact external-result qualification for retained paths and stepping stones.
• Uses C.11.CRC: finite step comparisons, inherited configurations, complete coordinates, transition burden, and future option effects.
• Uses C.18: actual generation, archive, front, descriptor, lineage, and possibility-space claims.
• Uses C.19: treatment of a still-live pool under its declared policy; local choice remains a different result.
• Supplies DOCA.7 and PSD: retained alternatives and conditional paths for an actual bounded advising and decision-support question.
• Returns to HCD.2 and Learning Product: human programme comparison and later Guide realization; authorized choices and performed Work remain separate.
• Uses DOCA.8: affected reconsideration, revision, or retirement while preserving independent candidates.

DOCA.6:End