integrationPackage manifestv2.0.5

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-agent
Source, release and verification context

Source snapshot bcc79fcc · Declared package version 2.0.5. This page combines the checked-in package guide and manifest; commands and runtime behavior were not executed in this review.

Package source ↗ Manifest ↗
servernode
EXPLORE THE PACKAGE

See where this package fits.

Follow a declared connection, inspect an import, then open the source guide when you need the detail.

THIS PACKAGEintegration.communication-os-agentintegrations

Arrows point from a package to its direct dependency. Each count is derived from the captured manifests.

8 declaraciones · se muestran las primeras 6SELECT TO INSPECT

@lssm-tech/integration.communication-os-agent

Governed agent binding for CommunicationOS (plan P1-S2 + P1-S3, AC1.2, AC1.4).

It wires the @lssm-tech/lib.ai-agent runtime so it drafts replies and extracts decisions/risks/actions/summaries/intent for CommunicationOS — using the fail-closed governed command-inbox as the approval seam and a SovereigntyProfile-driven sovereign LLM (Mistral EU by default, Claude as a config-only alternative) — without ever giving the agent outbound send authority.

Why this is an integration package

This package binds three reusable libs (ai-agent, ai-providers, communication-runtime) plus the communication-spec contracts to a concrete runtime target (the governed agent). It introduces no new domain contracts and depends only downward (libs + spec), matching package-architecture.md for the integrations/ layer. It is the glue between the generic agent runtime and the CommunicationOS governance surface; it does not belong in a lib (it composes several libs) nor in a bundle/app (it is reusable across verticals).

Safety invariants (non-negotiable)

  1. Allowlist, not denylist (pre-mortem #3, R3). createCommunicationAgentOperationRegistry() builds the agent's operationRegistry from an explicit allowlist: reply.draft, summary.generate, intent.classify, action.extract, decision.extract, risk.extract. The outbound communication.reply.send operation is structurally absent — it is never registered, so the agent can never resolve it into a tool. A future send-like operation cannot leak in by omission.
  2. Inbox-backed approval seam (architect MUST-FIX 1). CommunicationInboxApprovalStore implements ApprovalStore. Every approval request is projected through createCommunicationCommandInboxItem, producing a fail-closed inbox item (canExecute: false). The agent can only create pending records; it cannot transition them to approved and holds no send tool. The store is wrapped as new ApprovalWorkflow(store) and passed as approvalWorkflow — the inbox object is never passed directly.
  3. Send is a separate port the agent cannot call. Outbound delivery is reachable only by an inbox approval transition driven by a human or an explicitly authorized policy — never by the agent.

Sovereign model binding (P1-S3, AC1.4)

resolveSovereignDefaultModel / createSovereignModelSelector resolve the LanguageModel from the tenant SovereigntyProfile.llmProviderId: Mistral (sovereign EU) by default, Claude (anthropic) as the alternative, switchable by config only. On-prem/self-host hosting routes through a provider-local-model OpenAI-compatible baseUrl.

Thread assist over the Vercel AI Gateway

./thread-assist-gateway exports createGatewayThreadAssistModels(). It returns a read/draft-only thread assist port for any entry of COMMUNICATION_OS_AI_MODEL_CATALOG (@lssm-tech/lib.communication-spec/contracts/ai-model-catalog), built on the shared createVercelGatewayModel adapter.

Every call carries the enforced Gateway policy: EU inference zone, zero data retention, no training, and only the catalog's inference providers. There is no direct-provider key and no automatic fallback model. Ports are cached per model id, so switching models per request does not rebuild clients.

Omit apiKey to let the Gateway SDK use AI_GATEWAY_API_KEY or Vercel OIDC. CommunicationOS API uses this binding for summaries, drafts and inbox triage. The port's triage() (./thread-triage) requests strict structured output (Output.object with the communicationThreadTriageJsonSchema() schema) and validates the label again, so invalid output always rejects. The sovereign binding below remains for the governed agent.

Usage

ts
import { createCommunicationOsAgent } from '@lssm-tech/integration.communication-os-agent';

const { factory, approvalStore, approvalWorkflow } = createCommunicationOsAgent({
  models: {
    sovereignty: { llmProviderId: 'mistral', hostingMode: 'saas' },
    providers: {
      mistral: { apiKey: process.env.MISTRAL_API_KEY },
      anthropic: { apiKey: process.env.ANTHROPIC_API_KEY },
    },
  },
  inbox: { log: { events: [], version: 0 } },
});

Declared capabilities.

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.

Use it to

  • Adopt 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

Requires

  • TypeScript

Choose another boundary when

  • The @lssm-tech/integration.communication-os-agent package constraints do not match the target runtime or platform.

@lssm-tech/integration.communication-os-agent

@lssm-tech/integration.communication-os-agent/agent

@lssm-tech/integration.communication-os-agent/agentic

@lssm-tech/integration.communication-os-agent/agentic/approval-policy

@lssm-tech/integration.communication-os-agent/agentic/mcp-skill-registry

@lssm-tech/integration.communication-os-agent/agentic/memory-binding

@lssm-tech/integration.communication-os-agent/agentic/parallel-subagents

@lssm-tech/integration.communication-os-agent/agentic/scheduler

@lssm-tech/integration.communication-os-agent/agentic/thread-search

@lssm-tech/integration.communication-os-agent/inbox-approval-store

@lssm-tech/integration.communication-os-agent/narrowed-registry

@lssm-tech/integration.communication-os-agent/sovereign-model

@lssm-tech/integration.communication-os-agent/thread-assist

@lssm-tech/integration.communication-os-agent/thread-assist-gateway

@lssm-tech/integration.communication-os-agent/thread-triage

Imports and export paths.

15 entries

These are package-manifest entry points. Named symbols listed above come from the capability catalogue; this is not an exhaustive TypeScript symbol reference.

15 importaciones

@lssm-tech/integration.communication-os-agent/agent

Dependencies and related packages.

Runtime dependencies 8
ai
catalog:ai
Development dependencies 4
@types/bun
catalog:types
typescript
catalog:

Package scripts.

Commands declared by this package. Review its setup requirements before running them; no command here was executed by this review.

buildcontractspec-bun-build build
build:bundlecontractspec-bun-build transpile
build:typescontractspec-bun-build types
devcontractspec-bun-build dev
cleanrimraf dist .turbo
lint:checknode ../../../scripts/biome.cjs check .
lint:fixnode ../../../scripts/biome.cjs check --write --unsafe --only=nursery/useSortedClasses . && node ../../../scripts/biome.cjs check --write .
testbun test
prebuildcontractspec-bun-build prebuild
typechecktsgo --noEmit
Tu vista

Make room for your context.

Shape the presentation around this moment. You can change it whenever you need.

Tu contexto

The different parts of you

Choose a starting point

Una mezcla útil de contexto, imágenes y orientación discreta.

Tune each dimension
Each dimension can change independently. Product permissions and available actions stay unchanged.

Support the way you begin and return

Tune your support

Comodidad de lectura

Elige tu idioma

El idioma de la interfaz solo cambia el texto. Los mercados, precios y flujos de trabajo conservan sus propios ajustes.

Cobertura de traducción

Parte del contenido se muestra en inglés.

Navegación151
Grafo616
Categorías188
Portafolio332
Ejemplos2035
Vista previa de la fuente41

Se añadirán más traducciones a medida que se revise el contenido.

Esta preferencia se guarda en este navegador.

Buscar en el sitio web

Puntos de partida útiles

Sin resultados. Prueba una frase más corta, un nombre de operación u otro ámbito de búsqueda.

UN POCO DE ESPACIO PARA EXPLORAR

Encuentra algo que explorar.

Abre una vista detallada en esta página, prueba otra perspectiva o sigue el detalle a su propia página.

Cómo funcionan las vistas previas y los controles
01

Mirar antes de salir

Pasa el cursor por un enlace o enfócalo con Tab para ver una vista previa. Hacer clic en el enlace original o pulsar Intro siempre abre su destino.

02

Mantener el contexto

Entra en la vista previa para explorar sus secciones. Usa Alt + ↓ desde un enlace enfocado para entrar con el teclado. Escape la cierra.

03

Abrir las posibilidades

Las filas desplegables, las perspectivas y los controles destacados revelan más. Tu vista cambia la comodidad de lectura y el contexto que exploras.

Un botón separado para mirar más de cerca

Muestra pequeños botones de vista previa junto a los enlaces donde haya espacio. Toca el ojo para inspeccionar o el enlace para ir directamente. Esta elección permanece en esta pestaña.

No se recoge historial de navegación. El movimiento reducido sigue tu dispositivo y Tu vista.