# Communication and notifications Compose messaging, delivery, channels and notifications around scoped journals and current send authority. Source snapshot: bcc79fcc27c4d801c2119bef81ddcce7b4e86498 ## Start with the three-layer boundary CommunicationSpec and CommunicationRuntime define the protocol, journal, projections and authority behavior. ModuleCommunicationOS provides reusable product UI. Apps and bundles choose deployment, identity, transport and provider configuration. This makes the communication hub usable both inside another product and as a standalone host. Select the package by the job you are doing, then follow the host-specific binding; importing the visual module alone does not connect a live account or create a durable delivery system. Source: https://github.com/lssm-tech/contractspec/blob/bcc79fcc27c4d801c2119bef81ddcce7b4e86498/packages/domains/communication/runtime/README.md Source: https://github.com/lssm-tech/contractspec/blob/bcc79fcc27c4d801c2119bef81ddcce7b4e86498/packages/domains/communication/module/README.md ## Keep journal truth separate from external delivery The runtime maintains scope-isolated append-only journal behavior and deterministic projections. Typed provider ingestion can retain non-message events as their own journal records instead of fabricating messages. Send checks apply to the current human, agent or system principal. The documented default remains legacy_draft_only; membership_grants mode requires current membership and auditable, revocable grants from the host. Inspect delivery intent, eligibility, queue acceptance and retry evidence as separate transitions so the product can explain whether a message was drafted, accepted or actually delivered. Source: https://github.com/lssm-tech/contractspec/blob/bcc79fcc27c4d801c2119bef81ddcce7b4e86498/packages/domains/communication/runtime/README.md Source: https://github.com/lssm-tech/contractspec/blob/bcc79fcc27c4d801c2119bef81ddcce7b4e86498/packages/domains/communication/module/README.md ## Choose honest UI data modes The communication landing surface accepts an explicit dataMode. Deterministic examples keep preview behavior, while authenticated managed routes use live projections. Live mode derives counts from the supplied workspace projection and removes synthetic-data disclosure. Keep the same distinction in a new host: a preview should teach the interaction, while a live screen must reflect the selected workspace and current authority. Capability-gated actions, pending outbox work and meeting threads should remain inspectable from the interface. Source: https://github.com/lssm-tech/contractspec/blob/bcc79fcc27c4d801c2119bef81ddcce7b4e86498/packages/domains/communication/runtime/README.md Source: https://github.com/lssm-tech/contractspec/blob/bcc79fcc27c4d801c2119bef81ddcce7b4e86498/packages/domains/communication/module/README.md ## Trace one inbound item Follow the provider event through normalization, scope validation and append-only journal storage into the room/space projection. Inspect whether a non-message event retains its correct kind and evidence. Source: https://github.com/lssm-tech/contractspec/blob/bcc79fcc27c4d801c2119bef81ddcce7b4e86498/packages/domains/communication/runtime/README.md Source: https://github.com/lssm-tech/contractspec/blob/bcc79fcc27c4d801c2119bef81ddcce7b4e86498/packages/domains/communication/module/README.md ## Trace one outbound draft Identify the principal, room membership, grant and selected channel. Follow the transition through current send checks, provider queue acceptance and delivery evidence, including an ambiguous or retried outcome. Source: https://github.com/lssm-tech/contractspec/blob/bcc79fcc27c4d801c2119bef81ddcce7b4e86498/packages/domains/communication/runtime/README.md Source: https://github.com/lssm-tech/contractspec/blob/bcc79fcc27c4d801c2119bef81ddcce7b4e86498/packages/domains/communication/module/README.md ## Embed the appropriate surface Choose the reusable module route or slot and supply the host’s actual projection and data mode. Review denied membership, disconnected channel and pending delivery states before treating the resulting screen as a live communication workflow. Source: https://github.com/lssm-tech/contractspec/blob/bcc79fcc27c4d801c2119bef81ddcce7b4e86498/packages/domains/communication/runtime/README.md Source: https://github.com/lssm-tech/contractspec/blob/bcc79fcc27c4d801c2119bef81ddcce7b4e86498/packages/domains/communication/module/README.md ## Packages - [@lssm-tech/integration.communication-channel-core](https://lssm.co/docs/packages/integration.communication-channel-core/): Shared ChannelAdapter port + registry types for CommunicationOS channel integrations (INTERNAL/UNSTABLE until P2-S4 freezes it). - [@lssm-tech/integration.communication-channel-discord](https://lssm.co/docs/packages/integration.communication-channel-discord/): Observe-only multi-guild Discord Gateway integration for CommunicationOS. - [@lssm-tech/integration.communication-channel-email](https://lssm.co/docs/packages/integration.communication-channel-email/): CommunicationOS email channel adapter: inbound normalization (provider-email Gmail parse), outbound send (Postmark/Resend), and documented-retention erasure. - [@lssm-tech/integration.communication-channel-slack](https://lssm.co/docs/packages/integration.communication-channel-slack/): CommunicationOS Slack channel adapter: inbound normalization (Events API + signing-secret verify), outbound send (chat.postMessage), and best-effort erasure (chat.delete). - [@lssm-tech/integration.communication-channel-sms](https://lssm.co/docs/packages/integration.communication-channel-sms/): CommunicationOS SMS channel adapter: inbound normalization (Twilio webhook parse), outbound send (provider-sms/Twilio), and documented-retention erasure. - [@lssm-tech/integration.communication-channel-telegram](https://lssm.co/docs/packages/integration.communication-channel-telegram/): CommunicationOS Telegram channel adapter: inbound normalization (builder-telegram), outbound + erasure via the Telegram Bot API. - [@lssm-tech/integration.communication-os-agent](https://lssm.co/docs/packages/integration.communication-os-agent/): Governed agent binding that drafts CommunicationOS replies via the ai-agent runtime, using the fail-closed command-inbox as the approval seam and a SovereigntyProfile-driven sovereign LLM (Mistral EU default, Claude alternative) — with no outbound send authority. - [@lssm-tech/integration.communication-os-client](https://lssm.co/docs/packages/integration.communication-os-client/): Browser-safe typed REST and realtime client for CommunicationOS. - [@lssm-tech/integration.communication-os-host-auth](https://lssm.co/docs/packages/integration.communication-os-host-auth/): Scoped host-session and access-token exchange for CommunicationOS embeds. - [@lssm-tech/integration.communication-os-persistence](https://lssm.co/docs/packages/integration.communication-os-persistence/): Server-only persistence binding that executes CommunicationOS governed-mutation descriptors against a database, with self-host (PgLite) and managed Postgres support. - [@lssm-tech/integration.communication-os-realtime-ticket](https://lssm.co/docs/packages/integration.communication-os-realtime-ticket/): Short-lived, scoped realtime ticket issuer and verifier for CommunicationOS. - [@lssm-tech/integration.communication-os-runtime](https://lssm.co/docs/packages/integration.communication-os-runtime/): Governed approve→send→event+audit orchestrator that closes the CommunicationOS hexagon: an approved approval (never the agent) is the only path that resolves a ChannelAdapter, and reconciliation does not redispatch a provider-accepted send while audit/event completion remains retryable. - [@lssm-tech/bundle.communication-os](https://lssm.co/docs/packages/bundle.communication-os/): Shell-neutral CommunicationOS application kit for standalone and embedded messaging products. - [@lssm-tech/lib.email](https://lssm.co/docs/packages/lib.email/): Typed email composition, delivery contracts, and provider-neutral primitives. - [@lssm-tech/module.communication-os](https://lssm.co/docs/packages/module.communication-os/): Spec-first communication backbone for turning conversations into structured, governed, agent-callable work - [@lssm-tech/lib.notification](https://lssm.co/docs/packages/lib.notification/): Library-first notification contracts, schema, channels, templates, and i18n for ContractSpec applications - [@lssm-tech/module.notifications](https://lssm.co/docs/packages/module.notifications/): Notification center module for ContractSpec applications - [@lssm-tech/lib.communication-runtime](https://lssm.co/docs/packages/lib.communication-runtime/): Backend-neutral CommunicationOS runtime, governance, lifecycle, state, ingestion, records, and replay helpers. - [@lssm-tech/lib.communication-spec](https://lssm.co/docs/packages/lib.communication-spec/): Canonical communication contracts, operations, events, and validation helpers for ContractSpec. - [@lssm-tech/app.communicationos-api](https://lssm.co/docs/packages/app.communicationos-api/): Inspect the package guide, declared imports and source relationships. - [@lssm-tech/app.communicationos-desktop](https://lssm.co/docs/packages/app.communicationos-desktop/): Tauri 2 desktop shell for CommunicationOS. - [@lssm-tech/app.communicationos-discord-worker](https://lssm.co/docs/packages/app.communicationos-discord-worker/): Inspect the package guide, declared imports and source relationships. - [@lssm-tech/app.communicationos-mcp](https://lssm.co/docs/packages/app.communicationos-mcp/): MCP server exposing CommunicationOS contracts as AI-callable tools via the Model Context Protocol. - [@lssm-tech/app.communicationos-mobile](https://lssm.co/docs/packages/app.communicationos-mobile/): Expo Router iOS and Android shell for CommunicationOS. - [@lssm-tech/app.communicationos-realtime](https://lssm.co/docs/packages/app.communicationos-realtime/): Long-running CommunicationOS realtime gateway for realtime.hcircle.app. - [@lssm-tech/app.communicationos-web](https://lssm.co/docs/packages/app.communicationos-web/): Next.js and PWA shell for the CommunicationOS application kit. - [@lssm-tech/app.communicationos-worker](https://lssm.co/docs/packages/app.communicationos-worker/): Inspect the package guide, declared imports and source relationships.