IMO since access rights are bound to bags, that will cause a lot of problems. Think about separation of concerns. — I think KISS is the way to go.
I think we need to keep the structure tiddlyweb introduced. A lot of thought went into it. As far as I can remember it was designed to have filters for bags. But nobody really used that option. Way to complex.
This would be filtering the tiddlers inside a bag you have already been granted access to. It wouldn’t be used to determine which bags you have access to.
I’ve been trying to find documentation on Tiddlyweb, but a lot of the hosting sites aren’t working anymore.
I think it makes sense to add filter options to each bag in the recipe. In the bag, I will have some customised tiddlers that will be used only in this bag, so I don’t want those tiddlers to show up in the recipe along with it. So it would be nice to have a filter option so that I can avoid these custom tiddlers from being presented in the recipe, but being able to use them properly in the bag.
Also, it seems a bit confusing to me to think of the plugin as a bag. A plugin is a bag, but there are hundreds of plugins in the TiddlyWiki community, so if all of them were treated as bags, the list of bags would be very long and affect other bags that might contain content, so a better way of handling this might be needed.