orders, and their corresponding objects in the system, haven't been discussed much since the definition of the concrete Order class in the artisan_objects module. In part, this is because the other classes (particularly Artisan and Product) are representations of data that originate in the hms_sys code-bases. Still, the artisan_objects.Order class was left in about as complete a state as could be expected, with full data persistence and a concrete implementation that was expected to deal with all the requirements against it up to that point.
As a result, though, several aspects of orders fell off the radar. The original set of stories for this iteration only included one Order-related story—an Artisan's need to be able to update an Order as part of a fulfillment process—with nothing that provided any path for that Order to...