Skip to content
ContractSpec
Start here

reference

SupportOS notification evidence

Preference-aware, body-free notification intent and CommunicationOS delivery evidence.

field.key.label
docs.customer-support.notifications
field.version.label
field.type.label
field.title.label
SupportOS notification evidence
field.tags.label
supportos,notifications,communication-os,privacy
field.owners.label
field.stability.label
public

SupportOS owns notification preferences, intent, escalation policy, and durable delivery evidence. CommunicationOS owns channel identity, rendered message content, provider delivery, and attachments. Notification contracts contain only opaque party, template, source-event, policy, and delivery references; message bodies, contact destinations, provider payloads, and credentials are never copied into SupportOS.

Mutations derive tenant and workspace authority from authenticated server context, require idempotency and revision fencing, and persist immutable audit evidence. Collection reads use keyset pagination and a stable watermark. Delivery failure never silently downgrades a required escalation. Durable workers resolve only a body-free dispatch projection by opaque notification reference, pass a stable effect-idempotency key to the channel authority, and record exact delivery evidence before completing the fenced job.