People, relationships, and context spaces

Personal by default, shared with purpose

A household can coordinate while each person retains authority

Unison uses explicit context spaces to organize private and shared information. Relationships inform the experience, and access follows membership, purpose, consent, and policy.

Each person begins with a private space

Knowing that two people are family, colleagues, caregivers, or friends can help Unison choose relevant context and an appropriate tone. The relationship itself does not grant access to private information.

Each assistant begins with a private space and an independent identity, key, credential, data, cache, index, audit, and backup-policy namespace. Search and prompt construction begin from an explicitly authorized space and purpose.

Sharing creates a governed space

A shared space records its purpose, members, selected information, policy, retention, and key domain. It can support a household grocery list, a trip with friends, a care plan, or a project with colleagues.

Sharing creates an auditable item in the selected shared space while the private source remains private. Invitations require acceptance. Member removal revokes access and advances the shared space key version. Co-location, family status, inference, and device administration carry no independent sharing authority.

  1. Choose a purposeState the shared outcome and the information needed to support it.
  2. Select peopleIdentify proposed members and collect the consent required by policy.
  3. Preview informationReview the exact items, fields, retention, and available alternatives.
  4. Create or update the spaceApply membership, keys, policy, and scoped copies through the owning services.
  5. Keep control visibleSupport inspection, correction, revocation, deletion, cancellation, and recovery through every native experience.

Shared work preserves personal privacy

Two adults can contribute calendar events or grocery items to one household space. Coordination reads the shared records needed for that intent and reports which sources contributed. Private records remain independently governed. Cross-person probes receive the same response as requests for resources that do not exist, reducing information leakage.

Per-assistant queue, concurrency, CPU, and memory budgets help the shared node serve multiple people without allowing one workload to monopolize the scheduler.

Roles that need dedicated care

The first implemented household model covers independently consenting adults. Child, dependent, caregiving, incapacity, delegated authority, and emergency access require role-specific policy, safety review, revocation, and recovery. They will enter supported profiles only after that work receives appropriate technical, domain, physical, and participatory evidence.