bundlePackage manifestv3.0.5

bundle.communication-os

Shell-neutral CommunicationOS application kit for standalone and embedded messaging products.

@lssm-tech/bundle.communication-os
Source, release and verification context

Source snapshot bcc79fcc · Declared package version 3.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 PACKAGEbundle.communication-osbundles

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

9 déclarations · les 6 premières affichéesSELECT TO INSPECT

@lssm-tech/bundle.communication-os

Reusable CommunicationOS application kit for Next.js, Expo, Tauri, and in-app feature-hub hosts.

createHcircleMeetingIntelligence provides the hCircle meeting projection: optional connection-focused preparation, consent-led sharing, no productivity scoring, no clinical inference, and public links disabled by default.

The bundle composes the canonical v2 messaging contracts, deterministic journal projections, revocable principal authority, normalized channel adapters, semantic navigation, and contextual embed slots. It is framework-neutral and provider-neutral.

communicationOsCanonicalRoutes and resolveCommunicationOsRoute derive from the 23-route hub catalog. Standalone, embedded, Expo, and Tauri hosts use this registry to validate list/detail paths instead of treating unknown URLs as an inbox or room fallback. Navigation derives every non-detail canonical destination from the same catalog and then adds explicitly owned product routes. resolveCommunicationOsRoutePresentation gives each canonical destination the same purposeful title, description, and empty-state contract on web, Expo, and Tauri. Thread and message deep links retain their opaque conversation reference instead of silently falling back to the previously active room. Hosts that only need the Forms experience should import the focused @lssm-tech/bundle.communication-os/forms-ui subpath so meeting/provider runtime code does not enter the same browser chunk.

Detail identifiers remain opaque, but the shared resolver rejects traversal segments, encoded path separators, control characters, malformed encoding, repeated interior separators, and decoded identifiers longer than 256 characters before any host selects or fetches a conversation.

Contextual slots use the same canonical communication-os.* identifiers as the route catalog. This keeps standalone web, CompanyOS embedding, Expo, and Tauri from showing an action that the canonical route authority would deny.

Legacy CommunicationOS adopters remain draft-only. Standalone and embedded hosts opt into membership_grants only after supplying membership, grant, policy, journal, and channel ports.

Forms

The bundle exports the shared Forms management and public respondent surfaces. CommunicationOS mounts management at /communications/forms, public forms at /f/{opaqueToken}, and the versioned API at /api/forms/v1. The same governed operations are registered for web, Expo mobile, Tauri desktop, and MCP; creator scope still comes from the authenticated CommunicationOS grant.

Declared capabilities.

Bundle Communication Os

Shell-neutral CommunicationOS application kit for standalone and embedded messaging products.

Use it to

  • Adopt shell-neutral communicationos application kit for standalone and embedded messaging products

Requires

  • TypeScript

Choose another boundary when

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

@lssm-tech/bundle.communication-os

@lssm-tech/bundle.communication-os/app-kit

@lssm-tech/bundle.communication-os/compatibility

@lssm-tech/bundle.communication-os/deployment

@lssm-tech/bundle.communication-os/forms-platform

@lssm-tech/bundle.communication-os/forms-ui

@lssm-tech/bundle.communication-os/meeting-intelligence

@lssm-tech/bundle.communication-os/navigation

@lssm-tech/bundle.communication-os/route-registry

@lssm-tech/bundle.communication-os/slots

@lssm-tech/bundle.communication-os/support-platform

Imports and export paths.

12 entries

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

12 imports

Dependencies and related packages.

Runtime dependencies 9
Development dependencies 3
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
prebuildcontractspec-bun-build prebuild
typechecktsgo --noEmit
testbun test
lint:checknode ../../../scripts/biome.cjs check .
lint:fixnode ../../../scripts/biome.cjs check --write .
Votre vue

Make room for your context.

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

Votre contexte

The different parts of you

Choose a starting point

Un mélange utile de contexte, de visuels et de guidage discret.

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

Confort de lecture

Choisir votre langue

La langue de l’interface change uniquement le texte. Les marchés, les prix et les parcours conservent leurs propres paramètres.

Couverture des traductions

Une partie du contenu est affichée en anglais.

Navigation151
Graphe616
Catégories378
Portfolio833
Exemples2 035
Aperçu de la source1 542

D’autres traductions seront ajoutées à mesure que le contenu sera relu.

Cette préférence est enregistrée dans ce navigateur.

Rechercher sur le site

Des points de départ utiles

Aucun résultat. Essayez une expression plus courte, un nom d’opération ou un autre périmètre de recherche.

UN PEU DE PLACE POUR EXPLORER

Trouvez quelque chose à explorer.

Ouvrez un aperçu détaillé sur cette page, essayez une autre perspective ou suivez le détail vers sa propre page.

Fonctionnement des aperçus et des commandes
01

Regarder avant de partir

Survolez un lien ou sélectionnez-le avec Tab pour voir un aperçu. Cliquer sur le lien d’origine ou appuyer sur Entrée ouvre toujours sa destination.

02

Rester dans le contexte

Entrez dans l’aperçu pour explorer ses sections. Depuis un lien sélectionné, utilisez Alt + ↓ pour y entrer au clavier. Échap le ferme.

03

Ouvrir les possibilités

Les lignes dépliables, les choix de perspective et les commandes mises en évidence révèlent davantage. Votre vue adapte le confort de lecture et le contexte exploré.

Un bouton séparé pour voir de plus près

Affichez de petits boutons d’aperçu à côté des liens quand l’espace le permet. Touchez l’œil pour examiner ou le lien pour y aller directement. Ce choix reste dans cet onglet.

Aucun historique de navigation n’est collecté. La réduction des animations suit votre appareil et Votre vue.