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.
| FPF PatternID | Source heading to locate |
|---|---|
| A.2.3 | U.PromiseContent — Promised Outcomes and Acceptance Criteria |
| A.3.1 | U.Method: Reusable Way of Doing with Explicit Applicability |
| A.3.2 | U.MethodDescription: Description Episteme for a Way of Doing |
| A.10.1 | Revalidate Affected Uses When a Relied-on Source Changes |
| A.15.9 | Use or Request a Bounded Result from Another Practice |
| C.11.CRC | Configuration-Relative Contribution Comparison |
| C.11.DUA | Make Advice and Evidence Demands Worth Their Burden |
| C.16 | Measurement & Metrics Characterization (MM‑CHR) |
| C.17 | Characterising Generative Novelty and Value |
| C.18 | Open-Ended Search Archive and Front Stewardship |
| C.19 | Explore-Exploit Live-Pool Governor |
| C.40 | Develop Branching Search from Reusable Material |
| C.40.CD | Develop Problems and Ways of Solving Them Together |
| E.10.DEV | Recovering What Development or Evolution Means in the Current Claim |
| G.11 | Decide Whether and How to Refresh (Telemetry and Decay) |
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.
| Exact source | Contribution used in APP-DOCA-01 |
|---|---|
| LG.02 - Проектировать длинный учебный маршрут по устойчивым адресам | Place the first distinction, worked use and later varied return along a learning route with stable addresses. |
| LG.03 - Проверять законченный фрагмент руководства по следующему действию учащегося | Check whether a completed Guide fragment supports the learner’s next action and identify the bounded repair. |
| LG.05 - Проектировать учебную единицу, которая учит применять паттерн | Develop a pattern-centred unit around recognition, explanation, action, result/check, a worked case and practice. |
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.