Spawned from conversations around standalone state transfer, we pivoted the direction we were headed with this during Sprint 204 as it became clear through the process of design that a lot of the objectives were shared between MTC and Crane 2 (and as a consequence, Scribe).

We feel the correct way to approach this problem is not to solve in two different places. Instead, we want to refactor the battle-tested DVM logic into a generically consumable library (crane-lib), and to contribute that in a way that's consumable by both Scribe, and DVM (and therefore MTC).

Definition of done for this story is that the approach has been reviewed and ack'd via our enhancement process, the logic has been reimplemented within crane-lib, and crane-lib is used behind the scenes for DVM.