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

This constructed case concerns Mira’s four-month exploration of useful engineering-review Work. Its source packet stipulates permitted example packages and a maximum of two inquiry hours per week. The stipulated review record identifies recurring delays from missing outside-practice premises. Her current ability to recognize those missing premises in representative Work is unknown. Independent acceptance, confidentiality, and sustainable workload remain protected.

One lead is “learn A.15.9.” The direction instead cites the complete A.15.9 body and recovers its contribution:

The pattern supplies guidance for the proposed contribution, not evidence of Mira’s capability. HCD and review-domain practice must establish representative performance, support, and transfer.

Two directions now differ materially:

The candidates do not yet share a qualified same-result comparison: the first proposes development of independent recognition; the second proposes supported result use. The next question is which contribution the receiving review needs and what HCD or supplier result can qualify the corresponding transition. Combining them creates another candidate whose joint time and support need testing.

The result is two conditional directions, not a learning programme or recommendation. If one is later chosen, HCD.2 can supply programme candidates and comparison. Any requested programme recommendation and authorized programme choice remain separate; only then can Learning Product realize the appropriate Guide. The person can also stop now with the conditional directions and the support limits that matter; an exact support request is a further selected contribution.

DOCA.4:5.2 - A faster retrieval candidate is not a cost-free improvement

This constructed example stipulates a service unit’s actual manual qualification arrangement and an engineering estimate for a possible indexed arrangement over a ninety-day horizon. The result premise is fixed: a source-traceable claim-to-evidence account under the same acceptance criteria. The candidate does not replace independent acceptance. Review capacity and scarce index-maintainer capacity are separate resource coordinates.

The finite change is adding and maintaining the index, not merely subtracting twenty minutes. Discarding the index could reverse its future use but would not recover spent setup time. A later model-assisted retrieval candidate would start from whichever configuration is then actually assumed, including its index-maintenance burden; it cannot reuse today’s S0 silently.

The return is a conditional configuration and two decisive questions: can the access owner qualify the proposed custody/use, and can the unit supply setup, verification, and maintenance without violating protected continuing Work? Even if latency improves, the resource increase prevents a no-worsening Pareto claim. C.11.CRC supplies the finite-comparison discipline; DOCA.5 must qualify the joint premises before a stronger reachability claim. The illustrative numbers establish no measured effectiveness.

DOCA.4:5.3 - The AI subject is the arrangement being changed

A team says “improve the model,” but its receiving-use failure may arise from the retrieval corpus, tool permissions, escalation path, or operating support. The team constructs a parameter-change direction and a changed-retrieval-and-oversight direction, each naming its model edition, data, tools, evaluation, and environment.

A bare-model benchmark does not by itself qualify either tool-enabled arrangement. The receiving engineering and evaluation practice must establish any transfer basis for the intended configuration, characteristic, and use under DOCA.1.CHR:4.5. Otherwise the reading remains unknown and the direction retains that limit. A corresponding request follows only when its obtainable contribution warrants acquisition. Human curriculum or learning-transfer evidence does not qualify either AI change.

DOCA.4:5.4 - Direct same-result arrangement work is enough

An organization already has a stable contribution and acceptance basis, adequate baseline evidence, and whole manual, internal-specialist, and provider arrangements. It does not reopen development-direction construction merely because the arrangements could be given development labels. OCE.8 owns the remaining organization comparison and lawful disposition; the necessary authority and specialist results still have to be present.

DOCA.4:6 - Bias-Annotation

• Label concreteness: naming a course, tool, person, or PatternID feels more specific than the contribution it actually describes.
• Capability default: an access or support limitation is treated as a need to develop the holder.
• Fragment parity: a fully supported direction is compared with an advertised fragment.
• Benefit-only comparison: transition, maintenance, distribution, or protected conditions disappear behind a desired gain.
• Combination optimism: attractive components are presumed to work together despite shared capacity or incompatible premises.
• Baseline drift: later steps are compared with the original situation instead of their actual assumed starting configurations.
• Learning-route projection: a prospective contribution path is mistaken for a selected programme or a Guide.

DOCA.4:7 - Conformance Checklist

A conforming direction/support account:

1. MUST name the subject/configuration, receiving contribution and use, horizon, acceptance expectation, protections, and actual or relied-on starting condition.
2. MUST describe the useful move and first result rather than only a label; a pattern-based direction must preserve its complete cited contribution and applicable conditions.
3. MUST preserve established Method/MethodDescription relations when relied on and must not infer them from a title or publication alone.
4. MUST state what makes retained directions materially different and whether their contribution premises are the same or different.
5. MUST identify the finite change, candidate configuration, material supports, prerequisites, constraints, interactions, and transition basis.
6. MUST preserve result, resource, affected-System/distributional, and explicitly protected coordinate families for finite comparison, with each coordinate’s declared scale and polarity under a common comparison basis.
7. MUST state transition burden, reversibility, and supported or conditional option effects; a later compared step must use its own starting configuration.
8. MUST keep unknown support and ruled-out support different and return the missing owner-qualified result before asserting realizability or joint reachability.
9. MUST NOT claim Pareto improvement when any coordinate in the complete set worsens or its necessary qualification is absent.
10. MUST distinguish a direction or path from a recommendation, choice, programme, Guide, performed Work, or observed effect.
11. SHOULD retain a serious baseline, smaller repair, or no-new-development direction and stop when the next missing result belongs elsewhere.

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

DOCA.4:9 - Consequences

Practitioners obtain directions that another person can inspect, challenge, and qualify. A capability-development route can coexist with a support repair or external contribution. The next inquiry becomes precise: which access, feedback, transition, resource, or protection premise changes this candidate?

The cost is recovering the baseline and enough support detail to expose interactions. Some attractive labels become conditional fragments, and the comparison may remain indeterminate. A commitment may have to wait while the responsible practice supplies the necessary result.

A constructed direction remains a possibility. Realization, authority, programme design, evaluation, and later observed effects retain their own requirements.

DOCA.4:10 - Rationale

A contribution and its support jointly determine what a proposed change means. A course without representative practice, a model without permitted data, or a provider without a usable interface can be a relevant ingredient without being a way to obtain the contribution.

Finite changes and stage-specific baselines make hidden burden visible. They let a receiver retain a useful possibility while identifying the exact condition that prevents a stronger claim, and they prevent a gain at one stage from being counted again in every later step.

DOCA.4:11 - SoTA-Echoing

Practice question. How can a development direction become a contribution-bearing possible change without treating a course, tool, or pattern label as a complete and reachable intervention?

Best-known line for this use. Construct the contribution and support together, then apply finite configuration-relative comparison. Current OCE.8 supplies whole-arrangement construction and comparison when one organization result premise is stable. C.11.CRC supplies actual S0, finite change, realizable S1, complete coordinates, transition basis, and option effects. This pattern adapts their contributions in :4.3–:4.6 for development inquiries that may still retain different contribution premises. Current HCD and other holder practices retain the change mechanisms and evidence.

Serious alternative and comparison. A course or product catalogue is cheaper when the missing contribution and all material supports are already known. When they are not, it omits the difference between developing capability and making an existing capability usable. At the bounded effort of the Mira case, two contribution/support descriptions expose different evidence and provider needs; ranking two course brands would not do so. OCE.8 is the stronger direct alternative once same-result organization arrangement comparison is the whole question. Use OCE.8 directly for that same-result question; no additional opportunity-construction pass is needed.

Front-end boundary. ISO 56007:2023 supplies normative guidance for opportunity/concept work before solution development and deployment. Here that boundary supports prospective configurations and truthful gaps; it supplies no missing support, implementation, or effect evidence. A complete cited pattern contribution similarly supplies guidance, not holder capability.

Trade-off, limits, and reopen. The selected account costs more than naming an intervention but less than designing and qualifying every implementation. Its constructed cases demonstrate distinctions, not comparative effectiveness. Reopen the affected move if current holder or configuration practice preserves the contribution, complete consequences, and necessary support with less burden; if a relied-on comparison or source changes; or if a real use reveals a consequential omitted interaction or transition.

DOCA.4:12 - Relations

• Receives from DOCA.1, DOCA.1.CHR, and DOCA.3: the bounded inquiry, relevant characterization, and worthwhile problem/proposed-contribution premise; equivalent direct results suffice.
• Uses A.3.1 and A.3.2: identification of Method and MethodDescription when a direction relies on those relations; a PatternID remains a locator for the complete contribution.
• Uses PSD.8: finite alternatives for the receiving decision-support question, including alternatives addressing different formulations.
• Uses OCE.8: whole same-result organization arrangement comparison once its result/use/acceptance premise is stable.
• Uses C.11.CRC: finite contribution comparison under one basis with complete coordinates, transition burden, reversibility, and option effects.
• Supplies DOCA.5: direction/support candidates and the material premises whose joint qualification changes reachability.
• Supplies DOCA.6: contribution-bearing finite steps and their stage-specific baselines for retention, paths, or branches.
• Returns to HCD, organization, strategy, AI, engineering, operations, and other direct practices: their interventions, mechanisms, capability, support, evidence, authority, and realization results.
• Returns human programme and Guide work: HCD.2 composes and compares programmes; authorized participants choose; Learning Product realizes the selected programme and pattern contributions as a Guide.
• Uses DOCA.7 and DOCA.8: an advising boundary when advice is requested and local requalification of changed directions or supports.

DOCA.4:End