This morning, the Architect woke up, pulled the Product Manager aside, and said, "Wait -- why exactly are we bothering with this? I mean, yes, it's a nice feature and all, but don't you always tell me that features should fight for their lives? If we weren't already doing this in the Wedding RSVPs, would *anybody* have thought to ask for it? Can't we just put it aside for a while?"
So the two of them got into a deep argument for an hour or two (with the Project Manager weighing in on the Architect's side), and eventually the Product Manager admitted that, yes, this feature is a "nice to have", and not even actually that high on the nice to have list. So we should tie it off as neatly as we can, and move on -- for the time being, invitations can simply point the invitees to the root of the Space, and that'll do for now.
But of course, now the Engineer is going, "Wait -- what? I just spent two freaking days on this! The code is *good*! I'm ready to implement this feature now! Waaahhhhh!"
You'd think that having all of these people in the same head would make for fewer arguments, but that doesn't seem to be the case...