Area guide · 28 packages · Inspect a generated content draft
Content, growth and creator operations
Move from source-grounded drafts and optimization reports to reviewed publishing, measurement and commercial lifecycle evidence.
What are you trying to do?
- Which package drafts content and which can publish it?
- What invalidates an editorial approval?
- How do creator earnings and growth rewards preserve evidence?
Why start with these packages
Suggested entry point
@lssm-tech/lib.content-genUse blog, email, social and marketing draft generators plus optimization reports.
Suggested entry point
@lssm-tech/lib.growth-runtimeInspect referral/reward lifecycle and optional marketing/editorial execution over supplied ports.
Suggested entry point
@lssm-tech/lib.creator-operations-runtimeUse creator campaign, agreement, submission and settlement lifecycle composition.
Suggested entry point
@lssm-tech/lib.content-analysis-runtimeInspect content analysis behavior separately from generation and publication.
Practical steps
Step 01
Trace a single content item
Choose one generator or analysis surface and inspect its validated output. Locate the publication operation and provider separately, then identify the content digest and evidence the reviewer sees.
Step 02
Inspect an editorial change
Change the proposed content in the owning fixture and follow how approval/scheduling state is invalidated. Review the path for uncertain publication and an explicit withdrawal of content already confirmed live.
Step 03
Follow one commercial result
Trace an attribution or submission observation through the deterministic lifecycle into a reward or settlement proposal. Keep source evidence, unit conversion, authorization and provider confirmation visible to the host and operator.
Start with a draft or analysis goal
ContentGen provides separate generators for formats such as blog, email and social posts. Its documented social flow parses model JSON and discards invalid channels, unsafe links or malformed content before a caller can approve publication. The geo and geographic surfaces address generative-engine optimization and local-market adaptation respectively; they return reports. Select the format and analysis task first, then inspect the model/provider input and the reviewable output rather than assuming a generated text is ready for an external account.
Bind publishing to the exact reviewed content
GrowthRuntime’s marketing entry includes editorial services and source-aware measurement with host-supplied authorization, durable compare-and-swap storage, provider, clock and IDs. Provider effects are unavailable by default. Edits invalidate previous approval and scheduling, reviews bind to a content digest, and removing a published item requires a separate withdrawal flow. Concurrent reservations and ambiguous outcomes make reconciliation a first-class path. A product should therefore distinguish draft, approved, scheduled, dispatched and confirmed publication states.
Preserve commercial lifecycle facts
Growth attribution selects a prioritized winner and applies consent, identity, approval and maturity boundaries before reward/payout transitions. CreatorOperations adds immutable accepted agreements, submission review, cumulative accrual and settlement orchestration. Its source represents money with explicit currency and scale and retains reservations when provider outcomes are unknown. Corrections should preserve the evidence and accepted terms they supersede. Keep a campaign estimate, earned balance, payout proposal and confirmed settlement separate when building reporting or an agent tool.
Follow a practical path.
Trace a single content item
Choose one generator or analysis surface and inspect its validated output. Locate the publication operation and provider separately, then identify the content digest and evidence the reviewer sees.
Inspect an editorial change
Change the proposed content in the owning fixture and follow how approval/scheduling state is invalidated. Review the path for uncertain publication and an explicit withdrawal of content already confirmed live.
Follow one commercial result
Trace an attribution or submission observation through the deterministic lifecycle into a reward or settlement proposal. Keep source evidence, unit conversion, authorization and provider confirmation visible to the host and operator.
Packages in this area (28)
28 of 28 shown
- Open manual →
Headless reusable creator platform foundation with governed optional surfaces.
- Open manual →
Shared governed marketing operation server composition.
- Open manual →
Reusable transactional creator operations.
- Open manual →
Authorized editorial deployment evidence retrieval.
- Open manual →
LSSM-authoritative GrowthOS projection adapter for the official Dub TypeScript SDK.
- Open manual →
GrowthOS payout orchestration over existing provider-neutral Stripe and PayPal capabilities.
- Open manual →
Tenant-scoped transactional persistence for GrowthOS referral and affiliate state.
- Open manual →
Provider-neutral social analytics tracking runtime with Postgres persistence and public metadata fallback.
- Open manual →
Durable advertising recipe execution and scoped HTTP mechanics.
- Open manual →
Product analytics and growth metrics
- Open manual →
Provider-neutral content analysis orchestration runtime.
Inspect content analysis behavior separately from generation and publication.
- Open manual →
Evidence-first provider-neutral content analysis and content-generation contracts.
- Open manual →
AI-powered content generation for blog, email, and social
Use blog, email, social and marketing draft generators plus optimization reports.
- Open manual →
Deterministic evidence-first creative intelligence runtime.
- Open manual →
Evidence-first creative trend, hypothesis, outcome, and benchmark contracts.
- Open manual →
Reusable transactional creator operations.
Use creator campaign, agreement, submission and settlement lifecycle composition.
- Open manual →
Provider-neutral creator-operations contract definitions: campaign, submission, wallet, training, quiz and accrual operation, schema, port and feature specs extracted unchanged from ContractSpec compatibility.
- Open manual →
Pure deterministic runtime for GrowthOS referral, affiliate, reward, and payout lifecycles.
Inspect referral/reward lifecycle and optional marketing/editorial execution over supplied ports.
- Open manual →
Provider-neutral growth and marketing operation contracts for autonomous-company campaign, lifecycle, and publishing handoffs.
- Open manual →
AI-powered image generation for hero, social, thumbnail, OG, and illustration
- Open manual →
Provider-neutral contracts and orchestration primitives for video generation.
- Open manual →
Thin provider-agnostic facade for unified content generation workflows with deterministic demo stubs.
- Open manual →
Reusable creator operations module.
- Open manual →
Versioned editorial review and publication workflows.
- Open manual →
Reusable participant and admin UI for GrowthOS referral and affiliate programs.
- Open manual →
Offline marketing evolution pipeline: signal collection, improvement proposals, human-gated PR output, and experiment-variant port.
- Open manual →
Provider-agnostic social analytics dashboard surfaces.
- Open manual →
Governed multi-provider social drafting, scheduling, publication, and reconciliation Hub.
Curated but no longer in the workspace: app.marketing-operations, app.video-studio
What connects to this area
Core contracts
Drafts, observations and publication actions need distinct contracts.
Governance and approvals
A publishing decision must bind the content actually reviewed.
Integrations and providers
Social, publishing, advertising and payment adapters own provider-specific effects.
Billing and finance
Commercial rewards and settlements need exact money and evidence.