A permanent, witnessed retirement record.
Severance is a signed, versioned tombstone for an Anchor. Once accepted and checkpointed, compliant resolvers reject later Presence or reactivation records for that Anchor.
YuraMesh v0.4 is a coordination specification. Native v1 remains operational and authoritative. YuraMesh production implementation is not authorized.
YuraSeverance belongs to a larger control plane.
Severance does not erase backups, historical records, copied keys or downloaded content. Witness checkpoints and anti-rollback rules are part of the proposed design; governance and exact tree encoding remain unresolved.
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.
YuraSeverance
Retirement statement → witness checkpoint → resolver rejection
Scoped next state
Only the authority and lifecycle signal defined by the design may continue.
Retirement statement → witness checkpoint → resolver rejection
Severance gives a site a final signed state. A compliant resolver can reject later reactivation records after checkpointing, while historical copies, backups and downloaded material remain outside the statement’s reach.
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.