RSP modules map directly to the Love Key data model and Help Network routing rules, while keeping protocol concepts out of the family UI.
In an online climate of impersonation, voice cloning and AI stand-ins, a person's avatar is its own consent dimension — scoped, projected, and revocable like every other.
Every dimension RSP tracks is scoped and revocable. This table is the quick reference — what each dimension governs, a concrete example, and how it is withdrawn.
| Dimension | What it governs | Example | Revocability |
|---|---|---|---|
| Permissions & visibility | Which people or hubs can see which parts of your profile and data. | Let your care circle see your calendar, but not your location. | Revoke per grant; visibility stops immediately. |
| Identity context | Your core profile plus contextual roles resolved per hub. | You appear as “Coach” in one hub and “Dad” in another. | Leave a hub or drop a role; context resolution updates. |
| Presence | How your live state (available, busy, quiet) is shown to others. | Show “available” to your household, nothing to everyone else. | Change or clear presence at any time; scoped per audience. |
| Identity exposure | Protection of visual and voice likeness against unwanted similarity. | An AI stand-in may read a message in your voice only during a session. | Session- or time-bounded; revoke and the likeness stops projecting. |
| Support signals | How a request for help routes to the right circle without broadcasting distress. | A quiet “need help” reaches your emergency circle only. | Withdraw the signal; routing ends and nothing is retained as a score. |