Source snapshot bcc79fcc · Declared package version 2.1.4. This page combines the checked-in package guide and manifest; commands and runtime behavior were not executed in this review.
Thin, provider-agnostic facade for unified content generation workflows across text/content, image, video, TTS, STT, and conversation.
Boundary
This package intentionally ships deterministic demo stubs only. Real provider SDKs and integration packages must be injected by callers through the exported provider ports.
Quick start
ts
import { createContentGenerationFacade } from '@lssm-tech/module.content-generation';
const contentGeneration = createContentGenerationFacade();
const result = await contentGeneration.runDemoWorkflow();
The default facade does not read credentials or call external services.
The optional rights registrar composes ContentRightsService and ContentWithdrawalWorker behind five canonical operations. It checks authenticated scope before service access and retains separate operation approvals for grant recording and provider withdrawal. This production port composition is independent of the default demo generation facade.
Durable media status
The additive content-generation.media.status v1 query exposes persisted generation state, revision, artifact references and expected output count through
POST /marketing/media/status and MCP media_generation_status. It never polls providers or dispatches generation. Installations supply an authorized reader; the marketing host mounts it only when configured. Tenant, workspace and generation ownership are checked before returning progress. Provider URLs, connection keys and payment reservation references stay private. Existing draft generation operations retain their behavior.
Declared capabilities.
Module Content Generation
Thin provider-agnostic facade for unified content generation workflows with deterministic demo stubs.
Use it to
Adopt thin provider-agnostic facade for unified content generation workflows with deterministic demo stubs
Requires
TypeScript
Choose another boundary when
The @lssm-tech/module.content-generation package constraints do not match the target runtime or platform.
These are package-manifest entry points. Named symbols listed above come from the capability catalogue; this is not an exhaustive TypeScript symbol reference.