Published

Communication Interaction

vr.wm-act-027 · wm-act-027-communication-interaction

Provide the format-neutral context an agent needs to open, conduct, evidence, classify, correlate and close a communication interaction - a bounded exchange of contact turns between identified parties across one or more channels - with its participant roster, channel and endpoint bindings, turn content, delivery evidence, lifecycle state, outcome and governance references.

World Models Activities and processes ACT.COM

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

6 bundles · 15 layers · 27 findings · 104 questions

Interaction Definition, Identity and Classification Establishes what one Communication Interaction record is, how it is typed, and how it is identified and correlated across channels and systems.

Subject Definition and Boundary

The bounded exchange that a single interaction record represents, and its classification vocabulary.

Interaction Unit of Account

The rule set determining what constitutes one interaction record: which exchange is enclosed, when a channel switch or idle gap starts a new record, and whether the record is a container of turns or a single atomic transfer.

What exchange boundary does a single communication interaction record enclose? definition
When does a channel switch continue the existing interaction rather than open a new one? decision
Which idle interval or closure event terminates an interaction for record-keeping purposes? constraint
Is an attempted but unconnected contact recorded as an interaction? exception

Interaction Classification Scheme

The typing dimensions carried on the interaction - purpose/reason, business category, priority, medium and activity verb - and the controlled vocabularies bound to each.

Which independent classification dimensions does the interaction carry? classification
Which authority governs each controlled vocabulary used for typing? authority
How is the business reason for the interaction distinguished from its outcome? definition
What determines the priority value recorded on the interaction? constraint

Identity and Correlation

Identifier assignment for the interaction and its turns, and the correlation keys that hold a conversation together across channels and systems.

Interaction Identity and Correlation Keys

How the interaction root and each turn are identified, which identifier is authoritative, and which secondary keys (channel-native message IDs, thread IDs, room IDs, provider references) support correlation without becoming the identity.

Which system holds the authoritative identifier for this interaction record? identity
How are channel-native message identifiers retained alongside the internal turn identifier? interoperability
Which correlation keys allow the same conversation to be recognised across two channels? relationship
What happens to identifiers when two interaction records are merged or one is split? lifecycle

Participants, Roles and Channel Binding Who is party to the interaction and in what role, and through which channel and endpoint each of them is reachable.

Participant Roster and Roles

The set of parties attached to the interaction, their communication roles, and how that membership changes over the interaction's life.

Participant Roles and Party References

How each participant is referenced into the external party model and which communication role they hold - initiator, addressee, copied, blind-copied, observer or handling agent - including visibility rules attached to the role.

How is each participant referenced into the authoritative party model? relationship
Which communication roles are permitted on a participant entry? classification
How are blind-copied participants hidden from other participants of the same interaction? privacy
How is an anonymous or not-yet-identified contact represented as a participant? exception

Participant Membership Lifecycle

The states a participant passes through within the interaction - invited, active, departed, removed, barred - and the events that change them.

Which membership states may a participant occupy during the interaction? state
Who is authorised to add or remove a participant mid-interaction? authority
What portion of prior turns becomes visible to a participant joining late? access

Channel and Endpoint Binding

The channels used, their capability constraints, the endpoint addresses bound to each participant, and the direction of the exchange.

Channel Classification and Capability

Which channel each turn used, how channels are typed, and which capability constraints (message size, media types, template requirements, encryption, synchronicity) the channel imposes on the interaction.

Which controlled vocabulary types the channel of an interaction or turn? classification
Which channel capability constraints must be recorded to explain what was sendable? constraint
How does one interaction record more than one channel across its turns? composition
Is the channel end-to-end encrypted, and what does that imply for stored content? security

Endpoint Binding and Direction

The concrete endpoint addresses used at each end of a turn, including proxy or service-owned addresses, and the direction and initiation attribution of the exchange.

Which endpoint address pair carried each turn? identity
How is the direction of the interaction determined and recorded? definition
Which participant initiated the interaction and by what evidence? provenance
How is a change of a participant's endpoint mid-interaction recorded? event

Turns, Content and Threading The ordered turns that make up the interaction, the content they carried, and the relations that thread them to each other and to other records.

Turn and Content Structure

Structure of an individual turn and of the content and attachments it carried.

Turn Record Structure

The minimum structure of one turn: author, sequence position, channel binding, timestamps, subject or topic, and the reference to its content.

What is the minimum viable set of fields for a recorded turn? requirement
How is the canonical order of turns determined when timestamps disagree? temporal
How is the acting author distinguished from the party on whose behalf the turn was sent? ownership
How are edits, replacements and redactions of an already recorded turn represented? lifecycle

Content Payload and Attachments

The renderable content of a turn and any attached files, including media type, size, integrity digest, language and the distinction between inline body parts and downloadable attachments.

Which alternative representations of the same turn content are retained? composition
What distinguishes an inline body part from a downloadable attachment? definition
How is the integrity of stored content and attachments demonstrated? evidence
In which language and script was the content expressed? quality

Threading and Linkage

Relations among turns and interactions, and links from the interaction to records owned by other models.

Thread and Reply Relations

How reply chains and threads are derived or asserted, covering identifier-based derivation, explicit relation events, and the treatment of subject-line heuristics.

By what rule is thread membership of a turn decided? relationship
Is the thread a derived view or a stored asserted relation? provenance
Can a thread span more than one channel, and how is that asserted? interoperability
How is a conflict resolved when identifier evidence and asserted threading disagree? exception

Linkage to External Records

Typed links from the interaction to records owned elsewhere - the request or order that prompted it, the case or encounter it belongs to, the subject it concerns, and sibling interactions.

Which typed link roles may an interaction hold to records outside this model? relationship
Who or what is the subject the interaction is about, as opposed to its participants? definition
What happens to a link when the target record is withdrawn or merged? validation

Lifecycle, Time and Outcome The state the interaction is in, who is handling it, the time points and windows that govern it, and how it concludes.

Interaction State and Handling

Lifecycle states of the interaction record and the assignment of responsibility for handling it.

Interaction State Machine

The permitted lifecycle states of the interaction, the transitions between them, the reasons recorded on transition, and the treatment of erroneous records.

Which lifecycle states may an interaction record occupy? state
Which state transitions are permitted and which are forbidden? lifecycle
What reason must accompany a transition to a non-completion state? requirement
How is a record created in error withdrawn without destroying evidence? exception

Handling Assignment State

Which queue, team or individual currently holds responsibility for the interaction, how that assignment changed, and what accountability the assignment establishes.

Who currently holds handling responsibility for this interaction? ownership
How is a transfer of handling responsibility recorded? process
What represents an interaction that is awaiting assignment? state

Temporal Semantics

The time points, periods and channel-imposed windows that govern the interaction.

Interaction Time Points and Periods

Which distinct times are recorded - authored, sent, received by the store, delivered, read, observed, ingested - the interaction period as a whole, and the timestamp format and offset requirements.

Which distinct time points must be recorded separately rather than collapsed? temporal
What timestamp format, precision and offset are required? constraint
Whose clock authoritatively stamps each recorded time point? provenance
How is the overall interaction period bounded for a long-running asynchronous conversation? measurement

Engagement Windows and Timers

Channel- and rule-imposed windows that constrain when a party may be contacted or a free-form reply may be sent, and the timers that close or reclassify an interaction.

Which event opens a channel engagement window and when does it expire? event
What changes about permissible outbound content once the window has closed? constraint
Which time-of-day or calendar restrictions applied to outbound contact? requirement
Which inactivity timers change the interaction state automatically? process

Outcome and Disposition

How the interaction concluded, what was resolved, and the human or automated wrap-up recorded against it.

Outcome and Wrap-Up Record

The recorded outcome, resolution and follow-up commitment for the interaction, together with the notes authored at close, distinguishing outcome from lifecycle state.

Which outcome and resolution values may be recorded at close? classification
Who authored the wrap-up note and were they human or automated? provenance
What follow-up commitment was made and where is it tracked? process
How is the reliability of a generated summary distinguished from a verified one? quality

Delivery Evidence, Provenance and Measurement What can be demonstrated about the interaction: whether it reached its recipient, who observed it, what was captured, and what is measured from it.

Delivery and Receipt Evidence

Evidence of what happened to a turn after it was submitted, and of recipient engagement with it.

Delivery Status Evidence

The chain of submission and delivery outcomes recorded for an outbound turn - accepted, sent, delivered, failed, expired - each with its reporting source, timestamp and failure reason.

Which delivery outcome states are recorded for an outbound turn and in what order? state
How is platform acceptance of a send request distinguished from actual delivery? evidence
What failure reason and reporting authority are recorded for an undelivered turn? exception
How is delivery evidence held separately for each recipient of a multi-recipient turn? composition

Engagement and Read Signals

Signals that a recipient opened, read or acted on a turn, and the honest limits of what each signal proves.

Which engagement signals are captured for a turn? measurement
What does each engagement signal actually evidence, and what does it not? quality
Under what conditions may read or open tracking be recorded at all? privacy
To which participant is an engagement signal attributed when several share an endpoint? identity

Provenance and Capture

Which system observed, authored or reconstructed the record, and what durable capture exists of the exchange itself.

Capture Provenance and System of Record

Attribution of the interaction record to the system that captured it, the fidelity of that capture, and which system is authoritative when several hold a version.

Which system captured this interaction record and by what method? provenance
Which holder is authoritative when several systems hold a version of the same interaction? authority
How faithful is the stored record to the original exchange? quality
How is a manually entered or reconstructed interaction distinguished from an observed one? validation

Recording and Transcript Material

Durable capture of the exchange itself - media recordings and transcripts - with their notification basis, integrity protection and relationship to the turns they evidence.

On what basis was the exchange recorded, and were participants notified? authority
How is a recording protected against undetected alteration? security
How does a transcript segment map onto the turns it represents? composition
What is recorded when the exchange should have been captured but was not? exception

Interaction Measurement

Quantities derived from the interaction record and the definitions that make them comparable.

Interaction Measures and Their Definitions

Counts and durations computed from the interaction - turn counts, response latency, handling duration, wait time, transfer count - each with an explicit definition, unit and derivation base.

How is each derived measure defined in terms of recorded time points? measurement
Which periods are excluded from a duration measure and why? constraint
Are measures stored as materialised values or recomputed on demand? decision

Permission, Confidentiality, Retention and Interoperability The governance references the interaction record must carry, and the bindings that let it be exchanged and validated.

Permission Basis and Contactability Signals

References to the permission decision that authorised an outbound contact, and the suppression or revocation signals observed within the interaction itself.

Permission Basis Reference

The reference this record carries to the permission or lawful-basis decision that was in force when an outbound turn was sent, together with the sender-identification content that had to accompany it.

Which permission decision authorised this outbound contact, and where is it held? authority
What minimum snapshot of the permission decision is retained on the interaction? evidence
What sender identification and cessation route accompanied the outbound turn? requirement
How is an outbound turn recorded when no permission reference can be resolved? exception

Suppression and Revocation Signals in the Exchange

Recognition and recording of stop, unsubscribe or objection expressions that occur inside the interaction, as observations to be forwarded to the permission model rather than acted on here.

Which expressions within a turn are recorded as revocation or objection signals? event
How is a recognised revocation signal handed to the model that owns permission state? process
What evidence is retained about how quickly the signal was passed on? evidence
How is an ambiguous or partial revocation expression recorded? exception

Confidentiality Markers and Retention Binding

Classification and redaction markers carried on the record, and the retention class bound to it for another model to execute.

Visibility Classification and Redaction Markers

Confidentiality classification of the interaction and its parts, plus redaction and masking markers that record what has been withheld and why, without performing enforcement.

What confidentiality classification applies to the interaction and to individual turns? security
Which parts of the content carry heightened sensitivity requiring extra handling? privacy
What is retained about content that has been redacted or masked? validation
Which model evaluates and enforces access based on these markers? access

Retention Class and Disposition Binding

The retention class bound to the interaction, the trigger that starts its retention period, any legal hold marker, and the tombstone left when disposition is executed elsewhere.

Which retention class applies to this interaction and what triggers its period? retention
How is a conflict between competing retention obligations resolved on one record? constraint
What marks an interaction as being under a hold that suspends disposition? authority
What remains after disposition has been executed by the owning model? lifecycle

Interoperability and Validation

Alignment bindings to external interaction vocabularies, the validation rules that keep records defensible, and the handling of degraded or partial capture.

External Schema Alignment Bindings

Declared, evidence-backed alignments between this model's elements and external interaction schemas and vocabularies, together with the conflicts those alignments expose.

Which external interaction schemas is this record aligned to and at which version? interoperability
Which semantic conflicts between aligned schemas must be recorded rather than resolved silently? validation
On what evidence may conformance to an external schema be claimed? evidence
Which elements survive a round trip through an external representation and which do not? quality

Record Validation and Degraded Capture

The rules that make an interaction record acceptable, and the explicit handling of partial, delayed, duplicated or unverifiable records so that gaps are visible rather than silently absorbed.

What is the minimum set of assertions for an interaction record to be acceptable? validation
How is a duplicate interaction record detected and reconciled? identity
How is a turn that arrives out of order or long after the fact incorporated? temporal
How is a partially captured interaction represented without implying completeness? quality

Classifiers Filled

Family: World Models
Category: Activities and processes
Entry kind: aggregate
Navigation path: NAV.ACT.COM
Domain: ACT.COM
Industry: Cross-industry
Tags: communicationinteractionact.com

What it is Filled

WM-ACT-027 models the interaction record as an aggregate: an interaction root carrying identity, classification, participants-in-role, channel and endpoint bindings, ordered turns with content and attachments, threading relations, lifecycle and handling state, temporal points and windows, delivery and engagement evidence, outcome/disposition, and typed references to the party, permission, access, retention and audit models that own their own semantics. It stops at transport protocols, party master data, permission evaluation, policy enforcement, audit-trail production and disposition execution. It is storage- and interface-neutral: JSON, YAML, Markdown, HTML, Git, MCP and MongoDB are projections of these semantics, not their definition.

In scope

The interaction as a unit of account: what opens one, what continues it across a channel switch, what closes it
Interaction identity, correlation keys and cross-channel identifier resolution
Participants in roles (initiator, addressee, copied, observer, handler) as references into an external party model
Channel classification, channel capability constraints, and endpoint/address bindings including proxy-address pairs
Direction (inbound, outbound, internal) and initiation attribution
Ordered turns with authorship, sequence, content references and attachments
Threading, reply and relation structure between turns and between interactions
Lifecycle and handling state, assignment of handling responsibility, and state-change reasons
Interaction time points, periods and channel engagement windows/timers
Delivery, receipt, read and engagement evidence attached to turns
Capture provenance: which system observed or authored the record and how faithfully
Outcome, resolution and wrap-up disposition of the interaction
Confidentiality/visibility classification and redaction markers carried on the record
References to permission basis, retention class, access policy and audit records owned by sibling models
Alignment bindings to external interaction schemas and vocabularies

Out of scope

Party, organisation and person master data and their identity lifecycle (owned by the party model)
The canonical contact-point/electronic-address registry and address verification
Permission and consent capture, evaluation and withdrawal semantics (this model carries only a reference to the decision)
Runtime access-control evaluation and enforcement (this model carries classification markers only)
Audit-trail creation, immutability guarantees and audit query semantics
Execution of deletion, anonymisation or disposition (this model carries the class and a tombstone marker only)
Transport and signalling protocol behaviour (SIP/IMS sessions, SMTP relay, SMS submission, charging/CDR production)
Case, ticket, order or service-request lifecycle (referenced, not reproduced)
Campaign, journey and outbound orchestration logic
Bot/NLU intent model training, ranking and dialogue policy
Media file storage, transcoding and CDN delivery
Workforce management, agent scheduling and staffing forecasts
Billing, rating and settlement for communication traffic

Why it exists Filled

Distinguishing features Filled

An interaction is the exchange between parties over a channel, made of turns; a single message (WM-REC-003) is one of its parts.
It records what was observed and referenced, never a permission, access or audit decision.
Platform acceptance of a send is not delivery, and an engagement signal is not proof of comprehension.
Gaps, late or duplicate turns stay visible and marked rather than absorbed.

What robots and AI may and may not do Filled

Must not

Record platform acceptance as delivery.
Treat opens or clicks as proof that a person understood a message.
Expose blind-copied participants or redacted spans to other participants.
Send an outbound turn without a resolvable permission basis reference.
Present a partial record as complete.

Only with a human decision

Closing an interaction with a legal or contractual outcome.
Disclosing an interaction to a third party.
Handling a dispute about whether a revocation was received.

May

Open an interaction and bind its channel endpoints.
Append turns and resolve thread membership.
Record delivery evidence with its source.
Link the interaction to related records such as orders, cases or requests.

Moral aspects Filled

Communications are private; content and traffic data need protection.
Service interactions should treat people with dignity, including clear disclosure when they are talking to an agent.
Unwanted contact burdens people and must respect their objection.

Who is affected

Parties to the interaction
Human and software agents handling it
Third parties mentioned in it

Owners Filled

Steward

The adopting Dimension must designate a single accountable owner for the interaction record population and publish the system of record for each channel it operates

Roles

Interaction Record Owner: Owns the interaction record population and its published unit-of-account, lifecycle and continuation rules; Designates the system of record per channel and resolves divergence between holders; Approves model version changes and their compatibility classification
Channel Steward: Maintains the channel registry entries, capability constraints and engagement window rules used by this model; Reviews channel-native identifier stability and correlation key quality; Signals channel deprecation and migration impact on open interactions
Records and Retention Officer: Binds retention classes and reconciles competing retention obligations to one effective period; Issues and releases hold markers and confirms tombstone completeness after disposition executed elsewhere; Verifies that recordings and transcripts subject to obligation are held on a compliant medium
Privacy and Permission Liaison: Defines the permission basis reference contract between this model and the permission model; Confirms that revocation signals observed in turns are handed off within the applicable deadline; Reviews sender identification and cessation route requirements per jurisdiction and channel
Interoperability Steward: Maintains alignment bindings and interoperability binding profiles with their target schema versions; Records semantic conflicts and round-trip losses instead of resolving them silently; Executes and dates conformance evidence before any conformance claim is published
Data Quality Reviewer: Monitors validation status, duplicate detection, late arrivals and completeness indicators; Audits capture gaps and fidelity levels against expected coverage; Escalates systematic capture degradation to the record owner and channel steward

Links to other meta-models Filled

child

WM-ACT-018 (parent activity model in NAV.ACT) - Registers Communication Interaction as a specialisation of the parent activity concept, inheriting generic activity identity and actor structure rather than restating it.

references

Party and party-role model - Participants are carried as party references with a role, mirroring the TMF683 relatedParty pattern; party attributes, identity resolution and lifecycle remain with the party model.
Contact point and electronic address registry model - Endpoint bindings cite canonical contact points; address verification, reachability and ownership stay in the registry.
Channel and channel-capability registry model - Channel codes and capability constraints are dereferenced from the channel registry so that channel definitions are not duplicated per interaction.
Permission, consent and preference model - Optional at interaction level. For an outbound turn that requires permission or lawful-basis evidence, carry a resolvable decision reference and point-in-time basis snapshot. Inbound and internal interactions do not invent a permission decision. Capture, evaluation, validity and withdrawal remain owned entirely by the permission model.
Case, request or service-order model - Provides based-on and part-of links so an interaction can be situated in a wider work item without importing that item's lifecycle.
Content and media asset model - Attachment and recording bytes, storage location and transcoding are owned by the content model; this model holds references, media types and digests.
Records retention and disposition model - Supplies the retention class, schedule and disposition execution; this model contributes only the trigger time, hold marker and tombstone shape.
Access-control and authorization policy model - Consumes the confidentiality and redaction markers carried here; evaluation and enforcement of access requests are never performed by this model.
Audit trail and event log model - Receives access and change events concerning interaction records; FHIR's explicit Communication-versus-AuditEvent split keeps audit-trail semantics outside this boundary.

composes

Identifier and reference mixin - Supplies the shared pattern for authoritative identifier, alias retention, superseded-by links and correlation keys used across the interaction root, turns and artifacts.

aligned

Temporal expression pattern (RFC 3339 profile) - Binds all recorded time points to the RFC 3339 profile including seconds, explicit offset and the unknown-offset convention.
TM Forum TMF683 Party Interaction resource - Element-level alignment for direction, status, channel, interactionDate, interactionItem, relatedParty, note and interactionRelationship, recorded as alignment with conflicts noted rather than a conformance claim.
HL7 FHIR Communication resource - Alignment for status, category, medium, sender, recipient, sent, received, payload, inResponseTo and about in healthcare-facing deployments, without adopting FHIR's clinical context model.
W3C Activity Streams 2.0 vocabulary - Alignment for actor, object, target, audience targeting and inReplyTo when interactions are projected into social or federated activity feeds.

extends

Interaction analytics and reporting model - Consumes measure definitions and derived durations declared here and extends them into aggregate reporting; aggregation, benchmarking and visualisation are not modelled locally.

neighbor

Party / party-role model (e.g. TM Forum TMF632/TMF669 pattern) - TMF683 carries only relatedParty references with a role; the interaction record must not restate party attributes, party identity resolution or party lifecycle.
Permission / consent model - ePrivacy and 47 CFR 64.1200 place consent capture, validity and revocation with the permission holder; this model records only the reference to a permission decision that was in force at send time, never the evaluation.
Clinical or business request model (FHIR CommunicationRequest) - FHIR separates the planned/ordered communication from the record of one that occurred; WM-ACT-027 covers the occurrence, with the request kept as a basedOn reference.
Audit / disclosure log (FHIR AuditEvent pattern) - FHIR explicitly distinguishes Communication from AuditEvent; system-level disclosure tracking and audit-trail semantics stay in the audit model.
Transport and protocol layer (RFC 5322 trace fields, Matrix federation, carrier submission) - Trace/Received fields and protocol event graphs are informational transport artefacts; this model consumes their identifiers and status outcomes without owning routing or delivery mechanics.
Records retention and disposition model - Sector rules such as MiFID II impose fixed retention on communication records, but the retention schedule and its execution belong to the retention model; this record only binds a retention class and a disposition marker.
Content / media asset model - Attachment bytes, transcoding and storage location are owned by the content model; this model carries attachment references, media type and integrity digests.

parent

WM-ACT-018

What else AI and robots need to interact with it Filled

Sources Filled

TMF683 Party Interaction API, OpenAPI (Swagger) definition v4.0.0 - TM Forum
FHIR R5 Communication Resource - HL7 International
Activity Streams 2.0 Vocabulary - World Wide Web Consortium (W3C)
RFC 8621: The JSON Meta Application Protocol (JMAP) for Mail - Internet Engineering Task Force (IETF)
Matrix Client-Server API specification - The Matrix.org Foundation C.I.C.
Message - Schema.org Type - Schema.org (W3C Schema.org Community Group)
Directive 2002/58/EC concerning the processing of personal data and the protection of privacy in the electronic communications sector (ePrivacy Directive) - European Parliament and Council of the European Union
47 CFR 64.1200 - Delivery restrictions - Legal Information Institute, Cornell Law School (reproducing US Code of Federal Regulations, FCC)
RFC 5322: Internet Message Format - Internet Engineering Task Force (IETF)
RFC 3339: Date and Time on the Internet: Timestamps - Internet Engineering Task Force (IETF)
Regulation (EU) 2016/679 (General Data Protection Regulation), consolidated text - European Parliament and Council of the European Union
WhatsApp Business Platform Cloud API - Send Messages - Meta Platforms, Inc.
Commission Delegated Regulation (EU) 2017/565 supplementing Directive 2014/65/EU as regards organisational requirements and operating conditions for investment firms - European Commission

Open questions

Re-pin the weak citations: replace SRC-008 with the official eCFR or FCC text, fix SRC-005 to an immutable Matrix specification version rather than 'latest', date SRC-012 or replace it, and re-verify the SRC-011 consolidation currency.
Secure a non-vendor, standards-track source for the acceptance-is-not-delivery distinction, which currently rests structurally on tier-3 WhatsApp Cloud API documentation and is acknowledged as over-specified against transports that cannot supply the distinction.
Obtain an independent structural review — successor second provider or human boundary reviewer — of the aggregate-root granularity code, since the interaction-versus-atomic-transfer resolution rests on a single provider's judgement with no cross-check.
Close the function-coverage gaps identified here: participant membership change, interaction record merge and split, and attachment of recording and transcript material, each with its own source support.
Locate a normative cross-channel interaction taxonomy so the classification dimensions can rest on a governing authority rather than convergence across TMF683, FHIR and Activity Streams, as the provider's own checklist flags.
Model the declared gaps that remain unsourced: accessibility obligations attaching to channel provision, cross-border transfer conditions for interaction content and recordings, automated-authorship attribution and disclosure, and scaling guidance for large group or broadcast interactions.
Ratify the parent relation to WM-ACT-018 and the proposed composition links in the relationship ledger so the ownership boundary moves from asserted to confirmed.
No channel-specific profile is provided for voice/IMS session semantics, RCS Universal Profile capabilities or postal contact; these would need per-channel extension profiles with their own primary sources.
Bot, agent-assist and automated-authorship provenance is modelled only as an automation indicator and generation method; detailed model-attribution and disclosure obligations are not developed.
Accessibility obligations attaching to channel provision are identified as a gap rather than modelled.
Cross-border transfer conditions for interaction content and recordings are not modelled; they are assumed to be owned by a data-transfer or jurisdiction model.
Group and broadcast interactions with very large participant counts are supported structurally but no scaling or partitioning guidance is given.
No primary source was secured for a normative cross-channel interaction taxonomy; the classification dimensions are convergent across TMF683, FHIR and Activity Streams rather than drawn from one authority.

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-027-communication-interaction/spec.yaml, ver-cy/world-models/card-supplements/wm-act-027-communication-interaction.json