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 05:29:54 UTC · snapshot created 2026-10-03 05:30:57 UTC · last check 2026-10-03 06:25:20 UTC

Part of a long section. Showing characters 1–59282 of 825663. Continue below for the remaining text.

Part I — Human Capability Demand, Programme, Practice, Evidence, Continuation, Repertoire, Culture, Learning Products, and Shared Tasks

HCD.1 — Derive Human Capability Demand from Representative Later Work

Type: Human Capability Development practitioner method pattern Status: Stable

HCD.1:0 - Use This When

Use this pattern when someone asks what a named person must become able to contribute in later Work and the available request is still expressed as a job title, competency list, course request, platform score, MethodDescription, or technology rollout. Begin with the exact human holder and representative later Work, not with a learning product.

The first useful result is a human capability-demand account recording which contributions that person needs to make in the named Work family, configuration, conditions, and horizon for the receiving decision. When the future Work is well framed but current evidence is not yet available, return a prospective demand hypothesis and the observations to obtain. When the question belongs to a clinical, target-domain, authority, organization, assignment, access, tool, or nonhuman-capability owner, return it there. When a conclusion consumes evidence that is absent, name each missing value and its retry predicate instead of calling the gap a learning need.

The practical gain is a demand that can guide diagnosis or profile comparison without pretending that training has been selected or that capability has already been observed. Use HCD.3 when the demand is known and the question is which changeable human limitation, if any, is supported. Use HCD.4 when the demand is known and simultaneous capability claims must be compared. A separate programme comparison (HCD.2) may use the account; deriving demand does not select a programme.

Do not use HCD.1 to prescribe diagnosis, treatment, curriculum, provider, employment action, safety judgement, release decision, or target-domain correctness. Those decisions remain with their direct owners.

HCD.1:0.1 - Working Terms

Name in this patternWhat it denotes
human holderOne identified human person whose capability demand is being considered. A role, cohort, roster, demographic category, or population is not that person.
later WorkA named family of future or recurring U.Work occurrences in which that person may contribute under stated conditions.
representative caseA case selected to examine a material variant of later Work, such as unfamiliar content, changed support, or a specialist interface. Its suitability depends on the conditions it represents and the conclusion for which it is used.
human capability demandThe contributions this person needs to be able to make under the named later-Work conditions. A demand account records those requirements; it does not establish the person’s current capability.
demand claimA statement that this person needs to be able to make a specified contribution under the named later-Work conditions, with the evidence for that requirement, uncertainty, and limits.
prospective demand hypothesisA provisional account of future demand grounded in a supported future-Work frame. It states which demand claims remain provisional and which observations could qualify or revise them.
demand-evidence-blockedA result that names each missing input, the conclusion it blocks, and the condition for retry. It also distinguishes available material from the missing input when that material could mislead the receiver.
outside-HCD returnA return of the current question and available evidence to the direct clinical, target-domain, authority, organization, assignment, access, tool, or other owner.

The account records what later Work requires of the person. Evidence about present capability, causes, learning, or intervention effectiveness answers different questions and uses its own pattern.

HCD.1:1 - Problem Frame

Human development is often commissioned from a visible carrier: a course catalogue, certification, role framework, AI platform, assessment dashboard, or manager’s request. Those carriers can be useful, but none identifies by itself what a particular person must contribute in later Work.

Later Work is configured. The same named task can require different contributions when the product configuration, Method, information access, AI support, time, authority, specialist interface, or critical-error boundary changes. Assisted performance may also conceal which contribution belongs to the person and which belongs to a tool, another Agent, or an organization.

Demand therefore has to be recovered from representative Work and its intended result. Current observations are valuable, but future planning sometimes precedes an actual Work occurrence. The method must support honest prospective hypotheses without silently upgrading plans or demonstrations into current evidence.

HCD.1:2 - Problem

A role-first or course-first description bundles unlike things. It can call a missing Method, inaccessible source, broken tool, absent specialist result, poor assignment, unsafe workload, or organizational constraint a human skill gap. It can also average across a population and then assign the average to one person.

The reverse mistake is to refuse any demand account until the exact future Work has occurred. That discards useful architecture and delays the observations that would test it. The practitioner needs a result that distinguishes what can be framed now, what is qualified now, what belongs elsewhere, and exactly what evidence blocks the stronger conclusion.

HCD.1:3 - Forces

  • A short role label is easy to communicate, while the consequential demand usually lives in case variants, interfaces, and error boundaries.
  • A MethodDescription can make intended Work inspectable, while only enactment or qualified representative evidence supports claims about obtaining Work and its results.
  • Current task success is visible, while later transfer and unfamiliar variants must be established rather than presumed.
  • AI and other supports can improve the joint result, while assisted output is not automatically human capability.
  • Population summaries help allocation, while a person-specific decision requires a person-specific holder and compatible evidence.
  • Missing evidence should stop false certainty, while a useful prospective hypothesis may still guide observation.
  • HCD can organize demand evidence, while target-domain correctness, specialist judgement, assignment, safety, release, and employment authority stay elsewhere.

HCD.1:4 - Solution

Derive demand claim by claim from representative later Work. Preserve the truth posture of every case and source, separate human contributions from surrounding conditions and other owners, and return the strongest conclusion that the evidence supports.

HCD.1:4.1 - Pattern-Use Unfolding

  1. Fix the use boundary and holder. Name the exact human person, receiving decision, later-Work family, subject configuration, effective horizon, and evidence window. If the question concerns a population, identify the separately observed members or representative accounts; do not manufacture one aggregate holder.
  2. Recover the later-Work basis. For every case, distinguish what was observed from what is planned, stipulated, or assumed. Explain which later Work and material conditions the case represents, and why its evidence is suitable for the intended conclusion. Recover the intended result, quality and critical-error predicates, Work products, and stopping conditions.
  3. Recover Methods and direct-owner inputs. Identify applicable target Methods or MethodDescriptions, specialist results, assignments, authority, access, environment, tools, and supports. A missing nonhuman value remains a missing nonhuman value; do not rename it a learning gap.
  4. Select representative cases. Cover the variants that can change demand: familiar and unfamiliar situations, allowed and withdrawn assistance, time or workload limits, AI-output challenge, coordination interfaces, specialist-return conditions, and material quality or critical-error boundaries.
  5. Derive human demand claims. For each case, state which contribution the named person must be able to make for the intended result under the protected conditions and why the evidence warrants that requirement. Contributions may include, for example, noticing a signal, handling an object, coordinating a specialist return, or justifying a decision. Record required tools and supports as conditions of the contribution. Keep each contribution distinct from the Method, task, tool output, team result, or personal trait.
  6. Bind evidence and uncertainty. Relate each demand claim to the cases, observations, work products, inference rule, uncertainty, and remaining observation. Keep instruction events, learner events, learning outcomes, later transfer, and job performance distinct; one does not establish the next by label alone.
  7. Return a conclusion-specific disposition. Emit qualified current demand, prospective demand hypothesis, outside-HCD return, or demand-evidence-blocked. Different questions may lawfully receive different dispositions in one use—for example, a prospective hypothesis for future framing and a blocker for qualified current demand.

HCD.1:4.2 - Record the Result

A human capability-demand account contains these result positions:

Result positionRequired content
use boundaryHuman holder, receiving decision, later-Work family, configuration, effective horizon, evidence window, and direct owners whose results or authority matter.
later-Work basisCases, what was observed or remains planned, stipulated, or assumed, and the later Work and conditions they represent; reasons the evidence is suitable for the conclusion; intended result, quality and critical-error predicates, Work products, and stop conditions.
protected conditionsAllowed or required tools, AI posture, information access, time, environment, assignment, authority, supports, and specialist interfaces.
demand claimsStatements of the human contributions required in the named later Work, including material interfaces among simultaneous contributions. Derive these requirements from the cases rather than assigning capability from job labels or traits.
evidence accountEvidence and inference for every demand claim, uncertainty, incompatible evidence, and the observation or case still needed.
external gapsMissing Method, description, specialist return, assignment, authority, access, environment, or nonhuman capability kept under its own kind and owner.
dispositionOne conclusion-specific qualified current demand, prospective demand hypothesis, outside-HCD return, or demand-evidence-blocked.
continuationCompatible inputs that HCD.3, HCD.4, or a future programme comparison may consume, plus scope limits and reopen conditions.

A demand-evidence-blocked result records one row per absent consumed value:

Missing-value fieldRequired content
missing kindFor example later-Work-occurrence-missing, later-Work-result-claim-missing, result-record-missing, representative-observation-evidence-missing, or a named external supplier result.
blocked conclusionThe exact conclusion that cannot be supported without this value.
available non-substitute, when relevantIf available material could plausibly be mistaken for the missing input, name it and explain why it cannot fill this gap. Otherwise omit this field.
retry conditionThe input that must become available or be confirmed before reconsidering the named conclusion. State its required connection to the person, Work, and conditions, using only qualifiers that affect that conclusion.

Do not infer result-record-missing when qualified direct observations are sufficient for the conclusion. Conversely, an orphan record does not establish that Work occurred or produced the result described in the record.

HCD.1:4.3 - Population and Reuse Boundary

A population use may return a distribution over separately identified member or representative demand accounts. It does not create one person’s demand by averaging, and it does not turn the population into a capability holder. A population whole qualifies as a holder only through the independent-System condition of E.23.CDI, outside this one-human-holder pattern.

Any downstream use must preserve the same human holder, configuration, later-Work conditions, effective horizon, compatible evidence window, and receiving decision. HCD.3 may consume the account as evidence input; HCD.4 may consume it as a scope and result frame. Programme comparison (HCD.2) may use the same frame. Deriving demand requires no programme-comparison result.

HCD.1:4.4 - What Changes in Practice

A practitioner stops asking, “Which course matches this role?” and first asks, “What must this person contribute in which later Work, under which conditions, and what evidence makes that demand current?” The answer either supports a bounded demand, makes a future hypothesis testable, returns the question to its owner, or exposes the exact missing evidence.

HCD.1:5 - Archetypal Grounding

HCD.1:5.1 - Constructed Positive Case: ImpactReview-17

ImpactReview-17 is a constructed pedagogical case. Its answer key, ImpactReview-17-Domain-Oracle-v1, supplies the engineering correctness and criticality criteria for PumpWorks-Config-Baseline-42 and AI-Assist-M4. The review events and evidence below are stipulated case data.

The human holder is Engineer-P14. The later-Work family is independent review of AI-proposed change-impact claims for mixed physical/software pump-controller changes before separate integration, assurance, and release decisions. The constructed 2026-Q4 conditions include the named configuration and AI assistant, current source access, a forty-five-minute case limit, recoverable audit records, and bounded safety and maintenance specialist returns. Final integration, safety, release, and employment authority remain with their direct owners.

The stipulated work permits a routine reminder to construct and test an alternative configuration hypothesis. The engineer must supply that hypothesis and its test; neither another person nor the AI may supply the case-specific rival or rejection decision. Remembering to initiate the operation without a reminder is a separate, stronger question.

The evidence packet stipulates eight representative review occurrences: four familiar and four unfamiliar variants; four include a plausible but wrong AI dependency claim; two require a specialist return; and every case requires a recoverable audit record. HCD.1 returns this human capability demand for Engineer-P14:

  • recognize when the independent-review Method applies;
  • trace each release-affecting claim to the current source and configuration;
  • independently challenge plausible AI output rather than treating supported output as the person’s contribution;
  • request, delimit, and preserve required specialist returns;
  • return auditable evidence; and
  • detect every seeded safety-critical omission within the protected time and authority boundary.

Within this example, the stipulated criteria and observations support qualified current demand for Engineer-P14. The case shows how to derive required human contributions from representative Work; demand does not establish the person’s current capability. Operational use needs qualified current target-domain criteria, safety or specialist inputs, and representative evidence for the actual person and Work.

HCD.1:5.2 - Missing Case: ReleaseWork-R9

For Engineer-E27, the accepted architecture supports a prospective demand hypothesis for 2026-Q4 ReleaseWork-R9: AI-output challenge, configuration-impact reasoning, evidence return, specialist coordination, critical-error detection, and adaptation across unfamiliar mixed physical/software variants may be required. This hypothesis guides observation; it is not qualified current demand.

The stronger conclusion is blocked by distinct absent values:

Missing valueBlocked HCD.1 useNon-substitute and retry
XRI-21-supplier-result-missingAny demand claim that consumes current engineering-culture enactment, its bounded practice-change decision, retained alternatives, or evidence gaps.The current SYSE.21 MethodDescription and its constructed PumpWorks demonstration can shape questions but are not an obtaining supplier result. Retry with a compatible obtaining SYSE.21 result—or a receiver-permitted qualified direct substitute—for Engineer-E27, the Method, Work, period, and evidence use.
later-Work-occurrence-missingTreating ReleaseWork-R9 itself as current later-Work evidence.A plan, architecture, MethodDescription, or constructed occurrence does not establish enactment. Retry when an admitted performed Work occurrence identifies Engineer-E27, configuration, period, and actual performer.
later-Work-result-claim-missingAny demand claim whose evidence consumes the occurrence-produced result, quality, error, or consequence.A planned result or demonstration result is not the occurrence’s result. Retry with the produced result or a supported direct claim tied to the admitted occurrence.
result-record-missingAny record-dependent inference about that occurrence or result.An orphan document would not establish the Work or result. Retry when a current result record links the admitted Work occurrence to its produced result; omit this requirement where qualified direct observations are sufficient.
representative-observation-evidence-missingUpgrading the prospective hypothesis to qualified current demand.A target repertoire, curriculum, course completion, platform score, or constructed case is not representative observation evidence. Retry with holder- and condition-compatible observations or a named qualified representative case set covering performed Method, configuration, work products, quality and critical errors, AI/support posture, specialist returns, variants, and evidence window.

These rows do not collapse into “insufficient data.” Each names a different missing input, blocked conclusion, misleading substitute, and retry condition. Recovering one row changes only the conclusions that consume it.

HCD.1:5.3 - Unlike Case: Clinical Ownership

Return an adult’s request for treatment of social anxiety to a qualified clinical specialist as an outside-HCD return. HCD.1 may address a separately posed, legitimate question about that person’s non-clinical participation in later Work, supplied by the person or qualified clinical owner. Diagnosis, treatment choice, provider competence, safety, consent, and clinical outcome interpretation remain with the qualified clinical route.

HCD.1:6 - Bias-Annotation

Recurring biasLikely driftRepair
training-solution biasThe requested course or certification is treated as the demand.Recover the human holder and representative later Work before considering any learning product.
role-average biasA job-family profile is assigned to one person or one population average is reified as a person’s demand.Keep holder-specific accounts and report population distributions separately.
current-arrangement biasToday’s Method, tool, or division of labour is assumed to be the only future demand.Name the effective horizon, alternatives, supports, and configuration; preserve prospective uncertainty.
technology biasAI-assisted or tool-supported output is attributed to the human holder.Separate human, tool, specialist, team, and organization contributions and test material support conditions.
evidence-convenience biasCompletion, self-report, platform prediction, MethodDescription, or visible document substitutes for later-Work evidence.Trace each demand claim to representative cases, observations, inference, uncertainty, and remaining evidence.
human-deficit biasMissing access, authority, assignment, Method, environment, specialist result, or nonhuman capability is called a skill gap.Return the value under its actual kind and direct owner.
occurrence maximalismNo future question is allowed until the exact Work occurs.Return a prospective demand hypothesis with observations-to-obtain, while blocking only the stronger current conclusion.

HCD.1:7 - Conformance Checklist

  • One exact human person is named as holder; any population use preserves member or representative accounts.
  • The later-Work family, configuration, effective horizon, evidence window, and receiving decision are explicit.
  • Each case distinguishes observed facts from plans, stipulations, and assumptions, and explains which later-Work conditions it represents and why its evidence is suitable for the conclusion.
  • Intended results, quality and critical-error predicates, protected conditions, tools, supports, and specialist interfaces are recoverable.
  • Each demand claim names a human contribution supported by representative Work rather than a job label, trait, task, MethodDescription, or course.
  • Human, AI, tool, specialist, team, organization, assignment, authority, and environment contributions or gaps remain distinct.
  • Each demand claim has evidence, an inference boundary, uncertainty, and any observation still needed.
  • The result uses one conclusion-specific disposition and does not suppress a lawful prospective hypothesis merely because qualified current demand is blocked.
  • Every blocker names the missing input, blocked conclusion, and retry condition; available material is distinguished from that input when it could mislead the receiver.
  • Downstream reuse preserves holder, configuration, conditions, horizon, evidence window, and receiving decision.
  • The first result selects no curriculum, provider, intervention, assessment programme, treatment, safety action, release action, or employment action.

HCD.1:8 - Common Anti-Patterns and How to Avoid Them

Anti-patternWhy it failsRepair
“The role requires these competencies”The role label hides case variants, conditions, and the exact holder.Derive claim-sized contributions from representative later Work for the named person.
“The course objective is the capability demand”A learning-product intention is not a later-Work result.Start with later Work and let a future programme comparison answer the demand.
“The MethodDescription proves the Work”A description states an intended Method; it does not establish enactment, result, or observation.Preserve its use as a question frame and recover the missing occurrence or qualified representative evidence.
“The tool score is the person’s capability”The score may describe joint or model-dependent performance.State support conditions and recover direct task evidence and inference limits.
“One missing record means no evidence exists”Direct observations may support the conclusion without a record, while an orphan record may support nothing about the occurrence.Name the evidence actually consumed and require a record only for a record-dependent use.
“The average employee is the holder”Aggregation erases person, condition, and evidence identity.Keep individual accounts or an explicit distribution; use E.23.CDI before treating a population whole as holder.
“HCD.2 must come next”Numbering is mistaken for a lifecycle and invites premature programme design.Route independently to HCD.3 or HCD.4 when their qualified inputs exist; programme comparison needs its own qualified basis and decision.
“Poor outcome means training”Method, tool, assignment, access, organization, nonhuman capability, or specialist causes may dominate.Return those values to their owners and use HCD.3 only when a diagnostic question remains.

HCD.1:9 - Consequences

The organization gains an inspectable demand account that can support diagnosis, profile comparison, evidence collection, or later programme comparison without making those later decisions in advance. Prospective planning remains possible, and missing evidence becomes a substantive return rather than an administrative “TBD.”

The cost is more careful case selection and relation keeping. Demand may vary across configurations, supports, horizons, and holders; some visible requests will return outside HCD. Evidence collection may reveal that the main constraint is not human capability.

HCD.1:10 - Rationale

Beginning from representative later Work preserves the direction of justification: intended results and conditions constrain the required human contributions; learning products do not invent their own demand. Holder identity prevents a role model or cohort aggregate from masquerading as a person’s capability.

The four dispositions avoid a false choice between unsupported certainty and silence. A prospective hypothesis is useful for future framing, while a discriminated blocker protects a stronger current conclusion. Keeping external gaps under their own kinds prevents HCD from taking authority over target Methods, specialist results, assignments, safety, release, or employment.

HCD.1:11 - SoTA-Echoing

The working question is: How should a practitioner derive a human capability demand that is useful for later development decisions and still warranted by later-Work evidence?

The selected current line combines representative-work analysis with the workplace-instruction evidence chain summarized by Kraiger and Ford’s 2021 review (COG-10): instructional events, learner events, learning outcomes, transfer, and job performance must be distinguished, and claims about each need corresponding evidence. Transfer must be established under material learner, design, opportunity, support, and work-environment conditions. Direct target-domain evidence supplies what counts as correct, safe, critical, or useful in the actual Work. Where AI assistance is material, Dell’Acqua and colleagues’ Navigating the jagged technological frontier (AI-03) supplies a bounded cue to test independent error detection under the named task and model conditions. It establishes neither a universal AI-task boundary nor this person’s engineering capability.

A serious operational alternative is a role-first competency framework or training-needs inventory. It is cheaper to publish and supports broad workforce communication, but it commonly loses holder identity, representative case variation, tool and specialist interfaces, critical-error predicates, and the distinction between a learning outcome and later performance. HCD.1 retains those inventories only as discovery cues and mutates them into evidence-bound claim rows.

The selected line does not establish one universal demand, transfer trajectory, or intervention for ReleaseWork-R9. It also cannot supply target-domain truth. Reopen a demand claim when its holder, Work family, Method, configuration, support posture, quality or critical-error predicate, effective horizon, evidence window, direct source, or receiving decision changes. A later stronger source reopens only the claims whose move or limit it changes.

HCD.1:12 - Relations

  • A.15.1 and current Work ontology: keep Method, Work occurrence, performer, result, and result episteme distinct.
  • E.23.CDI: governs whether a population whole is an independent System capable of holding capability; HCD.1 otherwise stays at one-human-holder granularity.
  • E.23.CAE: supplies capability-evidence boundaries for downstream observations; evidence does not itself authorize intervention or employment action.
  • COG-10: supplies the event-to-transfer distinction and the requirement to qualify workplace opportunity, support, and environment.
  • Dell’Acqua and colleagues, Navigating the jagged technological frontier (AI-03): supplies the bounded independent-error-challenge cue where assisted Work makes that contribution material.
  • Target-domain Methods and results: determine correctness, quality, criticality, and specialist boundaries. HCD.1 consumes them; it does not replace them.
  • SYSE.21 / XRI-21: an obtaining compatible cultural-continuation result may supply later-enactment observations, a bounded practice-change decision, retained alternatives, and evidence gaps. Its MethodDescription or constructed demonstration is not that supplier result.
  • HCD.3: may consume a compatible HCD.1 account as evidence input for a limiting-capability or non-training disposition; no target is entailed.
  • HCD.4: may consume a compatible HCD.1 account as the scope and result frame for a condition-qualified profile comparison; no mastery or choice is entailed.
  • Programme comparison (HCD.2): may consume the compatible demand account and evidence needs. HCD.1 derives demand without selecting a programme or requiring a programme-comparison result.
  • Clinical, safety, legal, employment, specialist, organization, provider, and release owners: retain their direct decisions and authority.

HCD.1:End

HCD.3 — Diagnose Whether a Capability, Misconception, or Behaviour Limits Work

Type: Human Capability Development practitioner diagnostic pattern Status: Stable

HCD.3:0 - Use This When

Use this pattern when a named person’s later-Work demand is already recoverable, performance is inadequate or unstable, and different explanations would lead to different next Work. Begin by comparing the smallest rival set that could change the decision; do not begin by assigning training, practice, coaching, motivation work, or treatment.

The first useful result is either a qualified intervention target—the smallest changeable human limitation supported by current evidence—or a non-training return to the owner of the actual constraint, specialist question, or missing result. A target names what is supported, any still-plausible rival explanations, the conditions protected during observation, and what later observation could reopen it. A return names the blocked HCD decision and an exact retry condition.

The practical gain is stopping generic development Work before it consumes time or harms the person. Use HCD.1 when the later-Work demand itself is unclear. Use HCD.4 after a compatible demand and claim-level evidence exist and simultaneous capability claims must be compared. A separate programme comparison (HCD.2) may use a target or another qualified basis; HCD.3 stops at the target or non-training return.

Do not use this pattern to diagnose a medical disorder, prescribe a clinical or learning intervention, declare that development occurred, authorize surveillance, assign Work, or make safety, employment, provider, or treatment decisions.

HCD.3:0.1 - Working Terms

Name in this patternWhat it denotes
diagnostic questionA bounded question about which live explanation best accounts for an observed later-Work gap and would change the next Work. It is not a medical diagnosis.
rival branchA materially different explanation whose survival changes the next observation, owner, or development question.
human limitationA difficulty this person has in making a required contribution under the named later-Work conditions. Current evidence supports treating that difficulty as changeable and relevant to the decision.
qualified intervention targetThe smallest supported human limitation, with evidence, any still-plausible rivals, conditions, intended observation, specialist boundary, and reopen condition. “Intervention target” names what a later choice might try to change; it selects no intervention.
non-training returnA return to the owner of a nonhuman constraint, specialist question, or question outside the demand envelope; or a return naming evidence needed before a human target can be justified.
protected conditionA condition held stable or bounded so that an observation can discriminate rivals without quietly changing the holder, task, tool, authority, or support arrangement.
observed target changeA difference in the selected target between observations under stated conditions. It can inform the next development decision before its cause is established.
target engagementA change in the selected target attributable to an intervention. Evidence must concern that target and justify the attribution; a theory label or assigned activity does neither.

The diagnosis concerns the person’s difficulty making the required contribution under the named conditions. A low score, poor result, behaviour label, or inferred latent state can inform the diagnosis but does not by itself show what human change would help.

HCD.3:1 - Problem Frame

When Work goes badly, the visible human is often the easiest place to intervene. Yet the same observation can arise because the demand was wrong, the Method or source was missing, a tool or cue changed, the assignment or authority failed, workload or recovery was inadequate, a specialist return was absent, the response was not recognized as applicable, or the person’s capability really is limiting.

These branches have different owners and remedies. More practice can be useless when the task lies outside the claimed envelope, unsafe when a clinical or safety condition is current, and misleading when assistance or prompt design controls the result. Conversely, an endless list of possible causes is not a diagnosis. The comparison must become small enough to change a decision.

HCD.3:2 - Problem

The common shortcut is to transform “the result was poor” into “the person needs training.” It hides the evidence chain, turns a familiar intervention into a cause, and exposes the person to monitoring or employment consequences without a justified target.

The opposite shortcut refuses any bounded target while uncertainty remains. That makes practical diagnosis impossible even when controlled observations have eliminated the decision-changing rivals. The practitioner needs a conservative result that can name one qualified target, record the explanations considered and any still-plausible alternatives, and return questions for other owners. Eliminating the considered rivals leaves the stated evidence limits and reopen conditions in force.

HCD.3:3 - Forces

  • A familiar human explanation is actionable, while Method, tool, authority, organization, environment, or specialist constraints may be more decisive.
  • One observation is cheap, while a target must survive the rivals that would change the next Work.
  • A controlled probe improves discrimination, while the probe can teach, prime, fatigue, expose, or otherwise change the person.
  • Assisted performance reveals a joint result, while the human limitation may concern applicability, access, adaptation, enactment, or independent challenge.
  • Motivation language is easy to apply, while change in the proposed target needs evidence beyond a theory label or assigned technique.
  • A narrow target supports later design, while a diagnosis that is too broad becomes a trait label or a curriculum in disguise.
  • Useful evidence can be collected, while privacy, consent, worker governance, clinical safety, and employment authority constrain collection and use.
  • A specialist boundary protects the person, while HCD must still preserve any legitimate non-clinical Work question.

HCD.3:4 - Solution

Compare the coarsest decision-changing rival branches, run only safe and qualified observations, and return the smallest human limitation justified by the current evidence—or return the question to the owner of the surviving non-training branch.

HCD.3:4.1 - Bind the Diagnostic Use

Name:

  1. the exact human holder and participating basis;
  2. the HCD.1 demand account or equivalent qualified later-Work input, including configuration, conditions, horizon, and evidence window;
  3. the observed gap and the HCD decision it could change;
  4. the evidence collector, declared use, access conditions, privacy or worker-governance boundary, and direct owners;
  5. the protected conditions and safe probe limit; and
  6. the point at which a clinical, safety, legal, employment, target-domain, or other specialist owner must take over.

If the demand is absent or incompatible, stop with a non-training return for the exact missing scope or evidence. Do not diagnose a person against a job label, aggregate profile, or imagined future task.

HCD.3:4.2 - Compare Decision-Changing Rivals

Include at least the branches that remain plausible and would change the next Work:

Rival branchQuestion that keeps it live
demand or envelopeIs the demand specified correctly and inside the capability envelope being relied upon?
applicability, access, expression, adaptation, or enactmentIs the response unavailable, or does a cue, context, interference, configuration, or performer arrangement prevent selection or use?
Method or descriptionIs the target Method missing, stale, disputed, or inapplicable?
tools and supportsAre AI, information, cues, access, environment, workload, recovery, or another support condition limiting?
assignment and organizationIs assignment, permission, authority, coordination, organization, provider access, or a required specialist result missing?
specialist conditionDoes health, disorder, safety, ethics, law, or another specialist condition require its direct owner?
human change targetDoes the evidence support a particular capability, knowledge, skill, discrimination, misconception, behaviour, self-regulation, or commitment as limiting and changeable?
measurement artefactCould a scoring, recording, or interpretation error explain the poor indicator without the corresponding failure in Work?

Do not expand the set with every imaginable explanation. Include a branch when a credible current value or absence makes it decision-changing.

Too few or poorly linked observations, coupled conditions, contamination, or unsafe collection can prevent this comparison from distinguishing the live branches. Narrow the conclusion or give a non-training return that names the evidence limit, the next needed observation, and safe conditions for obtaining it.

Look for a missing intermediate performance, not just an absent basic skill or an unknown whole procedure. Use FPF B.1.5.EW to recover the relevant constituent–whole connections. In a stipulated dance case, the person has sufficient strength, holds the axis when stationary and recalls the figure, but loses balance during its rotation. Those observations locate a coordination question between the muscular actions and the figure; they do not establish a general lack of strength or memory. If existing observations already distinguish the decision-changing rivals, use them. Otherwise choose a suitable comparison of the rotation in isolation and in the figure, under domain-qualified conditions. Return the supported limitation or the unresolved alternative rather than prescribing more of whichever exercise is easiest to name.

HCD.3:4.3 - Probe Before Declaring Capability Loss

When a prior qualified capability or result exists and the differential can change the next Work, use an applicable E.23.CAE disposition before declaring loss or prescribing more practice. Return to a qualified reference condition without further development where safe, vary the smallest decision-bearing condition, and observe applicability, access, adaptation, enactment, and result separately.

A recovered response weakens simple global loss but does not prove transfer. Failure across reference and target conditions may warrant capability-claim revision only after demand, configuration, support, and measurement rivals have been addressed. If the probe teaches, primes, fatigues, changes exposure, or cannot be run safely, narrow the conclusion or return an unresolved differential that states the observation limit and its effect on the conclusion.

For any new observation, record the evidence collector, holder participation, declared use, protected conditions, access and privacy boundary, and whether another owner must interpret the result. Treat an assisting System’s inference as decision input. Acting on it requires separately established authority for the particular action.

HCD.3:4.4 - Record the Result

A qualified intervention target contains:

Result positionRequired content
use boundaryHuman holder, later-Work demand, configuration, horizon, evidence window, receiving decision, participation basis, and governance limits.
observed gapClaim-sized Work observation, intended result or critical-error boundary, and why the gap matters.
targetThe person’s difficulty with the required contribution and the smallest supported human change to target under the named conditions. A later decision selects any practice or other intervention.
evidenceObservations, work products, contrasts, inference rule, uncertainty, and contamination or measurement limits.
rival dispositionThe explanations considered, any still-plausible alternatives, and their effects on the target and next observation. When none remain, keep the evidence limits and reopen condition explicit.
protected conditionsMethod, task, tools, prompts, information, time, environment, assignment, authority, supports, and specialist routes held or bounded.
intended observationThe target change to observe, its conditions, and the claim that would depend on it. Explaining a result as an effect of the intervention through that target requires evidence for each link.
boundaries and continuationDirect specialist or owner boundary, unsupported uses, and the condition that reopens the target.

Observed performance may be reported with its conditions before a causal explanation is established. A better score alone establishes neither a change in the proposed target nor the intervention’s effect through that target.

A non-training return contains:

Result positionRequired content
actual owner or missing resultThe direct Method, tool, assignment, organization, authority, specialist, evidence, or other owner and the exact result or value needed.
blocked HCD decisionThe diagnosis or later development decision that cannot be made.
evidence and rival dispositionWhat is known, what remains unresolved, and why a human target is not supported.
safe interim boundaryWhat must not be assigned, inferred, prescribed, or used meanwhile.
retry conditionThe exact new result, protected observation, owner decision, or compatible evidence that permits reconsideration.

HCD.3:4.5 - What Changes in Practice

A practitioner no longer asks, “Which training should fix this failure?” They ask, “Which live explanation would change the next Work, what observation distinguishes it safely, and what is the smallest human target the evidence actually supports?” A missing Method, prompt, authority, specialist result, or diagnostic observation is returned under its own name.

HCD.3:5 - Archetypal Grounding

HCD.3:5.1 - Constructed Positive Case: ImpactReview-17

ImpactReview-17 is a constructed pedagogical case. ImpactReview-17-Domain-Oracle-v1 supplies engineering correctness and criticality criteria for PumpWorks-Config-Baseline-42 and AI-Assist-M4. The baseline observations and neutral-probe results below are stipulated case data.

For human holder Engineer-P14, the constructed HCD.1 account demands independent review of AI-proposed change-impact claims under a forty-five-minute limit with current sources, configuration trace, auditable evidence, and bounded safety and maintenance specialist returns. The baseline stipulates correct source/configuration trace and evidence return in eight of eight cases, correct specialist routing in two of two relevant cases, and rejection of two of four plausible wrong AI claims. Both misses occur in unfamiliar variants and are labelled safety-critical only by the constructed oracle.

Several rivals would change the next Work. The applicable MethodDescription, source access, tool configuration, time, assignment, authority, and specialist route are present in the case, so those branches do not explain the two misses. An E.23.CAE-shaped neutral probe preserves those conditions. Engineer-P14 recognizes that independent checking is required but does not generate and test a competing configuration hypothesis on either unfamiliar miss.

HCD.3 therefore returns this qualified intervention target:

Generate and test an independent configuration counter-hypothesis before accepting plausible AI output in unfamiliar variants.

The stipulated review permits an ordinary reminder to construct and test a competing hypothesis, but the engineer must supply the case-specific rival and its test. In the proposed comparison, the neutral prompt is “Review this AI claim against the current configuration.” The other prompt adds “Before accepting it, construct and test a competing configuration hypothesis.” Neither supplies the alternative or tells the engineer which claim to reject.

The evidence is narrow: two unfamiliar misses inside eight constructed cases. A prompt-design rival remains live because the neutral prompt may have suppressed the counter-hypothesis move. The protected conditions are the same source, configuration, AI assistant, time limit, authority, and specialist routes. The intended observation is whether Engineer-P14 produces and tests a competing configuration hypothesis and rejects the planted wrong claim in each of two further unfamiliar cases: one first attempt with a neutral prompt, and one first attempt on the other case with an explicit counter-hypothesis prompt. Success with the reminder supports performance under that permitted condition and may justify returning prompt design to the Method/tool owner; it does not establish self-initiated use of the operation. Different cases leave case-difference uncertainty; the comparison informs the next decision without isolating a causal prompt effect. Reopen when the prompt, configuration, case family, source access, tool posture, time, observation count, or target-domain oracle changes.

The result is a bounded target for a later development decision, not an assignment to practice. Operational use needs qualified current domain criteria and observations for the actual person and Work, including evidence that distinguishes the live rivals.

HCD.3:5.2 - Missing Case: ReleaseWork-R9

Engineer-E27 has only a prospective HCD.1 demand hypothesis for ReleaseWork-R9. The actual Work occurrence, occurrence-produced result claim, occurrence-bound result record, representative observations, and compatible obtaining SYSE.21 supplier result required by XRI-21 are not recoverable.

HCD.3 returns a non-training return with diagnostic-evidence-missing. The blocked decision is whether any human capability, knowledge, skill, discrimination, misconception, behaviour, self-regulation, or commitment is the limiting change target. A MethodDescription, plan, target repertoire, curriculum, constructed demonstration, course completion, or platform score cannot discriminate the rival branches.

The safe interim boundary is: do not base training assignment, an inference of human deficiency, employment consequences, or a transformation claim on the unsupported HCD inference. Separate decisions require their own sufficient evidence and appropriate authority. Retry after a compatible HCD.1 demand basis and holder-specific evidence distinguish the live demand/envelope, Method, tool/support, assignment/authority, specialist, and human-target branches under the intended configuration and evidence window. Recovering a Work occurrence alone does not complete the diagnosis; the observations must be decision-discriminating.

HCD.3:5.3 - Unlike Case: Social-Anxiety Clinical Route

When an adult seeks treatment for social anxiety, return that question to qualified clinical care. A diagnostic label, symptoms, avoidance, or treatment request alone does not establish a target for changing a separately specified contribution in later Work. The current NICE social-anxiety guideline (BEH-05) places recognition, assessment, treatment choice, provider competence, safety, shared decision-making, and outcome monitoring with qualified clinical care.

HCD.3 returns a non-training clinical route whenever diagnosis, treatment choice, exposure or CBT content, clinical safety, consent, provider competence, or clinical outcome interpretation is current. It may preserve a legitimate later-participation Work question and the distinction between observed behaviour, support, transfer, and outcome, but it does not prescribe exposure, behavioural experiments, homework, counterconditioning, symptom targets, or provider arrangements. Retry HCD only when the person and clinical owner supply a bounded non-clinical Work question whose evidence can be used safely without taking clinical authority.

HCD.3:6 - Bias-Annotation

Recurring biasLikely driftRepair
training-default biasA poor result becomes a course or practice assignment.Compare decision-changing rivals and return the smallest supported target or a non-training result.
dispositional biasA configuration-dependent observation becomes a stable trait, attitude, or motivation label.Bind holder, Work, conditions, horizon, observations, and any still-plausible rivals.
tool-blame or human-blame biasResponsibility is assigned to the AI tool or person before the joint arrangement is separated.Vary protected conditions and keep human, tool, Method, prompt, authority, and specialist contributions distinct.
familiar-mechanism bias“Forgot,” “misconception,” or “not motivated” substitutes for a controlled differential.Use E.23.CAE where applicable and retain any still-plausible explanation that could change the next decision.
target-rhetoric biasNaming autonomy, confidence, motivation, or practice is treated as evidence that it is limiting.Require holder-specific evidence for the proposed target. A later claim that an intervention worked through that target also needs target-engagement evidence.
clinical appropriation biasA disorder or treatment process is recast as development.Return diagnosis, treatment, provider, safety, consent, and clinical outcomes to qualified clinical ownership.
surveillance biasMore data collection is assumed to be harmless and authorized.Name declared use, participation, access, privacy or worker-governance conditions, and direct authority before collection.
intervention leakageThe target wording quietly names a programme, provider, schedule, or method.Name the person’s difficulty with the required contribution, the smallest supported human change to target, and the intended observation; select any intervention separately.

HCD.3:7 - Conformance Checklist

  • The exact human holder and a compatible HCD.1 account or equivalent qualified later-Work input are recoverable.
  • The observed gap, configuration, horizon, evidence window, receiving decision, and protected conditions are explicit.
  • The rival set contains every credible branch that would change the next Work and does not expand into an unbounded cause catalogue.
  • An applicable E.23.CAE disposition is used before capability loss or more practice is declared when its differential can change the decision.
  • Method, tool, AI, cue, information, access, environment, workload, recovery, assignment, authority, organization, provider, specialist, and human-target branches keep their own kinds.
  • Any qualified target names the person’s difficulty with the required contribution and the smallest supported human change under the named conditions.
  • Evidence, uncertainty, the disposition of considered rivals, any still-plausible alternatives, protected conditions, intended observation, specialist boundary, and reopen condition are present.
  • A non-training return names the actual owner or missing result, blocked HCD decision, safe interim boundary, and retry condition.
  • Evidence collection names collector, declared use, holder participation, access, privacy or worker-governance boundary, and required direct owners.
  • The result authorizes no surveillance, assignment, employment action, specialist action, treatment, or development intervention.
  • The result claims neither target engagement nor transformation before later evidence supports it.
  • The receiver can identify the next observation, safe interim boundary, and owner of any returned question.

HCD.3:8 - Common Anti-Patterns and How to Avoid Them

Anti-patternWhy it failsRepair
“The score is low, so train the skill”The score does not identify the required contribution, where the person has difficulty, or the rival explanations.Recover the later-Work account and compare decision-changing branches.
“They know it when prompted, so the problem is solved”Reference recovery does not establish unaided applicability, adaptation, enactment, or transfer.Record the qualified differential and probe the earliest unresolved position.
“They missed twice, so capability was lost”Small, configuration-bound evidence cannot eliminate support, prompt, envelope, or measurement rivals.Preserve uncertainty and any still-plausible rival; narrow or return the target.
“Motivation is the cause”Naming motivation supplies neither an observation of change nor a causal explanation.Specify the proposed target and observe it. A claim that an intervention changed it and thereby changed a later result needs grounds for both links.
“The AI made the error” or “the human made the error”The joint Method, prompt, source, review, and authority arrangement is hidden.Separate contributions and use a crossed or otherwise discriminating condition where safe.
“A clinical technique is just another learning intervention”HCD lacks diagnosis, treatment, provider, consent, safety, and clinical outcome authority.Return the case to qualified clinical ownership and retain only a legitimate non-clinical Work question.
“The target is practice”Practice is an activity intended to produce a change; it does not identify the person’s difficulty.Name the difficulty making the required contribution, what must change, and the observation that would show that change.
“Diagnosis chooses the programme”A target is evidence for a later decision, not a programme or authorization.Keep programme comparison (HCD.2) separate; stop at the target or non-training return.

HCD.3:9 - Consequences

A development decision can focus on one evidence-supported target instead of a generic deficit, or stop early when the real constraint belongs to another owner. Rival explanations and governance remain visible, reducing unnecessary practice, unsafe probing, and employment overreach.

The cost is disciplined observation. Some cases remain unresolved, and a narrow target may reopen when prompt, tool, task, support, evidence, or specialist information changes. Using a qualified target to design development still requires a separate intervention choice. A claim that the intervention worked through this target requires later target-engagement and result evidence.

HCD.3:10 - Rationale

The smallest decision-changing target is more useful than a complete causal story. It is sufficient to change the next development question while avoiding claims about hidden mechanisms that the evidence cannot support. Recording the considered explanations, any still-plausible alternatives, evidence limits, and reopen conditions prevents “qualified” from becoming “certain.”

The non-training return is a positive result because it prevents misdirected Work and tells the receiving owner exactly what is needed. The specialist boundary is not a residual exception: clinical, safety, legal, target-domain, assignment, and employment questions retain their own authority even when human development is also relevant.

HCD.3:11 - SoTA-Echoing

The working question is: How can a practitioner identify a development-relevant human target without treating every poor result as a training need or a medical diagnosis?

The selected current line joins three bounded contributions. First, Melanson and Fahmie’s Functional analysis of problem behavior: a 40-year review (2023; BEH-01) supports the warning to distinguish maintaining conditions before intervening, but its clinical populations, controlled procedure, causal functions, and specialist safety arrangements are not generalized into HCD. Second, E.23.CAE separates envelope, configuration, applicability, access, adaptation, enactment, and actual capability change through an observation-first differential. Third, Sheeran and colleagues’ meta-analyses Self-determination theory interventions for health behavior change (2020; MOT-01) and Does increasing autonomous motivation or perceived competence lead to health behavior change? (2021; MOT-02) support an intervention-to-target-to-result evidence chain when explaining an intervention’s result through its proposed motivational target. A theory label or assigned technique is not evidence that the target changed.

A serious alternative is the generic training-needs interview or competency-gap score. It is fast and legible, but it commonly treats the selected measure as the cause, omits support and authority rivals, and moves directly from gap to programme. HCD.3 keeps those measures as evidence cues, then mutates the workflow into a bounded rival comparison and one target-or-return result.

This line does not supply a universal causal diagnosis, clinical protocol, intervention, or transfer claim. Human mechanism and intervention claims still require a direct source matched to the population, target, comparison, measure, horizon, support, and limit. Reopen when the holder, demand, configuration, prompt, tool, support, Method, assignment, authority, specialist result, evidence window, observation, declared use, or governance condition changes.

HCD.3:12 - Relations