I spent a decade as a full time Tcl developer and even I don’t use fossil.

You could generate a revocation key and then encrypt for multiple people using Shamir’s secret sharing.

https://en.wikipedia.org/wiki/Shamir’s_secret_sharing

Look into ssss and gfshare, the latter explicitly discusses this use of the algorithm.

https://manpages.ubuntu.com/manpages/noble/en/man7/gfshare.7.html

You’ve used some phrasing that I am not really following. What exactly do you mean by “stable” in regards to an email address? And what is an “unknown” domain?

I do this for every website, not just financials. As long as you have a quick and easy way to create the email aliases and you’re using a password manager I think it can be an easy and effective boost to security.

Just to be clear, the “reason” here is that your expectations are not correctly aligned with the project goals.

This looks like an attempt to reproduce the web-of-trust functions provided by Keybase.io. Keybase has historically been a great resource that fills the same role as the PGP/GnuPG web of trust for a much broader range of identity attestations.

An open implementation of this concept has been sorely needed since Keybase got bought and shitcanned by Zoom during the COVID lockdown. Zoom wanted to aqui-hire all the Keybase devs to boost development on their lacking encryption and security. Sadly, Keybase has basically been abandonware since then.

You are describing the GPL. FOSS encompasses many licenses in addition to the GPL and those other licenses do not fit your description above.