Visible, not opaque
Users can see what long-term memory exists instead of treating privacy as a vague promise behind the scenes.
Feature
Privacy controls start with visible memory and explicit boundaries.
SparkCore should not ask people to trust hidden retention rules. The first layer of privacy is making memory, trace, and channel boundaries visible enough to inspect and repair.
Corrective controls
Hide, mark incorrect, and restore actions help repair remembered state without pretending the system is immutable.
Channel boundary awareness
The product shows which IM channels are attached to the relationship so users can understand where continuity is entering from.