Library / Human Capability Development Principles Framework
Jump to passage
In this reading

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 10:39:28 UTC · snapshot created 2026-10-03 10:40:04 UTC · last check 2026-10-03 11:25:15 UTC

HCD.7:4.3 - Test Competence, Access, Timing, and Capacity

For each contribution:

  1. Check competence and scope. Obtain evidence suitable for the task and consequence. Familiarity with content, teaching ability, domain judgement, facilitation, and independent assessment are not interchangeable.
  2. Check authority and independence. State who may provide feedback, access confidential data, change a project, judge a protected criterion, authorize a retry, or make the later decision. A helpful participant is not automatically the authorized assessor.
  3. Check actual access. Verify source edition or data, credentials, project permission, environment, tool or model availability, interface, and accessibility during the required window.
  4. Check total and peak capacity. Include preparation, learner contact, review, correction, coordination, disputes, fallback, and competing work. Test the busiest window and the promised feedback interval, not only the total.
  5. Check handoffs and fallback. Make the next provider, due time, result form, and failure signal visible. A fallback is feasible only when its competence, access, capacity, and authority also fit.
  6. Return exact gaps. If a contribution is unavailable, state the blocked practice or evidence use, current supported design, safe interim boundary, and retry condition. Use HCD.8 when obtaining or building that contribution must be compared; a build decision is not a prerequisite to that comparison.

An enabled arrangement can be small: one learner, one task, a source, a teacher feedback window, an assessor, and a fallback. It need not establish a complete institutional service when the bounded use needs less.