Volta Sovereign AI · SARION
← Return to Intelligence Briefings

INTELLIGENCE BRIEFING // DOSSIER V-12

The Family Is Not One User: Separate Instances and Deliberate Sharing in a Private AI

A Memo on Per-Member Privacy, Explicit Sharing and Why Shared Households Need More Than a Single Login

EXECUTIVE SUMMARY

A household or family office contains several people with different confidentiality needs. This memo explains why one shared AI account fails them, how separate private instances with explicitly configured sharing work on SARION Regent and SARION Sovereign, and what a family should decide about sharing before commissioning.

1. One Login Is the Wrong Model

A household does not behave like a single user. A principal, a spouse, an adult child and a family office director each have matters they discuss openly with some people and not at all with others. A medical question, a negotiation, a gift, a dispute with an adviser: each belongs to one person, and sometimes to a few.

An AI system built around one account and one memory treats the household as a single mind. Everything said becomes available to everyone who uses it. For a family, that is not a minor inconvenience. It is a confidentiality failure inside the house, and it grows with every conversation.

2. Separate by Default

SARION Regent and SARION Sovereign support separate, private instances for each member of a household. A husband and a wife can each have their own instance. Each is private by default, and nothing crosses between them automatically.

The default matters more than the feature. A system that is open unless someone closes it asks every user to remember to protect themselves. A system that is closed unless someone opens it protects people who forget.

3. Sharing Is a Decision, Not an Accident

Households do need to share things. A calendar, a family project, a property being renovated, a matter that two people are handling together. These are set up deliberately.

Sharing on a SARION Appliance is configured explicitly, instance by instance, and permission by permission. Nothing is shared unless someone with the right access chose to share it.

SPECIFICATIONA Useful Test

For every item two people see in common, ask who decided that, and when. If the honest answer is "it just happened," the system is open by default.

4. What This Looks Like in Practice

  • A principal's private matters stay in the principal's instance, invisible to the spouse's and to staff.
  • A shared household calendar is explicitly shared by the people it concerns, and not by default with the whole family.
  • An adult child's instance belongs to the adult child, not to the parents.
  • A family project, such as a renovation, is shared with the people involved and nobody else.

The point of the design is that each arrangement is one the family chose.

5. Why Privacy Inside the Home Is Not a Small Matter

Family offices are usually careful about external threats and less careful about internal boundaries. In practice, much confidential information moves between people for ordinary reasons, and some of it should not have.

  • Estate planning. The details of a will or a trust are sensitive within the family itself.
  • Disputes. Family members can be on different sides of the same question.
  • Gifts and surprises. The simplest case, and a real one.
  • Health and personal matters. These belong to the person concerned.

A system that respects those boundaries reflects how the family actually works.

6. Staff and Advisers

A household has people who are not family: a chief of staff, an executive assistant, a house manager, an external adviser. Each should see what their role needs and no more.

The principle that applies to family members applies to them as well. Access should be granted deliberately, for a purpose, and reviewed when roles change. When a member of staff leaves, a family should be able to say exactly what they had access to.

7. Decisions to Make Before Commissioning

  • Who in the household will have their own instance?
  • What, if anything, will be shared between which instances, and who decides?
  • Who is the final authority if two people disagree about what is shared?
  • How are staff and advisers given access, and how is it removed?
  • What happens to an instance when its owner leaves the household or the family office?

Settling these before commissioning is far easier than sorting them out after the system holds years of conversations.

8. Availability by Tier

Per-member instances with selective sharing are advanced features available on SARION Regent and SARION Sovereign. SARION Confidant is a personal executive tier for a single principal.

To discuss how your household or family office should be configured, contact us at volta.quest.

TECHNICAL VALIDATION

Ecosystem & Cited Authorities

The architectural specifications, hardware topologies, and sovereign compute fabrics cited in this dossier interface with the following enterprise engineering entities:

ISO/IEC 27001

Access Control and Information Security Management

Explore Architecture Spec ↗

NIST AI Risk Management Framework

Governance and Accountability for AI Systems

Explore Architecture Spec ↗

Volta Sovereign AI / SARION

Per-Member Instances on SARION Regent and SARION Sovereign

Explore Architecture Spec ↗

SOVEREIGN ARCHITECTURAL ADVISORY

"Worth raising with your advisor or architect."

Volta Sovereign AI provisions custom on-premise compute appliances and bespoke cognitive layers for ultra-prime residences, private offices, and sovereign wealth entities. Zero upstream telemetry, zero cloud dependencies, absolute legal and physical data custody.