Framework boundary, sources and refresh

Covered work and independent entry

The field is constructing development opportunities and bounding development-direction advice. Its recurring questions range from an unformed development wish through characterization, search, worthwhile receiving contribution, supported directions, joint reachability, retained possibilities, advising conditions and changed-premise requalification. Parts organize reading; they add no semantic parent or compulsory order.

Construction uses DOCA.1, DOCA.1.CHR and DOCA.2–DOCA.6 without requiring an adviser. Advising can start with a formed question, qualified opportunity or existing HCD.2 programme comparison. DOCA.1, DOCA.1.CHR, DOCA.5 and DOCA.8 are shared because both branches can depend on the same inquiry, characterization, joint conditions and changed-use qualification. They are not mandatory checkpoints.

The applications preserve a person-to-Guide use, an organization inquiry and unlike subjects. They are examples, not a claim that every domain mechanism has been covered. The common contribution remains useful precisely because its external results are not reclassified as DOCA results.

Results supplied by other practices

Source responsibility and references

The source roles below consolidate the pattern-local SoTA accounts for this edition’s claims. They identify which contribution is adopted or adapted, its limit, and the smallest return after a material change. They do not replace the complete sources or establish a client’s facts. The cited editions and bounded source roles qualify these uses; a changed source or receiving question can require a new source return.

Opportunity, characterization, and retained possibilities

Professional and AI-source qualification

For a concrete currentness episode, suppose an adviser needs to know whether “ICMCI compliant” establishes all required engagement conditions. The identified v4.0 clauses support the bounded involvement/conflict contribution, and the May 2026 AI Code supplies a separate scoped AI-use contribution. Neither closes the broader complete-current-standard claim. The visible 2026 update cue returns that precise claim to the professional source owner; the adviser can retain the identified qualified contributions while withholding the broader assertion. Local legal and professional applicability still needs its own result. A newer label alone supplies none of these conclusions.

Direct frameworks, predecessor sources, and honest omissions

Problem Structuring and Decision Support supplies its direct generic inquiry, comparison, recommendation and follow-up contributions. Human Capability Development supplies personal demand, programme and evidence contributions. OCE.8 supplies whole-arrangement construction and comparison when that same-result question is current. Their use is claim-specific; a bibliography entry is not proof of dependency or client adequacy.

The predecessor opportunity-construction description, advising profile and source-responsibility account remain distinct sources, with their public expressions and access limits identified below. Their construction moves are carried by DOCA.1–DOCA.6, their actual engagement conditions by DOCA.7, and their affected-opportunity return by DOCA.8. Generic recommendation and follow-up continue to return to PSD. The new text alone does not supersede an earlier publication or erase its historical uses.

The Foundations programme and comparison illustrate a programme design considered before a particular person’s development question. A learner-oriented narrative can arrange explanations and practice for learning; a compact pattern body helps a practitioner select a move for a working difficulty. For a particular person’s capability, programme fit or learning result, use the relevant direct practices and observations.

Broader career-design exercises, motivation and learning-science accounts, real-options valuation, investment allocation, complete professional certification, legal/safety compliance and domain implementation are not reproduced here. Their omission is not permission to bypass them when a receiving claim needs them. Return that exact question to its actual current owner.

Requalification and guidance refresh

For a changed client fact, configuration, support, use, horizon or service condition, use DOCA.8 to find the smallest affected opportunity result. Preserve independent qualified uses, historical advice and actual prior configurations. A narrowed data class needs its own quantities and comparisons; a missed necessary observation limits only the reliance that needed it.

For a changed source claim with several receiving uses, A.10.1 supplies bounded discovery and actual dependence before each direct practice qualifies its result. For source currentness, decay or scoped refresh, use G.11. A moved file with unchanged accessible claims can require only a repaired reference; an uninspected receiver or expired reliance window cannot be declared unchanged for convenience.

When a source or practitioner result defeats the guidance itself, send the precise failed move, receiving use, source difference and candidate repair to the responsible framework maintainer. Change only the dependent body, relation, entry or example unless the field or branch boundary is genuinely defeated. Updating a client account is not automatically a framework revision; updating a publication date is not a new qualification.

Reading the references

All nine DOCA bodies are included in this publication. Internal links use GitHub’s native heading fragments. If a Markdown reader uses another heading-address convention, use its document outline or search for the exact heading. Other framework and domain sources remain external. Their public URLs remain usable when this Markdown file is copied elsewhere, provided network access and the supplying publication remain available. This is not an offline-complete source collection.

Use a supplying source for the exact contribution and conditions named by the receiving claim. A working link does not establish that a result fits the subject, configuration, use or horizon. If the source or its necessary qualification cannot be obtained, retain the exact gap and use only independently supported contributions.

FPF source locators

The complete FPF Markdown is available as a raw file. GitHub’s file page may refuse to render the large document. Open or save the raw Markdown in a text or Markdown reader and search for the following PatternID and heading. FPF links in this publication return to that full file, not to a promised rendered fragment.

Use the complete relevant pattern and its conditions, not just the matched title. In particular, A.10.1 supplies bounded changed-source discovery and actual-use qualification; DOCA.8 requires a subject basis before asserting restored qualification, but may finish with a supported limit or compatible reference repair. It does not require a second result record or an unused common summary. A different edition or wording requires comparison of the relied-on contribution when that difference could affect the receiving use.

Learning Product source access

The following sources belong to the Learning Product Development LPF. Their complete texts are not included here, and this publication supplies no verified public retrieval address for them.

Obtain the applicable source from the Learning Product maintainer when its full instruction is needed. LG.05 is marked Candidate in its source LPF; qualify its applicable use before treating it as established instructional guidance. The constructed DOCA application explains the requested design contribution, not the admission of that source. Without the full source or a qualified design result, retain the Guide-design question with Learning Product practice. The opportunity and programme results remain separately usable within their conditions.

Foundations programme source access

ThinkingFoundations + EngineeringFoundations is the programme source; Основания выбора и сравнение программ is its supporting programme-choice and comparison account, with a source-inspection basis of 2 September 2026. They illustrate a programme design considered before a particular person’s development question. Their full working texts are not included here and no verified public retrieval route is supplied.

For that illustration’s complete design and comparison, request both sources from the programme’s responsible designer or maintainer. For an actual person’s programme question, obtain the compatible HCD.2 comparison and the person’s relevant starting conditions, later tasks, support and participation. The illustration supplies none of those individual premises. A different adequate programme comparison can enter the same advice or choice question directly.

Predecessor source-account access

Development-direction profile: source responsibility and local refresh is the full predecessor source account, whose identified qualification window is 2 September 2026. The public PSD section Source responsibility and references supplies a condensed source-responsibility expression, not that complete earlier account.

Use the public section for the contribution it actually states. If a historical qualification or source-use decision depends on omitted detail, obtain the full named account from PSD profile maintenance. The current DOCA source roles above remain the place to recover this publication’s own bounded reliance; neither a condensed expression nor the source’s date supplies an uninspected stronger claim.

A useful stop when access is incomplete

A reader should be able to locate the current question, recover its first useful result or gap, and identify the source or practice that can support the stronger claim. If source access fails, keep the missing premise explicit and preserve independent qualified work. The responsible practice may supply an adequate alternative result, a narrower claim or a blocker. Publication, accessible text, recent dates and well-written examples do not supply the client’s evidence or authorization.