PG-6 Waiting work is deferred with its reason

A task that waits on a person's judgement or on hardware the machine lacks SHOULD be recorded as a deferral with its reason, not left open.

Field	Value
Keyword	SHOULD
Level	1
Checked	by judgement
Findings	F105
Harness facts	none
Threat	external: the practice is seen in one project whose product depends on physical and aesthetic inputs
Status	active

Rationale: polyweave declared a deferred store when a task could not be finished from the machine, set work aside with its reason, and brought it back when the missing thing arrived: a task deferred because an engine was not installed returned the same morning, "now that there is a Godot", and a task deferred for a person's look shipped the next day once a person had looked (F105). A recorded reason makes waiting a state the backlog holds, so the next pick moves on instead of retrying. The finding is R3/S2, but its second origin, winwright, closed such work rather than deferring it, so the deferral itself is seen in one project on several occasions and the rule carries SHOULD. That the agent must not close such work is HR-1.