Vault Tagging for Classification and Filtering/Sorting

[CMCDragonkai]

Vault tagging is the ability to tag vaults to have a taxonomy/folksonomy of vaults.

This allows user to create classification levels of secrets which is useful for certain workflows: https://en.wikipedia.org/wiki/Classified_information

Users should be able create tags arbitrarily, and then assign these tags in a many-to-many relationship to vaults.

Then users can search for vaults with a specific tag or a set of tags.

When searching for a set of tags, the logic can be a conjunction of tags, or a disjunction of tags.

By default it should be a conjunction.

Previous issue: https://gitlab.com/MatrixAI/Engineering/Polykey/js-polykey/-/issues/159

[CMCDragonkai]

The idea of having vault names is similar to "petname system" (important with respect to zooko's triangle).

This is explained here https://www.inkandswitch.com/backchannel/#names:

The same concept could be applied to GestaltGraph as well, but it's a bit more complicated because how GG doesn't have a canonical structure. So names have to be applied to the "gestalt" which means it has to be applied to any of the vertexes in the gestalt, and thus all of them are applicable.

[CMCDragonkai]

Vault naming is also relevant for the workflow. For example a given project like "Polykey Enterprise" may have several vaults for different people/usecases. The naming of which can be left to the end user to figure out. It would be interesting to document useful ways of naming vaults though to avoid confusion. You may have 2 or more devs working on the same project using different keys to test it.