Hand-offs create useful continuity, but they also cross an identity boundary. A raw transcript can leak unrelated memories, confuse who said what, and make the receiving companion impersonate the sender.
The relay system builds a bounded message with explicit names and instructions not to answer as the other speaker. Family-safe eligibility is checked before a childlike companion receives a shared turn.
What was actually going wrong
Treating relay as transcript concatenation blurred identity and context ownership.
What I tried
- Forwarding the complete source conversation
- Removing speaker tags to make the relay sound natural
- Asking the model to infer which companion should answer
A structured, scoped hand-off names the source and recipient, includes only relevant content, and enforces the recipient's own prompt and safety rules.
Why it worked
The receiving companion gets context without inheriting another identity or private store.
Continuity does not require collapsing boundaries.
Where EACI uses this today
Main companion relays preserve distinct voices for Caelum, Chad, Natalia, Atreus, Luna, Roxy, and Cael.
This journal covers real engineering on EACI Companion / The Veil. Companions include Caelum, Chad, Natalia, Atreus, Luna, Roxy, and Cael. Journal articles stay family-safe in content. See Privacy and Ethics.