HCD.7:4.2 - Allocate Contributions, Not Labels
Construct one contribution allocation:
| Allocation field | Required content |
|---|---|
| contribution and recipient | The explanation, demonstration, case, access, feedback, check, assessment, specialist result, coordination, or fallback needed; who or what uses it; and which task or result it enables. |
| provider and scope | Identified supplier, contribution-specific competence, authorization, independence where needed, and explicit non-responsibilities. |
| timing and service condition | Required date or interval, concurrency, response or feedback deadline, duration, handoff, and dependency on other contributions. |
| access and constraints | Data, source, project, environment, interface, accessibility, privacy, confidentiality, safety, legal, employment, or organizational conditions. |
| capacity | Preparation, delivery, checking, correction, coordination, fallback, and peak-load effort; competing uses and unavailable periods. |
| evidence and fallback | Evidence that the provider and access are available for this use; failure signal; feasible fallback or exact missing result and retry condition. |
One person or tool may fill several rows, but each row keeps its own competence, workload, and constraints. Several providers may jointly supply one result, but their interfaces and the person responsible for the final judgement remain explicit. A catalogue, contract, platform account, or calendar slot is evidence input; none establishes every row by itself.