Shouldn't the maximum declaration amount of the task responsible for issuing components be limited to the amount issued?

[Christian Carlow]

Arbitrary quantityProduced values may be specified for production run 
declarations.  In a previous post, it was agreed that the 
quantityProduced should be limited to the quantityProduced of the 
previous task.  Shouldn't this logic apply to the task that is 
responsible for stocking out materials also?  For example, if I have a 
production run to create 10 GZ-BASKET but issue only 1 of its GZ-1000 
components, shouldn't the quantity produced of that task be limited to 1 
since the remaining 9 GZ-1000 components haven't been issued yet?  
Currently it allows for any value such as 1000 to be entered as the 
quantityProduced.