Cosign

To cosign, is to say you agree with someone's membership in a tribe. Cosigns are temporary; they last until one party or the other changes their mind. You can also set an expiration date on your cosign.

So, you may meet someone at an event, and connect with them. Via the app, you get a list of concepts, tribes, and actions which they have made public, and you can select any of them to sign it, effectively saying yes you agree this is true about the other person. They then have the opportunity to sign anything you've signed, thereby making it an official cosign. Others they can throw away, and even though you signed it, it does not present them as a result when other people search on them.

When you connect with someone, you get a list of attributes to cosign, you can choose some and reject others. But you have 15 minutes to do it. Other than that, you have to wait till tomorrow. Since you two are connected, you can go to their persona, and once a day has passed get a new list of things to cosign. You cannot cosign the same attribute twice.

When people make an announcement, they can require the responders to have a certain cosign, so as to limit the number of people made aware of the announcement. If someone accepts a responder to their event, and they require your cosign, you will be notified so you can see which of your cosigns are in demand.

You should be able to verify, that, given this string, this tribe, person A and person B signed it using their public keys. Others can then see, did person B cosign you in this tribe? That will help to give weight to it, potentially make your tribe membership stronger.

The cosign is Bob taking Alice's self created verified credential for an attribute, and Bob issuing another credential based on Alice's indicating he agrees with the statement. The VC that Bob creates has a field indicating how a verifier can see if it has been superseded/cancelled/etc. The VC is a file, I believe, stored in Alice's possession: these are her list of people who cosigned her. Should that list exist anywhere else, other than with Alice, by default? I feel like not. Each person who cosigned her would also have a record. Not enough to build a comprehensive list though.

But then it has that possibility of being revoked, cancelled, etc. So the verifier checks with the method described in the VC, and anyway the point is that is another place info about VCs will be .. either a private centralized database, or on the blockchain somehow. You're gonna have to check for subsequent issues taking action on the original credential, and how does that even happen.. how do you find proof it was updated, that another superseding credential was ever created...? hmmm.