Private discovery with capability boundaries.
Obscura is the proposed Presence and capability layer. It distributes signed, expiring service records with access filtering while separating discovery visibility, hosting authority and content authorization.
YuraMesh v0.4 is a coordination specification. Native v1 remains operational and authoritative. YuraMesh production implementation is not authorized.
YuraObscura belongs to a larger control plane.
A Presence record can report online, offline, migrated or retired state, but endpoints do not prove ownership, host integrity or availability. Expired Presence means unknown or offline, not erased.
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.
YuraObscura
Presence → capability filter → eligible discovery
Scoped next state
Only the authority and lifecycle signal defined by the design may continue.
Presence → capability filter → eligible discovery
Obscura separates the fact that a service can be discovered from the authority to access it. Signed, expiring records can describe presence and capability without turning a public endpoint into proof of ownership or permission.
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.