Sometimes we have packages that make it all the way to the weekly repo that are actually broken. And when that happens, normally a fixed version is in limbo very quickly, but it can take quite a while to propagate down to the weekly repo. What if we had a concept (as proposed in the subject title) of a 'Emergency Fix Repo' to handle such situations.
The only packages to go into the Emergency Fix Repo would be to upgrade a known broken package that has made it out to weekly (or main, if the maintainer so chooses).
By keeping it separate, users of weekly don't have to take something that hasn't gone through the standard release procedure, if they don't want to get updates from this repo. In theory, the list of packages added to this repo should be very small, and hopefully empty most of the time. They can of course be removed when the package makes it to sabayon-weekly through standard means (in theory this part could be automated).
This particular concept does not have to be done by the official dev team, either! Feel like you've got what it takes to run a community repo? There's a real need for something like this. I see people asking for expedited fixes or how to downgrade a package all the time.