← Catalogue
World Models · legacy example

Message & Communication

This meta-model describes communications between agents: messages with parts and attachments, organized in threads, carried over channels to addresses, with delivery evidence and consent to be contacted. It is its own model because exchange semantics (send, deliver, read, bounce, reply) are identical whether the channel is email, chat, postal or broadcast, and because delivery evidence and consent form a distinct governed record separate from the content documents a message may carry.

AI YAMLAGENTS.mdSource
IDworld.n7-message-and-communication
Version history0.2.0-legacy
CategoryReference example
IndustryCross-industry
Domainknowledge-information
Tagsmessage, communication
Data structure

Bundles and layers

Bundle

exchange

What was said and in which conversation

Layers

messageAndContent`: messages, parts, attachments · `threadAndConversation`: threads, topics, participation

Bundle

transport

How it travelled

Layers

channelAndAddress`: channels, providers, address schemes · `deliveryAndReceipt`: delivery status and evidence

Bundle

custody

Permission and preservation

Layers

consentAndPreference`: consent to contact, preferences, revocation · `archivalRetention`: retention of communication records

Findings

Catalogue-native findings must describe the information grouped by each layer. This legacy version does not declare them separately.

Questions & artifacts

Questions, artifact requirements and serial naming rules are required by Vercy vNext; they remain unassigned in this reference version.

Service layers

How this specification operates

Dimension & namespace

  • REFERENCE `world.person` (H1): individual senders, recipients and consent subjects.
  • REFERENCE `world.organization` (O1): organizational senders and channel providers.
  • REFERENCE `world.documentRecord` (N1): attachments resolve to governed documents held there.
  • REFERENCE `world.identifierNaming` (N8): address schemes are registered identifier schemes.
  • REFERENCE `world.languageTerminology` (N9): language tagging of message content.
  • imports: rfc-5322 (ALIGN): message and header semantics.
  • imports: mime (ALIGN): multipart content and media type semantics.
  • imports: w3c-activitystreams-2 (ALIGN): actor-to-actor messaging semantics for social channels.

Canon, patches & standards

  • REFERENCE `world.person` (H1): individual senders, recipients and consent subjects.
  • REFERENCE `world.organization` (O1): organizational senders and channel providers.
  • REFERENCE `world.documentRecord` (N1): attachments resolve to governed documents held there.
  • REFERENCE `world.identifierNaming` (N8): address schemes are registered identifier schemes.
  • REFERENCE `world.languageTerminology` (N9): language tagging of message content.
  • imports: rfc-5322 (ALIGN): message and header semantics.
  • imports: mime (ALIGN): multipart content and media type semantics.
  • imports: w3c-activitystreams-2 (ALIGN): actor-to-actor messaging semantics for social channels.

Artifact formats & serial data

Format-independent core. Concrete artifact formats and naming prefixes are not declared in this legacy version.

Policies & accepted processes

  • `deliveryServiceContract`: terms between sender and channel provider for carriage and receipts.
  • `archiveAccessContract`: terms for access to retained communication records.
  • `consentedContactContract`: the standing permission scope under which a sender may contact a subject.

Read / add / edit / delete

CRUD procedures and interface bindings are not declared in this legacy version.

Ownership, roles & access

The neutral owner archetype is the sender as owner of the message record, with recipients owning their own copies and consent subjects owning their consent records. Access is always granted by the respective owner through the catalogue's S1/S2 ownership and access models, with archive access audited via S4.

Existing assembly

Objects, relationships, events and projections

Objects

  • `message`: a unit of communication from a sender; key attributes: messageId, senderRef, sentAt, subject, sensitivity.
  • `messagePart`: a content part of a message; key attributes: partIndex, mediaType, byteSize.
  • `attachmentRef`: a pointer from a message to a carried document; key attributes: documentRef, filename, checksum.
  • `thread`: a conversation grouping messages; key attributes: threadId, topic, startedAt, participantCount.
  • `channel`: a transport medium; key attributes: channelType, providerRef, addressScheme.
  • `address`: a reachable endpoint of an agent on a channel; key attributes: addressValue, schemeRef, ownerRef, verified.
  • `deliveryReceipt`: evidence about a message's transport outcome; key attributes: statusCode, recordedAt, reporterRef.
  • `consentRecord`: permission of a subject to be contacted; key attributes: subjectRef, channelRef, purpose, grantedAt, revokedAt.

Relationships

  • `message` -> belongsTo -> `thread` (N:1): conversation membership.
  • `message` -> sentVia -> `channel` (N:1): the transport actually used.
  • `message` -> addressedTo -> `address` (N:N): recipients as endpoints.
  • `message` -> repliesTo -> `message` (N:1): reply chains within a thread.
  • `messagePart` -> partOf -> `message` (N:1): multipart content structure.
  • `deliveryReceipt` -> confirms -> `message` (N:1): transport evidence per message.
  • `consentRecord` -> authorizes -> `address` (N:1): contact permission for an endpoint and purpose.

Events

  • `messageSent`: the sender released a message into a channel.
  • `messageDelivered`: transport confirmed arrival at the recipient endpoint.
  • `messageRead`: the recipient opened or acknowledged the message.
  • `messageBounced`: transport failed and reported the failure.
  • `messageRecalled`: the sender withdrew a message where the channel allows it.
  • `consentGranted`: a subject permitted contact on a channel for a purpose.
  • `consentRevoked`: a subject withdrew a previously granted permission.

Projections

  • `inboxView`: recipient-facing messages and threads; omits routing internals and other recipients' receipts.
  • `complianceArchiveView`: full messages with delivery evidence and consent state for authorized review; omits live channel credentials.
  • `threadSummaryView`: participants, timeline and subjects of a conversation; omits message bodies.