One, I think a week is too short, as another person has already said. I'm planning a week vacation soon and want to be unplugged the entire time. Also, while rare, I can imagine a natural disaster could last longer than a week and the last thing I want to worry about is making sure I send a few emails.

Second, I'm curious why you want so many conditions to be true before the trigger? I've seen services (and I've thought of setting up a simple self-hosted option) that simply email you a link on a predefined cadence and all you have to do is click the link. In order to protect against some weird spam filtering, I'm thinking a text message or Discord message could also be sent. The odds of both breaking for a month I think is rare. Why might I also want Github commits and phone calls to be checked?

If I would forget to click a link, it's either because I'm super busy with work, in which there will be multiple Github commits per day, OR it's because I'm enjoying a vacation, in which my social media might be more active.

I have been away from technology but not for more than 2 weeks at a time. I suppose just s/week/month/ or whatever.

I’d be careful to multi factor data decryption, the encrypted data must be released and some party you trust who isn’t likely to die with you holds a decryption code

Then you don't need complex technical triggers.

Just use something like Dashlane. People can report you dead, and then you have up until your specified waiting period to mark yourself as not actually dead. If Dashlane goes out of business you'd need a new provider, but as long as you don't die within a month or so of your password manager then you're set. Much better than writing your own.

Also, you're almost certainly going to outlive Dashlane.