Identity roles without accidental conflation.
YuraGenesis names the identity-separation architecture: installation key, device/session key, membership key, site-owner key, hosting key and content keys have distinct roles.
YuraMesh v0.4 is a coordination specification. Native v1 remains operational and authoritative. YuraMesh production implementation is not authorized.
YuraGenesis belongs to a larger control plane.
The separation limits unnecessary authority and linkability. It does not automatically provide anonymity. The v0.4 OS responsibilities explicitly require Native credentials to remain separate from YuraGenesis keys.
Its authority is intentionally bounded: identity, transport, naming, discovery, ownership and data protection are related without becoming interchangeable.
Input state
Explicit identity, record or transport context enters the component.
YuraGenesis
Installation → device → session → membership → site owner
Scoped next state
Only the authority and lifecycle signal defined by the design may continue.
Installation → device → session → membership → site owner
Each identity role has a narrower job. That lets the environment reason about device admission, a user session, network membership, a website owner and encrypted content without handing every layer the same key or context.
That boundary is the reason this component is named separately: it can evolve, be reviewed and be revoked without silently granting unrelated powers to the rest of the ecosystem.
Evidence status
Grounded in YuraMesh protocol specifications and phase-one audit material found in the authorized workspace. This page describes a specified or proposed architecture, not a claim of production deployment.
Trust boundary
Implementations must verify signatures, scope, expiry, replay, sequence and revocation according to the applicable specification. Reachability, DNS, TLS or Native success alone cannot establish the authority described here.
Relationship to current YuraNetwork
Native v1 remains unchanged and authoritative. Any future adapter must preserve its transcript and be separately reviewed. YuraCore may eventually expose lifecycle and readiness context through defined interfaces; that interface is not yet a public production API.