NHID™.

Before NHID, non-human identity was a collection of loosely-typed nouns: API keys, service accounts, machine tokens, workload certificates. Each was governed by a different tool with a different lifecycle. NHID names one artifact for all of them: the X.509 credential a non-human presents to authenticate, bound to a scope, a validity window, and a named accountable human owner in the enterprise identity provider. Naming the artifact makes it governable. Once every non-human carries an NHID, an enterprise can enumerate them, attest them, rotate them, and revoke them from one control plane. Every downstream question, from audit through incident response through cost attribution, begins with the NHID and its lineage.

In an Arkion-governed estate, every AI agent, service account, workload identity, and IoT endpoint is issued an NHID at deploy time. The NHID is presented on every request. Runtime authorization checks the NHID's certificate, scope, and revocation state on each action. When the human owner leaves the company, every NHID they attested is a candidate for reassignment or revocation in one motion.