Module catalogue

This index is generated from the Converged module registry. Every entry links to documentation owned by that module; dependencies are taken from its workspace package manifest, and solution membership comes from modules/solutions.

Access and security

lm-secrets

Provides the service contract for storing, retrieving, and deleting named secret values.

• Direct dependencies: none
• Solutions: none

rp-access

rp-access is a repository in the sequrity domain. Its detailed purpose is maintained with the module source.

• Direct dependencies: none
• Solutions: security

rp-auth

rp-auth is a repository in the sequrity domain. Its detailed purpose is maintained with the module source.

• Direct dependencies: none
• Solutions: security

rp-environment

Stores and retrieves environment configuration associated with platform users.

• Direct dependencies: none
• Solutions: security

rp-identity

rp-identity is a repository in the sequrity domain. Its detailed purpose is maintained with the module source.

• Direct dependencies: none
• Solutions: security

rp-oauth

rp-oauth is a repository in the sequrity domain. Its detailed purpose is maintained with the module source.

• Direct dependencies: none
• Solutions: none

sf-auth

sf-auth is a surface in the sequrity domain. Its detailed purpose is maintained with the module source.

• Direct dependencies: none
• Solutions: security

sf-secrets

Provides the administration interface for creating, viewing, updating, and deleting named secret records.

• Direct dependencies: none
• Solutions: none

sf-team

sf-team is a surface in the sequrity domain. Its detailed purpose is maintained with the module source.

• Direct dependencies: none
• Solutions: production

AI and agents

rp-assistant

rp-assistant is a repository in the ai domain. Its detailed purpose is maintained with the module source.

• Direct dependencies: none
• Solutions: ai

rp-contexts

Provides storage and retrieval of named AI contexts, including their language variants.

• Direct dependencies: none
• Solutions: ai

sf-assistants

sf-assistants is a surface in the ai domain. Its detailed purpose is maintained with the module source.

• Direct dependencies: sf-requests
• Solutions: ai

sf-contexts

Provides the AI workspace for listing, editing, and saving named contexts in multiple languages.

• Direct dependencies: none
• Solutions: ai

Analytics and telemetry

rp-counters

Stores per-tenant external analytics counter configs (tracking ids, head snippets) for SSR injection.

• Direct dependencies: none
• Solutions: analitycs

rp-dashboard

Stores personal dashboard indicator pins: which widgets a user pinned, their order and display metadata.

• Direct dependencies: none
• Solutions: analitycs

rp-logs

rp-logs is a repository in the analytics domain. Its detailed purpose is maintained with the module source.

• Direct dependencies: none
• Solutions: analitycs

rp-telemetry

rp-telemetry is a repository in the analytics domain. Its detailed purpose is maintained with the module source.

• Direct dependencies: none
• Solutions: analitycs

rp-usage

rp-usage is a repository in the analytics domain. Its detailed purpose is maintained with the module source.

• Direct dependencies: none
• Solutions: analitycs

sf-dasboards

sf-dasboards is a surface in the analytics domain. Its detailed purpose is maintained with the module source.

• Direct dependencies: none
• Solutions: analitycs

sf-logs

sf-logs is a surface in the analytics domain. Its detailed purpose is maintained with the module source.

• Direct dependencies: none
• Solutions: analitycs

sf-telemetry

sf-telemetry is a surface in the analytics domain. Its detailed purpose is maintained with the module source.

• Direct dependencies: none
• Solutions: analitycs

sf-usage

sf-usage is a surface in the analytics domain. Its detailed purpose is maintained with the module source.

• Direct dependencies: none
• Solutions: analitycs

Automation and orchestration

lm-kubernetes

Integrates platform automation with Kubernetes resources through a dedicated client and service contract.

• Direct dependencies: none
• Solutions: none

rp-dag

rp-dag is a repository in the automation domain. Its detailed purpose is maintained with the module source.

• Direct dependencies: none
• Solutions: automation, requests

rp-sheduller

rp-sheduller is a repository in the automation domain. Its detailed purpose is maintained with the module source.

• Direct dependencies: none
• Solutions: automation

rp-webhooks

rp-webhooks is a repository in the automation domain. Its detailed purpose is maintained with the module source.

• Direct dependencies: none
• Solutions: automation

sf-automation

sf-automation is a surface in the automation domain. Its detailed purpose is maintained with the module source.

• Direct dependencies: none
• Solutions: automation

Business domain

rp-billing

rp-billing is a repository in the business domain. Its detailed purpose is maintained with the module source.

• Direct dependencies: none
• Solutions: billing

rp-equipment

rp-equipment is a repository in the business domain. Its detailed purpose is maintained with the module source.

• Direct dependencies: none
• Solutions: production

rp-events

Provides creation, storage, and retrieval of business events.

• Direct dependencies: none
• Solutions: production

rp-finance

Provides finance operations for transactions, period summaries, cashflow, receivables, and payables.

• Direct dependencies: none
• Solutions: none

rp-invoices

rp-invoices is a repository in the business domain. Its detailed purpose is maintained with the module source.

• Direct dependencies: none
• Solutions: billing

rp-metering

rp-metering is a repository in the business domain. Its detailed purpose is maintained with the module source.

• Direct dependencies: none
• Solutions: billing

rp-orders

Provides the service contract for creating, updating, listing, and tracking business orders.

• Direct dependencies: none
• Solutions: production

rp-requests

rp-requests is a repository in the business domain. Its detailed purpose is maintained with the module source.

• Direct dependencies: none
• Solutions: requests

rp-reviews

rp-reviews is a repository in the business domain. Its detailed purpose is maintained with the module source.

• Direct dependencies: none
• Solutions: production

rp-sales

rp-sales is a repository in the business domain. Its detailed purpose is maintained with the module source.

• Direct dependencies: none
• Solutions: none

rp-staff

rp-staff is a repository in the business domain. Its detailed purpose is maintained with the module source.

• Direct dependencies: none
• Solutions: production

sf-equipment

sf-equipment is a surface in the business domain. Its detailed purpose is maintained with the module source.

• Direct dependencies: none
• Solutions: production

sf-orders

Provides the sales interface for order and request lists, order details, status filtering, and operational dashboards.

• Direct dependencies: none
• Solutions: production

sf-requests

sf-requests is a surface in the business domain. Its detailed purpose is maintained with the module source.

• Direct dependencies: none
• Solutions: requests

sf-reviews

sf-reviews is a surface in the business domain. Its detailed purpose is maintained with the module source.

• Direct dependencies: none
• Solutions: production

Communications

rp-calls

rp-calls is a repository in the communications domain. Its detailed purpose is maintained with the module source.

• Direct dependencies: none
• Solutions: ai

rp-chats

rp-chats is a repository in the communications domain. Its detailed purpose is maintained with the module source.

• Direct dependencies: none
• Solutions: communications

rp-community

rp-community is a repository in the communications domain. Its detailed purpose is maintained with the module source.

• Direct dependencies: none
• Solutions: communications

rp-notify

rp-notify is a repository in the communications domain. Its detailed purpose is maintained with the module source.

• Direct dependencies: none
• Solutions: security

rp-resonus

Provides communication configuration for managed phone numbers and LLM gate settings.

• Direct dependencies: none
• Solutions: none

rp-support

rp-support is a repository in the communications domain. Its detailed purpose is maintained with the module source.

• Direct dependencies: none
• Solutions: communications

rp-threads

rp-threads is a repository in the communications domain. Its detailed purpose is maintained with the module source.

• Direct dependencies: none
• Solutions: ai, communications

sf-calls

sf-calls is a surface in the communications domain. Its detailed purpose is maintained with the module source.

• Direct dependencies: none
• Solutions: ai

sf-chats

sf-chats is a surface in the communications domain. Its detailed purpose is maintained with the module source.

• Direct dependencies: none
• Solutions: communications

sf-community

sf-community is a surface in the communications domain. Its detailed purpose is maintained with the module source.

• Direct dependencies: none
• Solutions: communications

sf-support

sf-support is a surface in the communications domain. Its detailed purpose is maintained with the module source.

• Direct dependencies: none
• Solutions: communications

sf-threads

sf-threads is a surface in the communications domain. Its detailed purpose is maintained with the module source.

• Direct dependencies: none
• Solutions: ai, communications

Content and documents

rp-classifier

rp-classifier is a repository in the content domain. Its detailed purpose is maintained with the module source.

• Direct dependencies: none
• Solutions: none

rp-galery

rp-galery is a repository in the content domain. Its detailed purpose is maintained with the module source.

• Direct dependencies: none
• Solutions: content

rp-markdown

rp-markdown is a repository in the content domain. Its detailed purpose is maintained with the module source.

• Direct dependencies: none
• Solutions: content

rp-scripts

Provides storage operations for script files, including reading, saving, hashing, and deletion.

• Direct dependencies: none
• Solutions: none

rp-static

Provides the service contract for static content and SSR cache metadata.

• Direct dependencies: none
• Solutions: none

rp-struct

rp-struct is a repository in the content domain. Its detailed purpose is maintained with the module source.

• Direct dependencies: none
• Solutions: content

sf-classifier

Provides the classifier interface for navigating entities, mappings, and tree structures.

• Direct dependencies: none
• Solutions: none

sf-docs

sf-docs is a surface in the content domain. Its detailed purpose is maintained with the module source.

• Direct dependencies: none
• Solutions: none

sf-galery

sf-galery is a surface in the content domain. Its detailed purpose is maintained with the module source.

• Direct dependencies: none
• Solutions: none

sf-landing

sf-landing is a surface in the content domain. Its detailed purpose is maintained with the module source.

• Direct dependencies: none
• Solutions: none

sf-markdown

sf-markdown is a surface in the content domain. Its detailed purpose is maintained with the module source.

• Direct dependencies: none
• Solutions: none

sf-static

Provides the operations interface for inspecting and clearing static SSR cache entries.

• Direct dependencies: none
• Solutions: none

sf-struct

sf-struct is a surface in the content domain. Its detailed purpose is maintained with the module source.

• Direct dependencies: none
• Solutions: none

Files and storage

lm-compressors

lm-compressors is a lambda in the data domain. Its detailed purpose is maintained with the module source.

• Direct dependencies: none
• Solutions: requests

rp-dumps

rp-dumps is a repository in the data domain. Its detailed purpose is maintained with the module source.

• Direct dependencies: none
• Solutions: none

rp-files

rp-files is a repository in the data domain. Its detailed purpose is maintained with the module source.

• Direct dependencies: none
• Solutions: communications, requests

rp-store

rp-store is a repository in the data domain. Its detailed purpose is maintained with the module source.

• Direct dependencies: none
• Solutions: requests

sf-dumps

sf-dumps is a surface in the data domain. Its detailed purpose is maintained with the module source.

• Direct dependencies: none
• Solutions: none

sf-files

sf-files is a surface in the data domain. Its detailed purpose is maintained with the module source.

• Direct dependencies: none
• Solutions: requests

Message delivery providers

lm-lemonsqueezy

lm-lemonsqueezy is a lambda in the providers domain. Its detailed purpose is maintained with the module source.

• Direct dependencies: none
• Solutions: billing

lm-push

lm-push is a lambda in the providers domain. Its detailed purpose is maintained with the module source.

• Direct dependencies: none
• Solutions: none

lm-ses

lm-ses is a lambda in the providers domain. Its detailed purpose is maintained with the module source.

• Direct dependencies: none
• Solutions: security

lm-sms

lm-sms is a lambda in the providers domain. Its detailed purpose is maintained with the module source.

• Direct dependencies: none
• Solutions: none

lm-smtp

lm-smtp is a lambda in the providers domain. Its detailed purpose is maintained with the module source.

• Direct dependencies: none
• Solutions: none

Model conversion

lm-modelconvertor

lm-modelconvertor is a lambda in the convertors domain. Its detailed purpose is maintained with the module source.

• Direct dependencies: none
• Solutions: requests

Workflows

wf-dialogue-summary

Summarizes unprocessed chat and call dialogues with an LLM, then stores titles, descriptions, and noise classification.

• Direct dependencies: none
• Solutions: none

wf-equipment-incident

wf-equipment-incident is a workflow in the platform domain. Its detailed purpose is maintained with the module source.

• Direct dependencies: none
• Solutions: production

wf-file-analyze

Analyzes one stored non-archive file, producing model previews and CNC or 3D-print estimates when supported.

• Direct dependencies: none
• Solutions: requests

wf-file-unpack

Expands one uploaded archive into a collection of stored files for subsequent analysis.

• Direct dependencies: none
• Solutions: requests

wf-files-analyze

wf-files-analyze is a workflow in the platform domain. Its detailed purpose is maintained with the module source.

• Direct dependencies: none
• Solutions: requests

wf-files-process

Processes uploaded files in batches: it expands archives, identifies model files, and creates a manufacturing request from them.

• Direct dependencies: none
• Solutions: requests

wf-order-review-followup

wf-order-review-followup is a workflow in the platform domain. Its detailed purpose is maintained with the module source.

• Direct dependencies: none
• Solutions: production

wf-order-review-request

wf-order-review-request is a workflow in the platform domain. Its detailed purpose is maintained with the module source.

• Direct dependencies: none
• Solutions: production

wf-payment-settle

wf-payment-settle is a workflow in the platform domain. Its detailed purpose is maintained with the module source.

• Direct dependencies: none
• Solutions: billing

wf-request-analyze

wf-request-analyze is a workflow in the platform domain. Its detailed purpose is maintained with the module source.

• Direct dependencies: none
• Solutions: requests

wf-request-to-order

wf-request-to-order is a workflow in the platform domain. Its detailed purpose is maintained with the module source.

• Direct dependencies: none
• Solutions: production

wf-sales-import

wf-sales-import is a workflow in the platform domain. Its detailed purpose is maintained with the module source.

• Direct dependencies: none
• Solutions: none

wf-sales-review-outreach

wf-sales-review-outreach is a workflow in the platform domain. Its detailed purpose is maintained with the module source.

• Direct dependencies: none
• Solutions: none

wf-team-invite

wf-team-invite is a workflow in the platform domain. Its detailed purpose is maintained with the module source.

• Direct dependencies: none
• Solutions: production

Solution dependencies

• ai: security
• analitycs: security
• automation: security
• billing: security
• communications: security
• content: security
• production: security, analitycs, requests
• requests: no solution dependencies
• security: no solution dependencies