You can copy the flair. You cannot copy the proof.
A GitHub handle is not proof of identity and a badge image is not a credential. M5 binds an authenticated external account to the member's IAM subject, records evidence, and issues a separately status-checkable credential.
Binding ceremony
What the M5 credential says
IAM subject verified; public proof may remain pseudonymous.
Freedom Office, M5Brain, permissions, human approvals, portability and evidence demonstration.
External account control verified and bound to the IAM subject.
Signed / accepted contribution references and domain demonstrations.
Issuer status checked separately from the visual badge.
♡ M5 LOVE = community / contributor affiliation.
M5✦AI = demonstrated human-in-charge AI Agent Operations capability.
GH↔IAM = GitHub account has been identity-bound through the verification workflow.
Foundation Contributor = one or more accepted contributions are attached as evidence.
Impersonation, suspension and revocation
Anyone can report suspected impersonation or misuse. A report alone does not automatically revoke a human's credential.
Compare IAM binding, GitHub stable ID, signatures, evidence, credential issuer and audit history; allow correction/appeal.
When confirmed, M5 can suspend/revoke its credential, binding, Proof Share or Foundation permissions. GitHub controls the GitHub account itself.
Account types stay distinct
May bind to the human IAM subject after authenticated account-control verification.
Automation identity is linked to the responsible human/entity; it must not receive “verified human” status.
Software identity links to an agent/application record and delegated authority, not to the sovereign-human root.
Evidence Register
Use the M5 Evidence Register to see which claims are only source-mapped and which have progressed through IAM binding, demonstration, accepted contribution and authorization.