HCD.10:5 - Archetypal Grounding

HCD.10:5.1 - Four Scheduled Returns Are a Design Example

FoundationsProgramme revisits six selected patterns at weeks 8, 17, 25, and 34. Week 8 returns to F.1 and F.0.1 in a new quantitative source question after about six weeks. Week 17 revisits C.16 and B.5.2 in a manager or engineering case outside the main project. Week 25 combines F.1, C.16, and A.10.1 around sources, measurement, and revision for a configuration question. Week 34 uses F.1, C.16, and C.11 in an integrated case.

These are repeated practice episodes at separated times, so they instantiate a spacing design. They are not an optimal calendar. Each two-week topic also contains an independent variation within the time assigned to return to earlier learning, and the programme records whether the Methods were used in intervening weeks. The later observations therefore occur after delay with continuing practice history; they do not establish retention without intervening use.

Support is selected separately. Week 8 retains references and ordinary tools while reserving five minutes for independent recognition of the question before search. Week 17 permits pattern texts and AI with a short separate internal-core probe. Week 25 retains the same means and records intervening use. Week 34 retains normal equipment for the main task and separates a narrow changed-support fragment. The calendar does not decide retrieval or tool withdrawal by itself.

HCD.10:5.2 - Keep the Thirty-Minute Core Probe and Its Fifteen-Minute Fragment Distinct

The final core probe lasts thirty minutes. Within it, one fifteen-minute fragment is performed while AI is unavailable. The supplied tables and an ordinary calculator remain available. The bounded human action is to recover the specified time or configuration constraint, reject an unsupported release, and propose a supported next move; a large calculation and full written solution are not required.

The no-AI condition applies to that fifteen-minute fragment, not to the entire thirty-minute core probe or the programme’s main task. Normal pattern and AI access remains permitted for the main task. The result records whether the person performed the narrow contribution and what other help was needed. It is a changed-support observation inside the stated probe, not spacing, a universal AI-withdrawal rule, or a retention conclusion. HCD.13 governs the later delay/support interpretation.

HCD.10:5.3 - Vary the Release Case instead of Rewarding Refusal

One practice episode supplies a report for FW7 when FW8 is required; the warranted action is to reject that use. A later variant supplies compatible HW3/FW8/SCHED2 evidence and 24 test hours. Ten changes in three homogeneous batches require 23 hours, so a bounded continuation is supported while demand of twelve leaves a growing queue. Repeating the earlier refusal now fails. With only 22 hours, promising ten changes becomes unsupported again.

The variants change evidence applicability and capacity separately. Their value lies in selecting refusal, continuation, or constraint revision from the current condition, not in increasing difficulty or changing surface context.

HCD.10:5.4 - Stabilize before Interleaving and Fading

A learner who cannot yet compare energy per volume receives a worked example, integrated data, and stable supported practice. The next attempt changes the values but keeps the same operation and source access. Only after the operation is usable are pump explanation, ticket-load comparison, and release-configuration cases mixed when selecting the Method becomes the target.

After a successful independent variant, a detailed cue can be removed while ordinary references remain. If the learner then cannot identify the task at all, the practitioner restores the working entry and one discriminating question rather than removing more help. The progression follows observed action and intended later conditions, not a universal novice-to-expert ladder.

HCD.10:5.5 - Do Not Diagnose Loss from an Inaccessible Source

A later episode appears to show that the learner forgot a configuration rule, but the required current report was not accessible and the old cached report concerns another firmware. More repetition of the rule would not repair the access failure. The practitioner restores or requests the correct source and, when the distinction changes the next action, uses the applicable E.23.CAE differential before deciding whether a capability-development change is needed.