Doesn’t the existing bare base snap serve your purpose?
You said your snaps are statically linked so I’m not clear why they also need bash, but if they do maybe you can include bash in them (which you would also have to statically build anyway because I’m fairly sure using bash as a stage package will have library requirements and thus won’t be fully static).
For context, we are experimenting with this for the Livepatch client snap. The binary inside the snap is statically linked but it also uses some bash (and core utils) in its hooks and due to this bug the snap’s auto-generated meta hooks require a shell located at /bin/sh.
The original plan was to use the bare base + busybox (statically linked) to get it all working. But because of the limitation above around the meta hooks, it seems easier to go with our own base that has busybox and a shell located in /bin/sh.
Hope that’s all clear. Also, maybe this is something that can be discussed in person in Prague to understand the approach better.
iiuc from the bug comments, it seems @mr_cal is suggesting alternatives to make this work with the existing bare snap. Unless this is urgent or is blocking the Commercial System team, I think this is preferred. Maybe @sergiusens can also help here.