This is essentially an open invitation for comment on the issue of build products. Below I've laid out some points to potentially address and think about.

1. Where is the best place for products to be documented?
   Currently it seems like every vendor platform except QuickLogic does this in it's docstring for the platform. This is already rendered in the vendor section of the rendered documentation pages and this is likely a useful place for it to exist in some form. The question is if this adhoc method of documenting the available output products is really ideal given the importance of the information.
2. Should there be a programmatic way to query the available output products?
   This is likely not particularly necessary, while initially I thought this might be desirable in enabling users to copy all products from a remote machine or into a specific location, this can likely be done just as well or better by just allowing the folder itself to be copied in some form.
3. Should there be any standardized interface to the products?
   Obviously each platform's output is fairly unique, but there are some similarities, of these I think the most common likely products to exist are "bitstream/input to programmer software" type files, log files from the build, and any potential timing/DRC reports. It might be nice to have these extracted out so that at least some level of generic interface can be built on top. This also might result in a fragile mess that's not worth maintaining.
4. Should we document any changes to the products that a Platform will produce?
   I think we should, but we should think about how we want to handle this given that vendor toolchains especially can change the outputs they can provide or their format essentially at a whim.

I think I've covered most of my thoughts here. Perhaps in a bit too much detail, but hopefully it gets us thinking about the options we can have.