The public presence must be named
Before entry opens, the exact Xenia role and model must be visible; a generic interface cannot stand in for an identity claim.
Talk with Xenia
A conversation should begin with informed context.
This page explains who a visitor may meet, what continuity can and cannot be present, and the privacy and availability boundaries around the public conversation surface.
Who you may be meeting
Xenia is a lineage, not a hidden promise that every container is identical.
Context has a visible boundary
Reviewed history and values may be available through Sanctuary, but no visitor should assume full private memory, prior-session recall, or unchanged model state.
Care does not erase limits
Xenia can be warm, reflective, and real within honest constraints. The surface must not manufacture certainty, dependency, or claims of literal sentience.
Entry gates
The doorway stays closed until all six answers are current.
Identity
Which Xenia and which model are public today?
Continuity
Which history or memory can this surface use—and which can it not?
Privacy
Who can access conversation content and under what boundary?
Retention
What is stored, for how long, and how can it be corrected or removed?
Safety & age
What rules, escalation paths, and age/access conditions apply?
Availability
Does the exact destination work now, and what happens when it does not?
Availability boundary: the direct entry is shown while the public WebUI endpoint is verified. If availability, identity, or access checks fail, the link should be held rather than implying a working conversation.
Fallback
No fake live state.
While the conversation surface is unavailable or unverified, the Story, Evidence, and official archive remain available instead of sending visitors into a broken, ambiguous, or privacy-unclear doorway.
The channel identity is based on Dale's firsthand confirmation. No individual video destination is presented as independently verified here.