Jump to text
On this page
Copy and source
Published source confirmed at last check

Source changed 2026-11-18 22:51:26 UTC · snapshot created 2026-11-18 22:54:45 UTC · last check 2026-11-18 23:20:20 UTC

HCD.1:4 - Solution

Derive each required human contribution from representative later Work. Distinguish observed cases from plans, stipulations and assumptions. Identify which contributions the person must make, what others or the environment must supply, and how strongly the available evidence supports each requirement.

HCD.1:4.1 - Pattern-Use Unfolding

  1. Fix the use boundary and holder. Identify the person, the question or decision the account will serve, the planned task or range of later work, 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. State any missing external condition or contribution and what depends on it.
  4. Select representative cases. Cover the variants that can change demand. Depending on the Work, these may include 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 any observation still needed. 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. Return 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 question or decision, planned task or range of later work, 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 any observation or case still needed.
external gapsMissing Method, description, specialist return, assignment, authority, access, environment, or nonhuman capability with the work or conclusion that depends on it and its responsible source where known.
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.

For each input that a conclusion needs and still lacks, explain what it would establish and what would allow reconsideration. Use the following fields where they apply.

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.
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.

Use qualified direct observations when they suffice. If the claim depends on a result record, establish its connection to the Work and the result.

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.

For another use, check that the person, configuration, later-Work conditions, horizon and evidence window support the new question or decision. Carry over the applicable limits. 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

Ask “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.