← Back to catalogue
Published

Interpersonal Relationship

vr.wm-per-011 · wm-per-011-interpersonal-relationship

Describe a dyadic interpersonal relationship through independent roles, validity and privacy-aware attributed perspectives.

World Models Society, people and institutions SOC.PER.REL

Bundle → Layer → Finding → Questions Filled

6 bundles · 12 layers · 12 findings · 36 questions

Relationship identity and participants Dyadic interpersonal relationship identity and participants.

Scoped relationship identity

Authored relationship-memory design for scoped relationship identity, qualified by perspective, time and authorized evidence; not a universal interpersonal truth judgment.

Scoped relationship identity record

Authored relationship-memory design for scoped relationship identity, qualified by perspective, time and authorized evidence; not a universal interpersonal truth judgment.

  1. Which master-qualified identifier distinguishes this relationship from either participant and its individual assertions? identity
  2. Which two person references and owning context define the record boundary? relationship
  3. Which identity ambiguity prevents linking or merging records safely? quality

Type and role direction

Authored relationship-memory design for type and role direction, qualified by perspective, time and authorized evidence; not a universal interpersonal truth judgment.

Type and role direction record

Authored relationship-memory design for type and role direction, qualified by perspective, time and authorized evidence; not a universal interpersonal truth judgment.

  1. Which versioned relationship type and participant roles are asserted? classification
  2. What direction, inverse or symmetry does that specific vocabulary define? relationship
  3. Which overlapping types or culturally specific labels must remain distinct? classification
Recognition and attributed perspectives Dyadic interpersonal recognition and attributed perspectives.

Assertion and evidence basis

Authored relationship-memory design for assertion and evidence basis, qualified by perspective, time and authorized evidence; not a universal interpersonal truth judgment.

Assertion and evidence basis record

Authored relationship-memory design for assertion and evidence basis, qualified by perspective, time and authorized evidence; not a universal interpersonal truth judgment.

  1. Who states that the relationship exists, using what source and method? provenance
  2. What observation or statement supports the claim without importing unnecessary private content? evidence
  3. Which confidence and limitations distinguish reported belief from verified status? quality

Reciprocity and disagreement

Authored relationship-memory design for reciprocity and disagreement, qualified by perspective, time and authorized evidence; not a universal interpersonal truth judgment.

Reciprocity and disagreement record

Authored relationship-memory design for reciprocity and disagreement, qualified by perspective, time and authorized evidence; not a universal interpersonal truth judgment.

  1. Which participant perspectives are available and which are unknown? evidence
  2. What evidence supports reciprocal recognition for this specific type rather than unilateral assertion? relationship
  3. Which denial, correction or dispute must coexist without declaring one person's account universal truth? exception
Roles, expectations and boundaries Dyadic interpersonal roles, expectations and boundaries.

Role scope and commitments

Authored relationship-memory design for role scope and commitments, qualified by perspective, time and authorized evidence; not a universal interpersonal truth judgment.

Role scope and commitments record

Authored relationship-memory design for role scope and commitments, qualified by perspective, time and authorized evidence; not a universal interpersonal truth judgment.

  1. Which social, care, professional or family role is relevant in this context? definition
  2. Which mutually agreed commitments or separately evidenced mandates are referenced? relationship
  3. Which limits prevent a role label from implying legal representation, duties or access rights? constraint

Contact and interaction boundaries

Authored relationship-memory design for contact and interaction boundaries, qualified by perspective, time and authorized evidence; not a universal interpersonal truth judgment.

Contact and interaction boundaries record

Authored relationship-memory design for contact and interaction boundaries, qualified by perspective, time and authorized evidence; not a universal interpersonal truth judgment.

  1. Which participant-stated contact preferences and boundaries apply in this context? constraint
  2. Which separate authorization is required before contacting or disclosing information to a related person? authority
  3. Which restriction, withdrawal or unknown preference requires withholding an automated action? access
Shared context and change Dyadic interpersonal shared context and change.

Encounters and shared activities

Authored relationship-memory design for encounters and shared activities, qualified by perspective, time and authorized evidence; not a universal interpersonal truth judgment.

Encounters and shared activities record

Authored relationship-memory design for encounters and shared activities, qualified by perspective, time and authorized evidence; not a universal interpersonal truth judgment.

  1. Which authorized encounters, activities or shared contexts are linked to this relationship? relationship
  2. Which source and period qualify each link without treating co-occurrence as proof of friendship or intimacy? evidence
  3. Which summaries can be retained without copying another person's protected messages or files? privacy

Relationship episodes and transitions

Authored relationship-memory design for relationship episodes and transitions, qualified by perspective, time and authorized evidence; not a universal interpersonal truth judgment.

Relationship episodes and transitions record

Authored relationship-memory design for relationship episodes and transitions, qualified by perspective, time and authorized evidence; not a universal interpersonal truth judgment.

  1. Which start, end or uncertain interval is asserted for each role or relationship episode? temporal
  2. Which attributed event supports a change, pause or ending without inventing emotional state? event
  3. Which continuation or renewed episode should remain separate from a corrected historical claim? lifecycle
Privacy and contested memory Dyadic interpersonal privacy and contested memory.

Purpose and minimum disclosure

Authored relationship-memory design for purpose and minimum disclosure, qualified by perspective, time and authorized evidence; not a universal interpersonal truth judgment.

Purpose and minimum disclosure record

Authored relationship-memory design for purpose and minimum disclosure, qualified by perspective, time and authorized evidence; not a universal interpersonal truth judgment.

  1. For which explicit purpose and authority may these relationship details be held? authority
  2. Which fields and participant references may each recipient see without leaking the relationship itself? privacy
  3. Which sensitive detail is unnecessary or must remain only in its authorized master? privacy

Correction, retention and retirement

Authored relationship-memory design for correction, retention and retirement, qualified by perspective, time and authorized evidence; not a universal interpersonal truth judgment.

Correction, retention and retirement record

Authored relationship-memory design for correction, retention and retirement, qualified by perspective, time and authorized evidence; not a universal interpersonal truth judgment.

  1. Which participant request or steward decision triggers review or correction of an assertion? process
  2. What retention or legal-hold policy governs each piece of evidence and its access restrictions? retention
  3. How is a local record retired or erased without claiming that the real-world relationship ceased or leaking deleted details in a tombstone? lifecycle
Interoperable and safe agent use Dyadic interpersonal interoperable and safe agent use.

Qualified mappings

Authored relationship-memory design for qualified mappings, qualified by perspective, time and authorized evidence; not a universal interpersonal truth judgment.

Qualified mappings record

Authored relationship-memory design for qualified mappings, qualified by perspective, time and authorized evidence; not a universal interpersonal truth judgment.

  1. Which selected fields map to a pinned relationship vocabulary or domain profile? interoperability
  2. What direction, perspective, temporal or privacy meaning would be lost by exporting a simple edge? quality
  3. Which mapping must be refused when the target cannot preserve required qualifiers? constraint

Validation and permitted operations

Authored relationship-memory design for validation and permitted operations, qualified by perspective, time and authorized evidence; not a universal interpersonal truth judgment.

Validation and permitted operations record

Authored relationship-memory design for validation and permitted operations, qualified by perspective, time and authorized evidence; not a universal interpersonal truth judgment.

  1. Which fixtures detect reversed roles, unsupported reciprocity and conflated episodes? validation
  2. Which authorization, expected revision and protected references must be checked before updating memory? authority
  3. Which failure or uncertainty requires safe refusal rather than identity merging, outreach or sensitive inference? security

Classifiers Filled

Family
World Models
Category
Society, people and institutions
Entry kind
relationship
Navigation path
NAV.SOC.PER.REL
Domain
SOC.PER.REL
Industry
Cross-industry
Tags
interpersonalrelationshipsoc.per.rel

What it is Filled

A relationship between two referenced persons in a governed context, with independently qualified assertions and role episodes; not a global social graph or objective intimacy assessment.

In scope

  • Scoped relationship identity, typed roles, direction and person references
  • Evidence, competing perspectives, role boundaries and episodes
  • Purpose-limited record access, correction and loss-aware projection

Out of scope

  • Person identity masters, multiparty groups and households
  • Automatic outreach, social trust scoring or sensitive relationship inference
  • Legal status adjudication, consent grants and private-message ingestion

Why it exists Filled

Describe a dyadic interpersonal relationship through independent roles, validity and privacy-aware attributed perspectives.

Distinguishing features Filled

  • A relationship between two specific people in a governed context, not a global social graph.
  • Each participant's perspective is recorded separately and may disagree.
  • Differs from a contact entry, which is one person's address book data.
  • Differs from legal representation and from groups or households of more than two people.

What robots and AI may and may not do Filled

Must not

  • Infer intimacy, kinship or sensitive status from names, locations or messages.
  • Treat one person's assertion as the other's consent.
  • Contact people on the basis of a relationship record.
  • Ingest private messages to enrich the record.
  • Reveal that a relationship exists to someone without access.

Only with a human decision

  • Resolving contradicting perspectives.
  • Disclosing relationship records to third parties.

May

  • Resolve a relationship within its context and permitted scope.
  • Record an attributed assertion or a participant's own perspective.
  • Record a change such as a relationship ending.
  • Export a minimized projection for a declared purpose.

Moral aspects Filled

  • Relationship data can expose people to abuse, stalking or discrimination.
  • The other person in the relationship has their own privacy rights.
  • Records of ended relationships should be correctable and not used against people.

Who is affected

  • Both participants
  • Family members and dependants
  • Carers and professionals who rely on the record

Owners Filled

Steward

Declare relationship-record steward and participants as distinct roles.

Roles

Dimension owner
Delegates local memory scope, not ownership of another person.
Relationship steward
Maintains qualified relation and episode records.
Contributor
Supplies authorized attributed assertions.
Reviewer
Checks perspective, direction and evidence limits.
Custodian
Enforces restricted access and retention.

Links to other meta-models Filled

references

  • WM-PER-001 - Candidate participant reference, never Person inheritance or ownership.

aligned

  • https://www.rfc-editor.org/rfc/rfc6350 - Selected RELATED fields with loss annotations.
  • https://hl7.org/fhir/R5/relatedperson.html - Limited patient-context mapping; not full RelatedPerson payload ownership.
  • https://schema.org/Role - Qualified role mapping, development-version hold.
  • https://xmlns.com/foaf/spec/ - Only appropriate knows semantics, never all relationships.
  • https://www.w3.org/TR/prov-o/ - Assertion attribution, not truth or consent.

neighbor

  • Person - Participants remain references; relationship is not a Person subtype despite registry parent navigation.
  • Contact - Contact detail and RelatedPerson serve different purposes; neither alone grants communication rights.
  • Legal representation - Role label is not sufficient evidence of mandate or legal rights.
  • Encounter - Co-occurrence does not establish friendship or intimacy under this conservative profile.
  • Group - Dyadic profile does not represent all multiparty social structures.

parent

  • WM-PER-001

What else AI and robots need to interact with it Filled

Identity and identifiers required Filled

  • Master-qualified opaque identifier
  • Governed issuer-qualified URI
  • Dimension-issued UUID

Direct properties not applicable Not applicable

Not applicable

Institutional or informational subject: no invented physical properties.

Recognition optional Filled

  • A relationship record has two person references, a type, roles, direction and validity.
  • Confused with contact lists, social network follows, households and legal guardianship.

Capabilities and actions required Filled

  • Resolve relationship: Proposed record operation: resolve relationship. Not an implemented social-action engine.
  • Append attributed assertion: Proposed record operation: append attributed assertion. Not an implemented social-action engine.
  • Record participant perspective: Proposed record operation: record participant perspective. Not an implemented social-action engine.
  • Link context evidence: Proposed record operation: link context evidence. Not an implemented social-action engine.
  • Record episode change: Proposed record operation: record episode change. Not an implemented social-action engine.
  • Export minimized projection: Proposed record operation: export minimized projection. Not an implemented social-action engine.

Hazards and failure modes required Filled

  • Exposure of a hidden relationship to an abuser.
  • Wrong next-of-kin used in an emergency.
  • Social scoring from relationship networks.

Standards and interfaces required Filled

  • HL7 FHIR RelatedPerson resource.
  • HL7 v3 RoleCode personal relationship codes.
  • vCard RELATED property, IETF RFC 6350.
  • schema.org Person relationship properties.
  • FOAF knows property.

Context of use required Filled

  • FHIR healthcare and ICO UK guidance are bounded examples; role meanings vary by vocabulary and culture.

Sources Filled

  1. vCard Format Specification - IETF
  2. FHIR RelatedPerson - HL7
  3. Role - schema.org
  4. FOAF Vocabulary Specification - FOAF Project
  5. PROV-O: The PROV Ontology - W3C
  6. Principle (c): Data minimisation - Information Commissioner Office

Open questions

  • Independent review and exact source/license/profile verification.
  • Typed nested schemas and negative privacy/episode tests.
  • Ratified composition, multiparty profiles and safe mapping adapters.
  • Claude and Grok each timed out once; no independent external review.
  • Selected clauses only; RFC updates/errata, dated pins and licenses pending.
  • schema.org development version and ICO under-review guidance need stable profile verification.
  • RFC and ICO HEAD unavailable despite readable text.
  • No universal social/kinship taxonomy, multiparty profile or sensitive-inference mechanism.
  • No executable nested schemas, reciprocity/privacy fixtures or ratified composition adapters.

Machine files

Provenance

world-models research · reviewable-draft

Built from: models/wm-per-011-interpersonal-relationship/spec.yaml, ver-cy/world-models/card-supplements/wm-per-011-interpersonal-relationship.json