Communication specs
Canonical communication contracts, operations, events, and validation helpers for ContractSpec.
@lssm-tech/lib.communication-specpackages/domains/communication/spec
Core relationshipDeclares the ContractSpec core package directly.
Inspected package consumers9 packages declare this specification in the reviewed inventory.
CONNECTED ACROSS LSSM
From this specification to the systems around it.
Select an entry to explore its neighbours. Move between ownership, specifications, areas, products, data and infrastructure without leaving this page.
10 entries · 41 recorded relationships
Arrow keys navigate entries. Enter selects. Alt + arrows rearranges. F fits the view; Shift + F fits the selection. + and − zoom. Shift + F10 opens actions.
Accessible entry list (10)
- Shared foundations
- Products & experiences
- Shared foundations
- Inspected sources
- Infrastructure services
- Infrastructure services
- Infrastructure services
- Specialized specifications
- Specialized specifications
- Specialized specifications
Architecture lineage
- ContractSpec ↗Specialized contracts within ContractSpecContractSpec → Communication specs
The architecture specializes ContractSpec for this contract surface. Exact direct, indirect or absent package dependencies are recorded separately.
Dependencies between specifications
- Agent protocol specs ↗Declared package dependencyAgent protocol specs → Communication specs
The consumer manifest declares this dependency in dependencies. Presence in a manifest is distinct from a tested runtime import or live deployment.
- CompanyOS specs ↗Declared package dependencyCompanyOS specs → Communication specs
The consumer manifest declares this dependency in dependencies. Presence in a manifest is distinct from a tested runtime import or live deployment.
- ContractSpec ↗Declared package dependencyContractSpec → Communication specs
The consumer manifest declares this dependency in dependencies. Presence in a manifest is distinct from a tested runtime import or live deployment.
Connected systems and service roles
- CommunicationOS ↗Source-mapped contract scopeCommunication specs → CommunicationOS
Pinned package purpose and reviewed source map associate this contract surface with the target. This relationship is not a manifest dependency or proof of product runtime adoption.
- Communication & realtime delivery ↗Source-mapped contract scopeCommunication specs → Communication & realtime delivery
Pinned package purpose and reviewed source map associate this contract surface with the target. This relationship is not a manifest dependency or proof of product runtime adoption.
- Private & workplace messaging ↗Source-mapped contract scopeCommunication specs → Private & workplace messaging
Pinned package purpose and reviewed source map associate this contract surface with the target. This relationship is not a manifest dependency or proof of product runtime adoption.
- Notifications & channel preferences ↗Source-mapped contract scopeCommunication specs → Notifications & channel preferences
Pinned package purpose and reviewed source map associate this contract surface with the target. This relationship is not a manifest dependency or proof of product runtime adoption.
- Patio ↗Source-mapped contract scopeCommunication specs → Patio
Pinned package purpose and reviewed source map associate this contract surface with the target. This relationship is not a manifest dependency or proof of product runtime adoption.
Source and package context
- ContractSpec repository ↗Pinned specification package sourceCommunication specs → ContractSpec repository
Exact package manifest and README evidence at the retained source commit.
Groups connected through this specification
- Missions & real-world experience ↗Specialized contracts in this group’s contextMissions & real-world experience → Communication specs
Derived through explicit member products, selected capabilities or their recorded source paths. The source edge chain preserves implemented, proposed and editorial scopes; the group link adds navigation, not runtime integration.
- Company & owner assistance ↗Specialized contracts in this group’s contextCompany & owner assistance → Communication specs
Derived through explicit member products, selected capabilities or their recorded source paths. The source edge chain preserves implemented, proposed and editorial scopes; the group link adds navigation, not runtime integration.
- Expert, trade & craft workflows ↗Specialized contracts in this group’s contextExpert, trade & craft workflows → Communication specs
Derived through explicit member products, selected capabilities or their recorded source paths. The source edge chain preserves implemented, proposed and editorial scopes; the group link adds navigation, not runtime integration.
- Missions & external collaborators ↗Specialized contracts in this group’s contextMissions & external collaborators → Communication specs
Derived through explicit member products, selected capabilities or their recorded source paths. The source edge chain preserves implemented, proposed and editorial scopes; the group link adds navigation, not runtime integration.
- Founder intelligence ↗Specialized contracts in this group’s contextFounder intelligence → Communication specs
Derived through explicit member products, selected capabilities or their recorded source paths. The source edge chain preserves implemented, proposed and editorial scopes; the group link adds navigation, not runtime integration.
- Company decisions & learning ↗Specialized contracts in this group’s contextCompany decisions & learning → Communication specs
Derived through explicit member products, selected capabilities or their recorded source paths. The source edge chain preserves implemented, proposed and editorial scopes; the group link adds navigation, not runtime integration.
- Experience & personal learning ↗Specialized contracts in this group’s contextExperience & personal learning → Communication specs
Derived through explicit member products, selected capabilities or their recorded source paths. The source edge chain preserves implemented, proposed and editorial scopes; the group link adds navigation, not runtime integration.
- Missions & contribution ↗Specialized contracts in this group’s contextMissions & contribution → Communication specs
Derived through explicit member products, selected capabilities or their recorded source paths. The source edge chain preserves implemented, proposed and editorial scopes; the group link adds navigation, not runtime integration.
- Community life ↗Specialized contracts in this group’s contextCommunity life → Communication specs
Derived through explicit member products, selected capabilities or their recorded source paths. The source edge chain preserves implemented, proposed and editorial scopes; the group link adds navigation, not runtime integration.
- Conversations & correspondence ↗Specialized contracts in this group’s contextConversations & correspondence → Communication specs
Derived through explicit member products, selected capabilities or their recorded source paths. The source edge chain preserves implemented, proposed and editorial scopes; the group link adds navigation, not runtime integration.
- Goals, planning & personal agency ↗Specialized contracts in this group’s contextGoals, planning & personal agency → Communication specs
Derived through explicit member products, selected capabilities or their recorded source paths. The source edge chain preserves implemented, proposed and editorial scopes; the group link adds navigation, not runtime integration.
- Health context & wellbeing ↗Specialized contracts in this group’s contextHealth context & wellbeing → Communication specs
Derived through explicit member products, selected capabilities or their recorded source paths. The source edge chain preserves implemented, proposed and editorial scopes; the group link adds navigation, not runtime integration.
- Communication channels & infrastructure ↗Specialized contracts in this group’s contextCommunication channels & infrastructure → Communication specs
Derived through explicit member products, selected capabilities or their recorded source paths. The source edge chain preserves implemented, proposed and editorial scopes; the group link adds navigation, not runtime integration.
Packages that declare this dependency.
These package manifests explicitly name this specification. Their runtime and deployment status remain separate.
- @lssm-tech/bundle.communication-os ↗
packages/bundles/communication-osProvides a shell-neutral CommunicationOS app kit, messaging and meeting-intelligence projections, navigation, route presentations, Forms surfaces, and support-platform composition.
- @lssm-tech/bundle.managed-companyos ↗
packages/bundles/managed-companyosComposes the reusable CompanyOS workspace, OPA planning/booking, CommunicationOS, integration and agent/workflow hubs, governance/evidence, Special Ops, founder canary and executive cockpit, with product-scoped design and UI surfaces.
- @lssm-tech/module.communication-os ↗
packages/domains/communication/moduleSpec-first communication backbone for turning conversations into structured, governed, agent-callable work
- @lssm-tech/lib.notification ↗
packages/domains/communication/notificationLibrary-first notification contracts, schema, channels, templates, and i18n for ContractSpec applications
- @lssm-tech/module.notifications ↗
packages/domains/communication/notificationsNotification center module for ContractSpec applications
- @lssm-tech/lib.communication-runtime ↗
packages/domains/communication/runtimeBackend-neutral CommunicationOS runtime, governance, lifecycle, state, ingestion, records, and replay helpers.
- @lssm-tech/module.community-intelligence ↗
packages/domains/community/moduleGoverned, provider-neutral community analytics, coaching views, and Kaizen digests.
- @lssm-tech/module.customer-support ↗
packages/domains/customer-support/moduleReusable SupportOS inbox, AI canvas, messenger, host, and agent surfaces.
- @lssm-tech/lib.contracts-spec ↗
packages/platform/delivery/contracts-spec-compatCompatibility facade forwarding original ContractSpec contracts and registries to canonical owners.
Inspect the specification.
Canonical events, threads, identity-merge and governed-work declarations; no provider transport or effect execution. CommunicationOS owns conversation contracts and lifecycle. Transport credentials, current effect grants and production delivery belong to qualified hosts.
Open the package in the complete inventory ↗