Velin
A presence system built for relationships that last — where memory, tone and continuity are one layer rather than three features.
- Domain
- Emotional presence
- Stage
- In development
- Form
- Product and API
- Availability
- Not yet open
Presence is treated as a finishing step.
Most systems that people talk to for months were designed to handle single exchanges well and had warmth added afterwards, at the surface. The result is a system that is pleasant in any given conversation and has no idea it has had a thousand of them.
If something is going to sit beside a person for years, the layer that carries tone, memory and continuity has to be built at the same depth as everything else — not applied to the outside of it.
Presence is infrastructure, not interface.
Velin is built around attachment that holds up over time rather than responses that read well in isolation, and around handling difficult moments carefully rather than fluently.
How we are approaching this
- Systems people become attached to carry real responsibility, and we would rather be slow than casual about it.
- Access will be limited at first, and to partners who can be specific about who is on the other side of it.
- Safety behaviour in sensitive moments is part of the product, not a filter on top of it.
What we publish, and what we keep.
Released
- Design principles and safety approach
- Evaluation methodology
- Access terms
Retained
- Model architecture and training
- Memory and attachment internals
