A persistent identity for a website.
An Anchor is derived from a canonical owner public key, not an IP, host, operating system, provider or WireGuard address. A signed owner identity can survive hosting migration.
YuraMesh v0.4 is a coordination specification. Native v1 remains operational and authoritative. YuraMesh production implementation is not authorized.
YuraAnchor belongs to a larger control plane.
The v0.4 specification defines an AnchorID domain and Ed25519 owner key. An Anchor signature proves possession of the owner key; it does not prove host integrity, availability or service authorization. Aliases are signed mappings, not ownership proofs.
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.
YuraAnchor
Owner key → AnchorID → signed publication
Scoped next state
Only the authority and lifecycle signal defined by the design may continue.
Owner key → AnchorID → signed publication
An Anchor gives Studio and Hosting a portable ownership reference. Moving a service can change its host and endpoint while preserving the owner-authenticated identity; the signature still does not certify availability or the integrity of a host.
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.