A common use case different from the typical uses we've been thinking of for this is when editing a bunch of cards on a Wagn that you would ideally have all go live at once - e.g., when changing a field on a form from Phrase to Pointer (and associated +*input, +*options, etc.) - so that the site is not broken while the editing is in process.

We should probably close this ticket and focus on the Packs Blueprint.

I see the value of that user story. Not sure it's a modules use case, but maybe we should put it as a user story and think about what all we want to connect it to.

  --Ethan McCutchen.....Tue Mar 02 15:39:07 -0800 2010

closing -- this is highly important but energy centers around the Packs Blueprint

  --Ethan McCutchen.....Tue May 04 16:25:51 -0700 2010