Feature Discussion - Personal or Global Secrets

There are a few types of "secrets" that don't fit within the concept of a project (e.g. code repository) as their life cycles exist outside of a single application (e.g. AWS_SECRET_KEY or similar).

Ideally, these secrets can be stored inside torus, however, we need to answer a few questions.

* Do these secrets belong to the org or the user? For example, if I set my `AWS_SECRET_KEY`, is that accessible to the org or does the data belong to me?
* How are these secrets (which don't belong to a specific project) affect those that are set within a project or service (i.e. how does path specificity fit?)
* What would it look like to set a personal or global secret?
* How would you view and explore these secrets in relation to the other secrets stored inside torus?

All feedback, thoughts, ideas are welcome :)

Start by reviewing the four open questions in the issue about ownership, path specificity, setting secrets, and exploring them. Done would require an agreed design for personal or global secrets; the payload names no files, tests, or implementation entry points.

Written by the indexing model from the issue text.