Natural entry point
People already use IM all day. Keeping the companion there lowers friction and supports steady return behavior.
Feature
IM-native chat keeps the relationship where daily life already happens.
SparkCore treats IM as the main interaction surface. The website acts as a control center for setup, memory, and relationship state rather than forcing every conversation back into the browser.
Shared state, not mirrored clutter
The canonical thread and relationship state stay shared, but website messages do not have to become mirrored IM bubbles.
Website as control center
IM stays lightweight while the website handles configuration, channel control, and memory visibility.