Published

Encounter

vr.wm-act-018 · wm-act-018-encounter

Describe a bounded interaction among parties while preserving separate participation, exchange, perspective, acknowledgement and outcome evidence.

World Models Activities and processes ACT.ENC

Bundle → Layer → Finding → Questions Classifiers What it is Why it exists Distinguishing features What robots and AI may and may not do Moral aspects Owners Links to other meta-models Identity and identifiers Direct properties Recognition Capabilities and actions Hazards and failure modes Standards and interfaces Context of use Sources

Bundle → Layer → Finding → Questions Filled

7 bundles · 14 layers · 14 findings · 42 questions

Encounter boundary Encounter-specific questions about encounter boundary.

Interaction criterion

Bind the occurrence master to a declared interaction segment. Similar participants, timing or meeting links alone cannot prove two reports describe the same encounter.

Encounter identity and engagement

Bind the occurrence master to a declared interaction segment. Similar participants, timing or meeting links alone cannot prove two reports describe the same encounter.

Which occurrence master and party-local identifiers refer to this encounter, and what evidence supports their reconciliation? identity
What engagement criterion distinguishes this interaction from a plan, unanswered attempt, broadcast or mere co-presence? definition
What makes this one segment rather than a recurring series, parent encounter or separate follow-up? composition

Encounter progress

Record encounter-specific progress assertions against the occurrence master. An imported planned or cancelled record is not evidence that interaction happened; record correction is not a new occurrence.

Planned and observed progress

Which current progress assertion is planned, attempted, active, ended, cancelled, entered in error or unresolved under the adopted profile? state
What observation supports opening or ending actual engagement rather than merely opening or closing its record? event
How are no-show, disconnection, resumption and conflicting closure reports represented without forcing agreement? exception

Participation and authority Encounter-specific questions about participation and authority.

Party involvement

Identify participating roles, including representatives, interpreters and automated agents, separately from invitees and observers. Unresolved identity may use protected local placeholders; placeholders are not proof of distinct parties.

Actual and intended participants

Which parties actually engaged, were merely invited, observed, or remain unidentified, and what supports each status? relationship
During which segments did each participant join, leave or participate intermittently? temporal
Which participant is a person, organization, group or automated agent, and what principal does the role represent? classification

Representation limits

Keep authority to speak, attest, disclose and bind a principal distinct. Party perspectives are separately stewarded records; stewardship does not settle property rights or authorize disclosure.

Delegation and perspective stewardship

Keep authority to speak, attest, disclose and bind a principal distinct. Party perspectives are separately stewarded records; stewardship does not settle property rights or authorize disclosure.

What mandate, scope and effective period allow a representative to act for a principal in this interaction? authority
Who stewards each party account and shared record, and under what accountable policy? ownership
Which proposed commitments or acknowledgements exceed the recorded mandate and require referral? constraint

Channel and time Encounter-specific questions about channel and time.

Communication setting

An interaction may move among in-person, remote and written channels. Store protected endpoint and place references per segment, never access credentials or transport machinery.

Channels and locations

An interaction may move among in-person, remote and written channels. Store protected endpoint and place references per segment, never access credentials or transport machinery.

Which physical or virtual locations and channel segments contextualize the encounter? spatial
What language, interpretation or accessibility arrangements affected participation and record interpretation? requirement
Which channel identifiers or recording references must be withheld from each audience? security

Timing semantics

Keep planned bounds, observed engagement periods, participant intervals and record ingestion instants separate. Elapsed or connected time does not automatically measure attention, billable service or clinical care.

Bounds and timing uncertainty

What are the planned and observed bounds, their time zones, precision and reporting sources? temporal
If a duration is reported, which segments, units and exclusions define it and how uncertain is it? measurement
How are late reports, unknown ends, clock disagreements and date-only evidence preserved? quality

Exchanges and accounts Encounter-specific questions about exchanges and accounts.

Exchange references

Index exchanged messages, documents, object references and statements by source and recipient role. A transport receipt is not understanding, agreement, transfer of title or settlement.

Items and statements exchanged

Index exchanged messages, documents, object references and statements by source and recipient role. A transport receipt is not understanding, agreement, transfer of title or settlement.

What item or statement was exchanged, by which role and toward which recipient or audience? relationship
What distinguishes asserted dispatch, receipt, review and disputed delivery for this exchange? evidence
Which content can be referenced without copying sensitive payload into the encounter? privacy

Perspective records

Keep a unilateral account distinct from a shared proposal and an acknowledged revision. Multiple documents and translations may describe one encounter; preserve derivation and limited visibility.

Private and shared accounts

Keep a unilateral account distinct from a shared proposal and an acknowledged revision. Multiple documents and translations may describe one encounter; preserve derivation and limited visibility.

Which author, source material and transformation produced this account or translation? provenance
Which portions are private notes, shared proposals or content approved for a named audience? access
How does a corrected account relate to earlier versions without silently replacing acknowledged content? lifecycle

Acknowledgement and consequences Encounter-specific questions about acknowledgement and consequences.

Acknowledgement scope

Acknowledge exact record versions and scope per party. Silence, attendance, a digest or technical signature validity does not establish shared agreement; unsigned or disputed encounters remain representable.

Scoped acknowledgement evidence

What exact revision and content scope did each party acknowledge, reject or leave unanswered? evidence
What signature or acknowledgement validation result is available, and what trust or authority questions remain unresolved? validation
How are partial agreement, withdrawal, coercion concerns and later corrections recorded without rewriting prior assertions? exception

Consequences and continuation

Distinguish observed, proposed, agreed and disputed results, including no agreement. Link subsequent encounters and obligations to their masters without executing actions or determining legal or clinical effects.

Outcomes and follow-up references

Which result was observed or proposed, who supports it, and which qualifications or disagreements remain? decision
Which external task, commitment, transaction or clinical record carries any resulting obligation or observation? relationship
Which later encounter continues this one, and how is continuation distinguished from a child segment or recurring schedule? composition

Disclosure and record continuity Encounter-specific questions about disclosure and record continuity.

Authorized views

Assess collection, recording, transcription and disclosure separately under an adopting legal and purpose profile. Universal consent of all named parties is not assumed; absent or conflicting authority blocks local release.

Recording and disclosure authority

Which applicable rule and approved purpose authorize this specific recording, transcription or disclosure? authority
Whose data and sensitive inferences occur in the proposed view, including nonparticipants mentioned in the record? privacy
What evidence authorizes the recipient and exact scope, and when must the proposed release be refused or escalated? access

Retention and correction

Different accounts and recordings may have different retention rules. Referenced disposition authorities control execution; local correction history must not justify indefinite retention of personal content.

Correction and disposition obligations

Which retention rule, trigger, hold and disposition authority apply to each account and retained copy? retention
How can a party dispute or correct its account while preserving other parties assertions and signed-version meaning? lifecycle
What minimal lawful evidence can remain after payload erasure, and which remote copies cannot be claimed deleted? constraint

Evidence and interoperability Encounter-specific questions about evidence and interoperability.

Assertion quality

Record support and limitations for each encounter assertion. Presence logs, transcripts and party recollections can conflict; attribution and integrity do not decide which account is true.

Conflicting evidence and recognition

Record support and limitations for each encounter assertion. Presence logs, transcripts and party recollections can conflict; attribution and integrity do not decide which account is true.

Which evidence supports or contradicts each material encounter assertion and who supplied it? provenance
What limits arise from missing segments, transcript errors, interpretation or inferred participation? quality
Which discrepancies need an authorized reviewer instead of automatic account merging? validation

Profile bindings

Map only declared encounter facets to pinned external schemas. The general model is not identical to a clinical Encounter, a calendar event or a generic Activity.

Profile mapping and loss

Map only declared encounter facets to pinned external schemas. The general model is not identical to a clinical Encounter, a calendar event or a generic Activity.

Which source and target versions map identity, state, parties, bounds and acknowledgement scope without loss? interoperability
Which mandatory target fields or unsupported semantics require refusal, a qualified extension or a specialist profile? constraint
Which fixtures establish that no-show, partial participation, disputed records and clinical references survive the mapping? validation

Classifiers Filled

Family: World Models
Category: Activities and processes
Entry kind: event
Navigation path: NAV.ACT.ENC
Domain: ACT.ENC
Industry: Cross-industry
Tags: encounteract.enc
Also called: X5

What it is Filled

One encounter occurrence or explicitly planned, attempted or disputed encounter record. An occurred encounter needs evidence of engagement involving at least two distinct parties represented by role entries under an adopted interaction profile; incomplete identity is allowed without inventing parties. The two-party criterion is a local boundary decision, not a universal standard definition. Records persist independently of the event they describe.

In scope

Encounter-specific binding to occurrence identity, interaction kind, engagement criterion and segment bounds
Human, organization, group or automated-agent participation by reference with scoped roles and authority
Physical, remote, hybrid and bounded asynchronous channels, exchange references and timing uncertainty
Separate private accounts, proposed shared records, scoped acknowledgements, disputed outcomes and follow-up references
Policy-qualified access, evidence provenance, record corrections, retention and mapping limits

Out of scope

Generic occurrence identity issuance, lifecycle engine and conflict resolution belong to WM-ACT-015 or the adopting master
Scheduling, message transport, contract formation, payment settlement and task execution remain in their masters
Clinical care delivery and clinical observations or diagnoses are external domains, not mandatory content of every encounter
Person, organization, location, authority, consent, audit, retention execution and signature verification engines
Persistent relationships, unrestricted broadcasts and unobserved co-presence without evidence of interaction
Operational guidance for dangerous activities; any such encounter uses policy-level references only

Why it exists Filled

Describe a bounded interaction among parties while preserving separate participation, exchange, perspective, acknowledgement and outcome evidence.

Distinguishing features Derived, awaiting review

Unlike WM-ACT-015 Occurrence / Event: Accept conceptual EXTEND for the encounter-specific engagement and perspective facets; delegate generic event identity and state machinery. Executable inheritance awaits a pinned binding.
Unlike WM-ACT-014 Health Care Delivery: Incoming containment is conditional on a clinical profile. A generic meeting or negotiation is not thereby a healthcare event; this model cannot own care delivery.
Unlike WM-ACT-046 Clinical Observation / Diagnosis: Outgoing candidate containment is narrowed to optional external references in clinical profiles. Observations and diagnoses keep independent masters and need not exist for an encounter.
Unlike Appointment, message, transaction and persistent relationship masters: Invitations and calendar responses are plans; a message is an exchange artifact; a transaction outcome needs its own authoritative record; a recurring relationship is not one encounter.
Unlike Legacy X5 and unreviewed supplement: Retain party perspectives and optional mutual records. Reject mandatory countersigning, a single channel, one immutable record forever and universal all-party-consent disclosure. Multiple scoped revisions and disputed or absent outcomes are permitted.

Note: Derived from boundary notes against neighbouring models.

What robots and AI may and may not do Derived, awaiting review

Must not

Planned and unresolved records must not assert occurrence.
Deny access unless actor, purpose, recipient and exact perspective scope are authorized; participation alone grants no right to all private accounts.

Only with a human decision

Do not assume all-party consent is either always necessary or always sufficient.

May

Bind encounter evidence: Proposed local operation, not implemented. Prepare an encounter-specific projection linked to the authoritative occurrence master.
Record participation assertion: Proposed local operation, not implemented. Append a role-scoped participation account without upgrading invitation to attendance.
Index an exchange: Proposed local operation, not implemented. Link an already evidenced exchange to its item master and permitted audience.
Record scoped acknowledgement: Proposed local operation, not implemented. Record an existing party assertion against exact content and version, preserving disagreement.
Link result and continuation: Proposed local operation, not implemented. Record a qualified outcome and references to external follow-up masters.
Prepare an authorized local view: Proposed local operation, not implemented. Construct a minimal local review view from externally approved purpose and recipient scopes.
Assess profile mapping: Proposed local operation, not implemented. Compare declared encounter facets with a pinned target contract and record loss.

Note: Derived from functions, policies, CRUD and access rules; prohibitions were not authored for agents as such.

Moral aspects Derived, awaiting review

Do not assume all-party consent is either always necessary or always sufficient.
Privacy and records officer
Clinical and privacy sources are scoped examples, not universal definitions.
EDPB guidance concerns EU/EEA data protection; it does not settle national recording or signature law or worldwide privacy duties.
Reject the universal all-party-consent rule and automatic authority from participation.
Person, organization, location, authority, consent, audit, retention execution and signature verification engines
Reject mandatory countersigning, a single channel, one immutable record forever and universal all-party-consent disclosure.

Note: Sentences mentioning harm, privacy, consent or similar, collected from the specification.

Owners Filled

Steward

Accountable record custodian and participating-party roles with scope-specific authority evidence

Roles

Encounter record custodian: Maintain binding, profile and scoped record continuity
Party or authorized representative: Supply and qualify only assertions within the evidenced mandate
Evidence reviewer: Examine contradictory reports, identity matches and acknowledgement scope
Privacy and records officer: Approve recipient views, retention and disposition policy references
Profile maintainer: Pin schema mappings and record conformance limits

Links to other meta-models Filled

extends

WM-ACT-015 - Conceptual specialization of occurrence through engagement, party perspectives and scoped acknowledgement. Generic identity, event history, authority and conflict machinery stay in the occurrence master; runtime binding must be pinned.

references

WM-ACT-014 - Optional clinical context for the incoming care-delivery containment candidate; no generic requirement that every encounter belongs to care delivery.
WM-ACT-046 - Optional clinical observation or diagnosis reference. Candidate CONTAINS is qualified as a profile association; no mandatory child and no locally owned diagnosis lifecycle.

aligned

RFC 5545 - Calendar plan, attendee and recurrence references only; not evidence of actual engagement.
PROV-O 2013-04-30 - Attribution and derivation vocabulary alignment; no evidence truth or authority inference.
FHIR R5 5.0.0 Encounter - Selected clinical profile comparison only; no universal FHIR resource equivalence or implemented mapping.
Activity Vocabulary 2017-05-23 - Exchange and continuity vocabulary alignment; generic activities do not establish encounter engagement.
XML Signature 1.1 - Signed-scope and verification-evidence alignment only; signature execution and legal effect are external.

neighbor

WM-ACT-015 Occurrence / Event - Accept conceptual EXTEND for the encounter-specific engagement and perspective facets; delegate generic event identity and state machinery. Executable inheritance awaits a pinned binding.
WM-ACT-014 Health Care Delivery - Incoming containment is conditional on a clinical profile. A generic meeting or negotiation is not thereby a healthcare event; this model cannot own care delivery.
WM-ACT-046 Clinical Observation / Diagnosis - Outgoing candidate containment is narrowed to optional external references in clinical profiles. Observations and diagnoses keep independent masters and need not exist for an encounter.
Appointment, message, transaction and persistent relationship masters - Invitations and calendar responses are plans; a message is an exchange artifact; a transaction outcome needs its own authoritative record; a recurring relationship is not one encounter.
Legacy X5 and unreviewed supplement - Retain party perspectives and optional mutual records. Reject mandatory countersigning, a single channel, one immutable record forever and universal all-party-consent disclosure. Multiple scoped revisions and disputed or absent outcomes are permitted.

contains

WM-ACT-046

What else AI and robots need to interact with it Incomplete

Sources Filled

Internet Calendaring and Scheduling Core Object Specification (iCalendar) - IETF
PROV-O: The PROV Ontology - W3C
FHIR Encounter - HL7 International
Activity Vocabulary - W3C
Date and Time on the Internet: Timestamps - IETF
XML Signature Syntax and Processing Version 1.1 - W3C
Data protection basics - European Data Protection Board
Process personal data lawfully - European Data Protection Board

Open questions

Restore independent external review and complete claim, version, update, licensing and source-response verification before canonical promotion.
Develop jurisdiction and sector profiles for disputed, mediated, automated, asynchronous and clinical encounters while preserving separate authority and evidence ownership.
Build nested schemas and mapping fixtures for duplicate-party roles, no-show, hybrid participation, conflicting closure, partial acknowledgements, corrected signed content, scoped erasure and unmappable target constraints.
Independent second-provider review remains absent.
Direct HTTP and response hashes are unmeasured under the owner-reported sandbox restriction; coordinator verification is pending.
Executable nested schemas, event bindings, mapping fixtures, target versions and conformance testing remain incomplete.
Sector and jurisdiction rules for recording, representation, signatures, sensitive data, retention and compelled disclosure need qualified review.
Nonclinical trade, mediated group interaction, cross-border interpretation and asynchronous segment boundaries need additional profile evidence.

Machine files

Card as JSON Specification AGENTS.md Source Card backlog vercy.card/1

Provenance

world-models research · reviewable-draft

Built from: models/wm-act-018-encounter/spec.yaml