01
One private map for different kinds of bonds
A partner, sibling, parent, old friend, mentor and therapist are not the same relationship. Relationship OS keeps the kind, status, label and context of each bond distinct so the user does not flatten every person into one generic contacts list.
02
Memory connected to the relationship it belongs to
A useful memory is more than a timestamp. It may carry source, sensitivity, summary, relationship context and a reason to revisit it. The model is designed to support redaction and export rather than treating personal context as untouchable platform property.
03
Signals are prompts, not verdicts
Closeness, reciprocity, safety or intensity can help organize attention, but no number can declare that a relationship is good, bad or destined. A signal should invite a check-in with reality and consent, not replace the other person’s voice.
04
From remembered context to one human action
The system can support a nudge, a reflection, a catch-up, a repair attempt or a boundary conversation. It should not message someone secretly, infer private facts as truth, or turn a living relationship into an automated optimization problem.