Multi-human roots
Separate an MHR identifier from an actual threshold signing ceremony.
MHR denotes a multi-human-root entity. The current oas_sdk::identity::create_mhr helper generates a single Ed25519 keypair and signed L0 document. Calling it does not execute a distributed key-generation ceremony or prove control by multiple people.
Build a threshold-backed root
Choose the threshold library/version, coordinate the actual share-generation and signing ceremony, retain participant custody and recovery policy, and publish the document and authority records appropriate to that configuration. Verify that the group's signing key and document verification method agree.
The identity, key and ceremony modules are separate. Use OAS identity signatures and AEGIS threshold APIs, with the FROST version/custody guide.
Threshold signatures prove that the configured key-share quorum participated. They do not independently establish unique humans, organizational legitimacy, or a trusted authority anchor. Apply those policies explicitly.