In discussions in Dublin – mostly between Jason, Jeremy and Mike – the idea of a module-level manifest was well-received. The idea is that since resources are in fact maintained at the level of the module rather than the component, it is more honest to define them at the level of the module – perhaps in a manifest.js file, or in an exported object in the top-level component. (The latter is appealing in that it means there are no magic filenames in a Stripes module.)
Once a module-level manifest exists, the manifests of individual components within the module will in general contain references to the module-level resources rather than defining their own.
We may allow components also to continue, as now, defining their own resources. (As well as providing flexibility, this would provide a nice backwards-compatible upgrade path.) Or we might enforce that resources defined at the component level had to be stored at the component level, too.
There's a fair bit of design still to be done here, and it all falls into the category of Important But Not Urgent. (But one day, it might suddenly get urgent.)