fpf.tools
Library / Human Capability Development Principles Framework
Jump to passage
In this reading
Source · lines 121–137

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 02:22:15 UTC · snapshot created 2026-10-03 03:38:22 UTC · last check 2026-10-03 05:10:10 UTC

HCD-EVIDENCE - Decide what a successful attempt permits you to rely on

Situation: A learner reaches a correct answer after help, or succeeds in familiar work, and someone needs to decide what this permits them to rely on in later work.

Question: Which contribution is supported, under what conditions, and what part of development should change?

First useful result or blocker: A bounded performance conclusion and, when needed, a targeted change to the task or assistance; an unresolved transfer, delay or support question remains separate.

Start with: HCD.11 - Assess Human Performance in Representative Work, using the attempt and its actual conditions. If practice is being conducted, HCD.9 - Perform Deliberate Practice with Feedback preserves the first attempt, supplied help, feedback, correction and retry that assessment needs.

Stop or return: Stop when the available evidence is sufficient for the intended reliance or local revision. Obtain another observation only for a consequential unresolved claim whose evidence can be obtained at worthwhile cost.

  1. Separate the successful product from the person’s contribution. In the constructed APP-HCD-02, a teacher initially helps Learner-L17 reject a release proposal supported by the wrong firmware evidence. That correction is assisted. Two later fresh attempts show L17 detecting the mismatch before a teacher or AI cue, supporting a narrower independent configuration-checking conclusion.
  2. Change the condition relevant to the next use. HCD.12 - Test Transfer to Unfamiliar Work or Learning from a New Source uses unfamiliar work when transfer matters. A compatible release case requires two hours per change plus one hour per batch of at most four changes. Ten changes need 20 + 3 = 23 hours and fit a 24-hour allowance. At 22 hours, ten no longer fit; nine need 18 + 3 = 21. L17’s corrected nine-change answer after feedback supports helped resource adaptation while preserving the earlier configuration result.
  3. Repair the development contribution exposed by that result. HCD.14 - Revise the Human Capability-Development Arrangement from Evidence can replace a cue-led resource exercise with cases requiring both a justified proposal and a justified refusal. It need not discard sound arithmetic or configuration practice. HCD.10 - Choose Whether and How to Vary, Space, Interleave, or Progress Practice uses the attempt history to select a consequential variation, separated return, competing task or assistance change; these are different choices, not a fixed progression.
  4. Open a delay or support question only when it affects reliance. HCD.13 - Test Human Capability Retention and Dependence on Tools or Other Support compares performance after a delay and under changed support with suitable earlier conditions. One delayed attempt with AI also removed cannot isolate the effect of delay from the effect of removing AI. Keep intervening practice and remaining tools visible. An immediate local repair need not wait for this separate investigation.