great questions. here are my thoughts > The ability to target to a particular tag, commit or branch of a vault repo, so that I can control which version of a vault is imported into my workspace we'll add an optional

branch

parameter for the vault so you can specify a particular branch to track > The ability to include vaults that are hosted as private repos and require some kind of authentication to access them this will be done using either ssh, https, or token based auth depending on how your hosting your remote repo > From the proposal, I think it is clear how multi-vaults would work inside the Dendron workspace. I am less clear about how a publishing model would work. multi-vault publishing is still evolving. one way of handling multiple domains is for each domain to have its own site configuration. a site configuration specifies the vaults and hiearchies that are published for a particular site. for notes in a separate vault/site, the behavior can either be a tooltip that says the note is unavailable (because it isn't published) or it can turn into a link to another site