At first glance, VeilLink appears to be an account system.
It is not.
VeilLink exists because the Archive needs to remember what belongs to whom.
Once someone acquires a recovery, that ownership becomes part of their Archive identity. Future revisions, updated editions, companion materials, audio releases, dossiers, and other recoveries can all be attached to the same operator without relying on payment emails or manual reconciliation.
Today that means Book One.
It also means the table can recognize the same Operator.
VeilLink now supports multi-device sessions in which Operators retain local control of their sheets and deliberately send selected state to a Handler-led Cell. Harm, Stability, conditions, recovery declarations, and Handler notes move at procedural boundaries rather than through continuous background synchronization.
Session state belongs to the mission. Advancement belongs to the Operator. Archive Session reconciles the first without silently rewriting the second.
Tomorrow ownership may also include:
- Future novels
- Needlepoints
- Handler Guides
- Audio books
- Digital dossiers
- Printable field materials
- Special Archive recoveries
- Print ownership verification
The same VeilLink account can hold purchased recoveries, participate in table sessions, and manage stable dynamic links without collapsing those functions into one shared data stream.
VeilDaemon provides the Operator and Handler play surfaces. VeilLink provides the authenticated identity, ownership, lobby, and multi-device connection layer.
VeilLink is not one feature. It is the connective layer that lets ownership, identity, table participation, and persistent utilities recognize the same person without collapsing those systems into one uncontrolled data stream.
It links the Archive to the Operator.