There’s the concept of unclonable physical functions (PUFs) (https://en.m.wikipedia.org/wiki/Physical_unclonable_function) that can provide something like this. Some companies like Physec offer key derivation mechanisms based on PUFs that depend on the physical characteristics of the environment of the device that generates the key (e.g. the electromagnetic impedance), so an attacker needs the actual device to produce a key that matches the profile, and tampering with the device by e.g. opening it destroys its ability to generate a key due to changes in impedance.
It’s a really neat concept but I don’t think anyone found a way to apply it to a human, though it should be possible (e.g. using your heartbeat).
A company called nymi does exactly this. They have a wrist-watch device that actively profiles wearer's heartbeat for unique identification.
My previous and current company use perforce but many people (often those who recently join) are decrying that perforce is less elegant than git, but, realistically and based on your own criteria it would be "better" for the connected case.
I'm personally a big fan of 'offline/local-first' being a thing, but I'm a sysadmin not a developer.