Compositions & bundles / Developer distribution and agent-accessible hosting↗ @lssm-tech/bundle.alpic
packages/bundles/alpicComposes the Alpic MCP-server and ChatGPT-app hosting surface by forwarding the module-owned hosting helpers.
Source & scope
This thin bundle owns no business logic; the README identifies module.alpic and the alpic-mcp host as the implementation/consumer boundary. Hosting helpers are not evidence of a live Alpic-branded product or a new infrastructure company.
Compositions & bundles / Communication, meetings, forms and support composition↗ @lssm-tech/bundle.communication-os
packages/bundles/communication-osProvides a shell-neutral CommunicationOS app kit, messaging and meeting-intelligence projections, navigation, route presentations, Forms surfaces, and support-platform composition.
Source & scope
The documented hCircle seam uses connection-focused preparation and consent-led sharing; it is not general productivity or clinical inference. Membership, persistence, provider effects and current authority remain host-owned. Forms and support exports do not establish standalone deployments.
Compositions & bundles / Creator collaboration and commercial operations↗ @lssm-tech/bundle.creator-platform
packages/bundles/creator-platformSupplies reusable creator intelligence, learning, gamification, publishing and optional UI, plus governed creator campaign, agreement, submission, accrual, wallet and settlement composition.
Source & scope
The Taketide navigation mapping follows the user's product assignment, not proven application adoption of this bundle. The README explicitly leaves complete Hirly parity, production payouts and provider qualification open; hosts own transactional stores, current authority, credentials and product rules. Consequential actions remain human-controlled.
Compositions & bundles / Founder decision and capacity workspace↗ @lssm-tech/bundle.founder-suite
packages/bundles/founder-suiteComposes founder and executive intelligence, talent, domain doors, archetype packs, localized presentation, Forms and owner-scoped live-room/meeting surfaces for the founder workspace.
Source & scope
The source's historical Pactena founder identity is mapped to Tendframe using the user's explicit rename. CompanyOS is an external peer, not an authority shortcut. Providers, persistence and CommunicationOS client bindings remain injected; fixtures and degraded dependencies are not presented as live services.
Compositions & bundles / Career application operations↗ @lssm-tech/bundle.job-application
packages/bundles/job-applicationExposes reusable candidate and operator controllers for application lifecycle, profile provenance, form review, inbox/account challenges, takeover, submission, reconciliation, cancellation and deletion.
Source & scope
The Tafio-family mappings are use-case navigation, not proof that each brand imports this bundle. Browser projections are reference-safe and redacted; server-issued action descriptors and exact-resource confirmation govern effects. Credentials, answers, inbox addresses, codes and cookies remain outside the projection.
Compositions & bundles / Developer documentation, catalogs and reusable presentation↗ @lssm-tech/bundle.library
packages/bundles/libraryComposes ContractSpec documentation, examples/templates, integration marketplace, presentation features, credential-setup previews, and transport-neutral MCP surfaces into a shared product library.
Source & scope
The large export map contains many documentation and compatibility leaves, not hundreds of distinct services. MCP transport, hosts and real credentials remain separate; generated docs are a source-generation artifact. Declaration/packed-consumer qualification mentioned in the README is not rerun by this inventory.
Compositions & bundles / Company lifecycle and maturity advisory↗ @lssm-tech/bundle.lifecycle-managed
packages/bundles/lifecycle-managedComposes lifecycle assessment, an AI lifecycle advisor, domain events, analytics and thin REST adapters over the lifecycle core.
Source & scope
The documented CLI/example and service composition are source evidence. They do not establish a live advisory company or a deployed autonomous improvement loop. The opportunity-discovery mapping is adjacent navigation, not equivalent runtime behavior.
Compositions & bundles / Company operations and governed workspace composition↗ @lssm-tech/bundle.managed-companyos
packages/bundles/managed-companyosComposes the reusable CompanyOS workspace, OPA planning/booking, CommunicationOS, integration and agent/workflow hubs, governance/evidence, Special Ops, founder canary and executive cockpit, with product-scoped design and UI surfaces.
Source & scope
Fellowhand/Briefhand are inferred product-family navigation, not verified deployed adopters. The bundle is provider-neutral and app hosts own sessions, live databases, credential resolution, effects and production authority. Its product-health ledger separates SupportOS; fixture readiness and source-local UI evidence are not production acceptance. Autonomous-work-order authoring files are fixture-generation inputs, not a second runtime. Candidate UI templates are staged assets, not automatic shared-design-system adoption.
Compositions & bundles / Public brand and marketing presentation↗ @lssm-tech/bundle.marketing
packages/bundles/marketingProvides public ContractSpec and CompanyOS marketing content, stories, templates, campaign compositions, example previews and email helpers over shared design-system primitives.
Source & scope
Apps retain routing, metadata, canonical URLs and shell ownership. Template previews are deterministic and provider-free. Campaign styling, localized draft content and marketing claims do not establish product execution, pricing approval, SLA coverage or provider connections.
Compositions & bundles / GTM, editorial, advertising and creator operations↗ @lssm-tech/bundle.marketing-operations
packages/bundles/marketing-operationsComposes governed goal-to-plan marketing, advertising, conversions and observations, social scheduling, editorial Git publication, creator operations/training, content-rights withdrawal and evidence-bound optimization through REST/MCP and reusable UI.
Source & scope
The source describes optional composition and evolving operation counts; this review does not treat a count as deployment readiness. Hosts supply authenticated scopes, durable stores, exact-input human review, pricing, provider qualification, scheduler wiring and production issuers. Simulated SQL/provider/browser rehearsals do not qualify live advertising spend, publication or payouts. No Tellshift or Taketide runtime adoption is inferred from shared purpose.
Compositions & bundles / OSINT research and acquisition operations↗ @lssm-tech/bundle.osint
packages/bundles/osintProvides the OSINT command center, scoped provider research routing, governed-data transport and redacted operator controllers/UI for acquisition and evidence workflows.
Source & scope
Provider routing retains capability/provenance boundaries and host-owned deployment/credential allowlists. Persisted evidence precedes corroboration. Returned operation/auth/idempotency descriptors govern actions; the UI cannot invent authority. Listing supported providers is not proof of active subscriptions or credentials.
Compositions & bundles / Personal agency, finance, care and life administration↗ @lssm-tech/bundle.personal-os
packages/bundles/personal-osComposes the personal/non-work portfolio: missions and goals, productivity, household care and delegation, non-clinical health, learning, personal finance, life administration and rights, consent-aware personalization, and minimized community/founder projections.
Source & scope
The server-only composition uses subject-bound encrypted state and exact current authority; public projections are minimized. Finance is subject-owned and distinct from business FinanceOS. Historical Pactena projection consumers map to user-renamed Tendframe. The README and archived qualification records explicitly separate source/local proofs from host deployment, real providers, KMS, devices, accessibility acceptance, purge/restore and canary qualification; no current live-readiness percentage is independently asserted here.
Compositions & bundles / Product discovery and intent authoring↗ @lssm-tech/bundle.product-intent
packages/bundles/product-intentComposes product-intent reasoning, evidence retrieval and an AI runner around provider-neutral core services for product definition and delivery preparation.
Source & scope
The README explicitly says this bundle is not yet wired into an app. ContractSpec Studio is a relevant PO/PM navigation destination, not a claimed current implementation consumer. Model/provider selection and production host integration remain outside this evidence.
Compositions & bundles / Governed improvement operator surfaces↗ @lssm-tech/bundle.self-improving-system
packages/bundles/self-improving-systemProvides reusable headless operator controllers and view models for signals, candidates, evaluation, gates/review, shadow/canary, promotion, rollback, kill and replay in a governed improvement lifecycle.
Source & scope
The bundle only presents durable server decisions through injected data ports. It never authorizes or executes effects; idempotency, revisions, fingerprints, traces and evidence bind commands. This is not an unconditional autonomous self-healing deployment.
Compositions & bundles / Developer workspace and governed delivery tooling↗ @lssm-tech/bundle.workspace
packages/bundles/workspaceOwns ContractSpec's reusable CLI/editor service composition for workspace discovery, validation, code generation, graph/drift inspection, setup and release workflows, plus guarded maintenance adapters and Connect host hooks.
Source & scope
The Node/Bun root has filesystem/process requirements and is not a browser surface. Optional AI/providers remain injected. Local Builder draft storage is single-writer and not production authority; GitHub maintenance automation uses qualified host authorization and branch protections. Connect/operator grants described in source do not authorize this review to alter grants, permissions, repositories or deployments.
Product domains / Mobile app readiness↗ @lssm-tech/module.app-submission-readiness
packages/domains/app-submission-readiness/moduleReviewReady module: runtime-driven app-submission readiness report, rejection assistant, and admin rule surfaces built from real audit output.
Source & scope
Runtime-driven reports, rejection assistance and admin rules are implemented as product surfaces; no static demo result is treated as an audit. ReviewReady evaluates supplied store evidence; source does not establish a live store connection, submission or approval guarantee.
Product domains / Mobile app readiness↗ @lssm-tech/lib.app-submission-readiness-runtime
packages/domains/app-submission-readiness/runtimePure, deterministic runtime audit engine for mobile app submission readiness (ReviewReady). No network calls; integrations feed it snapshots to audit.
Source & scope
Pure deterministic audit runtime performs no network access and consumes caller-provided App Store / Google Play metadata snapshots. ReviewReady evaluates supplied store evidence; source does not establish a live store connection, submission or approval guarantee.
Product domains / Billing & metering↗ @lssm-tech/lib.billing-france
packages/domains/billing/billing-franceFrance-specific BillingOS readiness contracts and deterministic e-invoicing/e-reporting checks.
Source & scope
France e-invoice readiness metadata and checks do not claim PA accreditation, legal/tax advice or a production submission. BillingOS owns quote-to-cash and governed economic handoffs; credentials, provider execution and production finance qualification remain separate.
Product domains / Billing & metering↗ @lssm-tech/lib.crypto-payments-spec
packages/domains/billing/crypto-payments-specProvider-neutral crypto wallet governance and HTTP-native agent payment protocol contracts.
Source & scope
Contract-only wallet governance and agent-payment handoffs; no custody, signing, broadcasting, settlement or provider SDK execution. BillingOS owns quote-to-cash and governed economic handoffs; credentials, provider execution and production finance qualification remain separate.
Product domains / Billing & metering↗ @lssm-tech/lib.metering
packages/domains/billing/meteringUsage metering and billing core module for ContractSpec applications
Source & scope
Shared usage-metering core is mapped to metering services and economic evidence; no inspected production collection or billing binding is inferred. BillingOS owns quote-to-cash and governed economic handoffs; credentials, provider execution and production finance qualification remain separate.
Product domains / Billing & metering↗ @lssm-tech/module.billing-os
packages/domains/billing/moduleCompanyOS composition module for governed BillingOS action plans, authority checks, autonomy classification, and operator inbox routing.
Source & scope
Composition produces governed authority/operator-inbox handoffs. No provider credentials or authorized billing execution are supplied by default. BillingOS owns quote-to-cash and governed economic handoffs; credentials, provider execution and production finance qualification remain separate.
Product domains / Billing & metering↗ @lssm-tech/lib.billing-runtime
packages/domains/billing/runtimePure backend-neutral BillingOS runtime helpers for deterministic quote-to-cash lifecycle projections.
Source & scope
Pure backend-neutral quote-to-cash projections; no I/O, provider writes or production invoice submission. BillingOS owns quote-to-cash and governed economic handoffs; credentials, provider execution and production finance qualification remain separate.
Product domains / Billing & metering↗ @lssm-tech/lib.billing-spec
packages/domains/billing/specCountry-neutral BillingOS quote-to-cash contracts, invariants, and agent action governance types.
Source & scope
Country-neutral contract definitions and invariants; execution is outside the specification layer. BillingOS owns quote-to-cash and governed economic handoffs; credentials, provider execution and production finance qualification remain separate.
Product domains / Product authoring & delivery↗ @lssm-tech/module.lssm-os-control-plane
packages/domains/builder/control-planeTenant-safe application services and scheduling for the LSSM OS control plane.
Source & scope
Tenant-safe scheduling and worker orchestration use injected ports and exact fenced receipts. The control plane does not own effect authority or credentials. Builder plans, authors and prepares evidence through explicit boundaries. Connect authority, durable stores, provider execution and deployment qualification remain distinct.
Product domains / Product authoring & delivery↗ @lssm-tech/lib.evolution
packages/domains/builder/evolutionAI-powered contract evolution engine
Source & scope
Contract evolution and governed-learning helpers are source capabilities; not evidence of automatic deployment, unrestricted self-modification or live optimization. Builder plans, authors and prepares evidence through explicit boundaries. Connect authority, durable stores, provider execution and deployment qualification remain distinct.
Product domains / Product authoring & delivery↗ @lssm-tech/module.mobile-review
packages/domains/builder/mobile-reviewReusable mobile-first Builder review surfaces.
Source & scope
Reusable mobile-first review UI composes existing Builder components; a distinct launched mobile product is not established. Builder plans, authors and prepares evidence through explicit boundaries. Connect authority, durable stores, provider execution and deployment qualification remain distinct.
Product domains / Product authoring & delivery↗ @lssm-tech/module.builder-workbench
packages/domains/builder/moduleReusable Builder workbench UI module.
Source & scope
React workbench and CompanyContext/RoleMorph panels render validated evidence. Live provider activation, durable state, visual qualification and production authority remain separate. Builder plans, authors and prepares evidence through explicit boundaries. Connect authority, durable stores, provider execution and deployment qualification remain distinct.
Product domains / Product authoring & delivery↗ @lssm-tech/module.product-intent-core
packages/domains/builder/product-intent-coreCore product intent orchestration and adapters
Source & scope
Product-intent orchestration and adapters are a reusable module consumed by Studio; not a distinct public product or deployment. Builder plans, authors and prepares evidence through explicit boundaries. Connect authority, durable stores, provider execution and deployment qualification remain distinct.
Product domains / Product authoring & delivery↗ @lssm-tech/lib.product-intent-utils
packages/domains/builder/product-intent-utilsPrompt builders and validators for product-intent workflows.
Source & scope
Prompt builders and validators are library helpers; prompts do not grant execution authority or prove model execution. Builder plans, authors and prepares evidence through explicit boundaries. Connect authority, durable stores, provider execution and deployment qualification remain distinct.
Product domains / Product authoring & delivery↗ @lssm-tech/lib.builder-runtime
packages/domains/builder/runtimeBackend-neutral Builder runtime, ingestion, fusion, readiness, and replay services.
Source & scope
Provider-neutral ingestion, planning, replay and patch workflow enforce scope. Hosts must supply trusted workspace authority, isolation, provider ports and durable stores. Builder plans, authors and prepares evidence through explicit boundaries. Connect authority, durable stores, provider execution and deployment qualification remain distinct.
Product domains / Product authoring & delivery↗ @lssm-tech/lib.builder-spec
packages/domains/builder/specBuilder control-plane contracts, capabilities, and validation for ContractSpec.
Source & scope
Typed control-plane, plan, readiness and preview contracts reference Connect decisions without owning execution or authorization. Builder plans, authors and prepares evidence through explicit boundaries. Connect authority, durable stores, provider execution and deployment qualification remain distinct.
Product domains / Communication & notifications↗ @lssm-tech/lib.email
packages/domains/communication/emailTyped email composition, delivery contracts, and provider-neutral primitives.
Source & scope
Typed email composition and delivery contracts complement MailPatio; package presence does not establish live email or phone delivery. CommunicationOS owns conversation contracts and lifecycle. Transport credentials, current effect grants and production delivery belong to qualified hosts.
Product domains / Communication & notifications↗ @lssm-tech/module.communication-os
packages/domains/communication/moduleSpec-first communication backbone for turning conversations into structured, governed, agent-callable work
Source & scope
Canonical communication protocol, inbox and product composition. Voice-derived proposals cannot create customer promises or bypass PM/action approval. CommunicationOS owns conversation contracts and lifecycle. Transport credentials, current effect grants and production delivery belong to qualified hosts.
Product domains / Communication & notifications↗ @lssm-tech/lib.notification
packages/domains/communication/notificationLibrary-first notification contracts, schema, channels, templates, and i18n for ContractSpec applications
Source & scope
Notifications model templates, entities, channels and preparation; the package does not own external-effect authority. CommunicationOS owns conversation contracts and lifecycle. Transport credentials, current effect grants and production delivery belong to qualified hosts.
Product domains / Communication & notifications↗ @lssm-tech/module.notifications
packages/domains/communication/notificationsNotification center module for ContractSpec applications
Source & scope
Compatibility shim, not a second notification implementation, independent service or additional company. CommunicationOS owns conversation contracts and lifecycle. Transport credentials, current effect grants and production delivery belong to qualified hosts.
Product domains / Communication & notifications↗ @lssm-tech/lib.communication-runtime
packages/domains/communication/runtimeBackend-neutral CommunicationOS runtime, governance, lifecycle, state, ingestion, records, and replay helpers.
Source & scope
Backend-neutral lifecycle, journal, ingestion and replay require current membership and grants. Legacy behavior defaults to draft-only. CommunicationOS owns conversation contracts and lifecycle. Transport credentials, current effect grants and production delivery belong to qualified hosts.
Product domains / Communication & notifications↗ @lssm-tech/lib.communication-spec
packages/domains/communication/specCanonical communication contracts, operations, events, and validation helpers for ContractSpec.
Source & scope
Canonical events, threads, identity-merge and governed-work declarations; no provider transport or effect execution. CommunicationOS owns conversation contracts and lifecycle. Transport credentials, current effect grants and production delivery belong to qualified hosts.
Product domains / Community intelligence↗ @lssm-tech/module.community-intelligence
packages/domains/community/moduleGoverned, provider-neutral community analytics, coaching views, and Kaizen digests.
Source & scope
Provider ingestion, storage and moderation stay behind host ports; externally analyzed data is minimized, and observation/coaching is not automated HR authority. Community intelligence is observation and coaching support; it does not authorize staffing or HR decisions. Hosts own providers, moderation and persistence.
Product domains / Company operations & intelligence↗ @lssm-tech/module.company-metrics
packages/domains/company/company-metricsGoverned CompanyOS metric definitions, deterministic aggregation, collection, alerts, digests, and publications.
Source & scope
Metric definitions, aggregation, alerts and digests remain deterministic; AI may propose or explain but cannot change observed values or collection authority. CompanyOS owns company intent, authority-aware projections and reviewed handoffs. Private founder context and external execution retain separate owners.
Product domains / Company operations & intelligence↗ @lssm-tech/module.executive-intelligence
packages/domains/company/executive-intelligenceShared leadership briefs, risks, commitments, and decision packets.
Source & scope
Leadership briefs, risks, commitments and decision packets omit founder-private values from tenant-shared projections. CompanyOS owns company intent, authority-aware projections and reviewed handoffs. Private founder context and external execution retain separate owners.
Product domains / Company operations & intelligence↗ @lssm-tech/module.companyos
packages/domains/company/moduleCompanyOS execution composition module with typed adapter ports over CompanyOS spec/runtime contracts.
Source & scope
Application composition uses typed adapter ports, not provider/network/queue defaults; each effect needs current exact authority. CompanyOS owns company intent, authority-aware projections and reviewed handoffs. Private founder context and external execution retain separate owners.
Product domains / Company operations & intelligence↗ @lssm-tech/lib.companyos-runtime
packages/domains/company/runtimePure CompanyOS V0 runtime helpers for authority, autonomy, inbox routing, and operating review projections.
Source & scope
Provider-free deterministic projections include graph integrity, bitemporal replay and authorized search. The runtime does not execute actions. CompanyOS owns company intent, authority-aware projections and reviewed handoffs. Private founder context and external execution retain separate owners.
Product domains / Company operations & intelligence↗ @lssm-tech/lib.companyos-spec
packages/domains/company/specContract-first CompanyOS V0/V1 specifications for bounded company operations.
Source & scope
Company contracts own intent, approval and replay evidence. VoiceOps is a governed-action scenario, not live STT/TTS, customer sends, CRM writes or production execution. CompanyOS owns company intent, authority-aware projections and reviewed handoffs. Private founder context and external execution retain separate owners.
Product domains / Content, media & editorial↗ @lssm-tech/lib.content-gen
packages/domains/content/content-genAI-powered content generation for blog, email, and social
Source & scope
Text/blog/email/social generation helpers and schemas do not themselves execute publication or grant campaign authority. Content roles compose provider-neutral models and orchestration; publishing, providers, storage and exact authority must be supplied by hosts.
Product domains / Content, media & editorial↗ @lssm-tech/module.editorial
packages/domains/content/editorialVersioned editorial review and publication workflows.
Source & scope
Immutable revisions, review, scheduling and CAS publication use host publishers. Unknown effects are reconciled without blind redispatch; recovery is not publication approval. Content roles compose provider-neutral models and orchestration; publishing, providers, storage and exact authority must be supplied by hosts.
Product domains / Content, media & editorial↗ @lssm-tech/lib.image-gen
packages/domains/content/image-genAI-powered image generation for hero, social, thumbnail, OG, and illustration
Source & scope
Image-generation library for hero/social/thumbnail/OG/illustration outputs; provider and production usage are not established by the package manifest. Content roles compose provider-neutral models and orchestration; publishing, providers, storage and exact authority must be supplied by hosts.
Product domains / Content, media & editorial↗ @lssm-tech/module.content-generation
packages/domains/content/moduleThin provider-agnostic facade for unified content generation workflows with deterministic demo stubs.
Source & scope
Default unified generation facade deliberately uses deterministic demo stubs. Production model/provider ports are injected separately. Content roles compose provider-neutral models and orchestration; publishing, providers, storage and exact authority must be supplied by hosts.
Product domains / Content, media & editorial↗ @lssm-tech/lib.content-analysis-runtime
packages/domains/content/runtimeProvider-neutral content analysis orchestration runtime.
Source & scope
Bounded evidence-first analysis with injected authorization, decomposition, models, persistence and events; it never grants product authority. Content roles compose provider-neutral models and orchestration; publishing, providers, storage and exact authority must be supplied by hosts.
Product domains / Content, media & editorial↗ @lssm-tech/lib.content-analysis-spec
packages/domains/content/specEvidence-first provider-neutral content analysis and content-generation contracts.
Source & scope
Provider-neutral analysis contracts bind exact evidence and model/policy versions. Analysis cannot approve content, creators, ranking, publication or money. Content roles compose provider-neutral models and orchestration; publishing, providers, storage and exact authority must be supplied by hosts.
Product domains / Content, media & editorial↗ @lssm-tech/lib.video-gen
packages/domains/content/video-genProvider-neutral contracts and orchestration primitives for video generation.
Source & scope
Reusable Remotion video compositions and adapter interfaces. Translation/narration is experimental pending native review, not approved production creative. Content roles compose provider-neutral models and orchestration; publishing, providers, storage and exact authority must be supplied by hosts.
Product domains / Creator operations↗ @lssm-tech/module.creator-operations
packages/domains/creator/moduleReusable creator operations module.
Source & scope
Registers provider-neutral campaign/economic operations; current authority, transaction store and settlement ports are injected. No default payout grant or rail. Creator campaigns, agreements and economics require trusted current authority and durable transactional ports. No default live payout rail is established.
Product domains / Creator operations↗ @lssm-tech/lib.creator-operations-runtime
packages/domains/creator/runtimeReusable transactional creator operations.
Source & scope
Immutable accepted terms, cumulative CPM accrual and settlement orchestration use canonical evidence. Quiz verification cannot trust browser scores or replace durable training state. Creator campaigns, agreements and economics require trusted current authority and durable transactional ports. No default live payout rail is established.
Product domains / Creator operations↗ @lssm-tech/lib.creator-operations-spec
packages/domains/creator/specProvider-neutral creator-operations contract definitions: campaign, submission, wallet, training, quiz and accrual operation, schema, port and feature specs extracted unchanged from ContractSpec compatibility.
Source & scope
Canonical campaign, wallet, accrual and training declarations; compatibility exports retain identity and do not create a second implementation. Creator campaigns, agreements and economics require trusted current authority and durable transactional ports. No default live payout rail is established.
Product domains / Customer support & resolution↗ @lssm-tech/lib.customer-support-conformance
packages/domains/customer-support/customer-support-conformancePortable behavioral conformance harness for managed and self-hosted SupportOS authorities.
Source & scope
Deterministic authority conformance verifies isolation, replay and fencing. A fixture receipt is not production, migration, accessibility, recovery or canary qualification. SupportOS is a reusable source product; providers, persistence, credentials and production/security qualification remain host-owned.
Product domains / Customer support & resolution↗ @lssm-tech/module.customer-support
packages/domains/customer-support/moduleReusable SupportOS inbox, AI canvas, messenger, host, and agent surfaces.
Source & scope
Operator inbox, DecisionGraph canvas, messenger, embedding and agent surfaces are source-backed; production adapters, access/security review and canaries remain explicit gates. SupportOS is a reusable source product; providers, persistence, credentials and production/security qualification remain host-owned.
Product domains / Customer support & resolution↗ @lssm-tech/lib.customer-support-runtime
packages/domains/customer-support/runtimeProvider-neutral SupportOS case authority, SLA, autonomy, and ecosystem bridge runtime.
Source & scope
Provider-neutral case authority and resolution workflow use injected persistence; reference in-memory stores are not a production deployment. SupportOS is a reusable source product; providers, persistence, credentials and production/security qualification remain host-owned.
Product domains / Customer support & resolution↗ @lssm-tech/lib.customer-support-spec
packages/domains/customer-support/specProvider-neutral SupportOS customer-support contract definitions: case, authority, operation, event, schema and feature specs extracted unchanged from ContractSpec compatibility.
Source & scope
Canonical case, authority, operation, event and resolution contracts; sending a reply does not itself resolve a case. SupportOS is a reusable source product; providers, persistence, credentials and production/security qualification remain host-owned.
Product domains / Customer support & resolution↗ @lssm-tech/lib.support-bot
packages/domains/customer-support/support-botAI support bot framework with RAG and ticket management
Source & scope
SupportOsCopilot returns drafts, evidence and typed operation references under feature, consent, redaction and budget gates. Older raw-ticket helpers are deprecated compatibility. SupportOS is a reusable source product; providers, persistence, credentials and production/security qualification remain host-owned.
Product domains / Customer support & resolution↗ @lssm-tech/lib.supportos-worker-runtime
packages/domains/customer-support/supportos-worker-runtimeProvider-free fenced job execution and handler composition for the SupportOS worker.
Source & scope
Provider-free fenced durable-worker loop and retry/outcome orchestration; provider clients, PostgreSQL, credentials and deployment configuration remain outside. SupportOS is a reusable source product; providers, persistence, credentials and production/security qualification remain host-owned.
Product domains / Business finance↗ @lssm-tech/module.finance-os
packages/domains/finance/moduleGoverned FinanceOS application services producing Connect-authorized effect handoffs.
Source & scope
Application services return plans, review requirements and authorized Connect handoffs; never direct banking, payroll, tax or accounting-system calls. FinanceOS covers internal business finance beyond BillingOS. Packages prepare contracts, projections and authorized handoffs rather than banking, tax, payroll or ledger effects.
Product domains / Business finance↗ @lssm-tech/lib.finance-os-runtime
packages/domains/finance/runtimeDeterministic provider-neutral FinanceOS planning, budget, posting, and evidence runtime.
Source & scope
Deterministic money, posting, budget and consolidation validation. Consequential operations produce digest-bound handoffs and require Connect plus host adapters. FinanceOS covers internal business finance beyond BillingOS. Packages prepare contracts, projections and authorized handoffs rather than banking, tax, payroll or ledger effects.
Product domains / Business finance↗ @lssm-tech/lib.finance-ops-spec
packages/domains/finance/specProvider-neutral internal finance operations contracts beyond BillingOS quote-to-cash.
Source & scope
Reviewable procurement, spend, payroll/tax handoff and runway contracts, distinct from BillingOS quote-to-cash; no financial advice or provider action. FinanceOS covers internal business finance beyond BillingOS. Packages prepare contracts, projections and authorized handoffs rather than banking, tax, payroll or ledger effects.
Product domains / Founder intelligence↗ @lssm-tech/module.founder-intelligence
packages/domains/founder-intelligence/moduleReusable founder cockpit application services and safe presentation models.
Source & scope
Reusable cockpit assembly, observations, assessment and clarity-loop services require host persistence and AuthOS/CompanyOS authority. Tendframe is the user-confirmed founder product. Source still uses historical names; founder-private evidence and selective sharing stay separate from company authority.
Product domains / Founder intelligence↗ @lssm-tech/lib.founder-intelligence-runtime
packages/domains/founder-intelligence/runtimePure deterministic projections for founder intelligence, selective sharing, and clarity reviews.
Source & scope
Pure private projections, grants and weekly review; a bounded founder canary retains citations and checkpoint scope rather than asserting full-history coverage. Tendframe is the user-confirmed founder product. Source still uses historical names; founder-private evidence and selective sharing stay separate from company authority.
Product domains / Founder intelligence↗ @lssm-tech/lib.founder-intelligence-spec
packages/domains/founder-intelligence/specProvider-neutral contracts for founder-private intelligence, executive projections, and operating archetypes.
Source & scope
Execution-free founder-private contracts, fourteen domain doors and advisory recommendations. One-mailbox canary contracts never send mail or claim three-mailbox/full-history coverage. Tendframe is the user-confirmed founder product. Source still uses historical names; founder-private evidence and selective sharing stay separate from company authority.
Product domains / Learning & progression↗ @lssm-tech/module.gamification
packages/domains/gamification/moduleReusable gamification projections and theme-aware React surfaces over the canonical gamification runtime.
Source & scope
Theme-aware cadence/streak/XP/quest/badge/leaderboard UI and projections delegate to canonical spec/runtime; no payout ledger or app-owned campaign policy. Gamification is reusable progression logic. Product policy, participant authority, durable state and delivery remain outside the package; creator payouts are excluded.
Product domains / Learning & progression↗ @lssm-tech/lib.gamification-runtime
packages/domains/gamification/runtimeDeterministic storage-neutral gamification evaluation and replay runtime.
Source & scope
Deterministic immutable evaluation and replay with explicit timestamps, seeds and host-authorized participants. No I/O or implicit authority. Gamification is reusable progression logic. Product policy, participant authority, durable state and delivery remain outside the package; creator payouts are excluded.
Product domains / Learning & progression↗ @lssm-tech/lib.gamification-spec
packages/domains/gamification/specPortable cross-vertical gamification campaign contracts and validation.
Source & scope
Portable campaign, cadence, reward-inventory and progression declarations without persistence, network, user discovery or notification delivery. Gamification is reusable progression logic. Product policy, participant authority, durable state and delivery remain outside the package; creator payouts are excluded.
Product domains / Marketing, growth & distribution↗ @lssm-tech/lib.advertising-runtime
packages/domains/growth/advertising-runtimeDurable advertising recipe execution and scoped HTTP mechanics.
Source & scope
Durable scoped provider recipes require authorization, secrets and transport. Unknown creates are never retried blindly; API acceptance does not prove delivery or conversion. GrowthOS scope includes marketing and referral/affiliate lifecycles. Provider actions and spend require current authority, durable state and qualified integrations.
Product domains / Marketing, growth & distribution↗ @lssm-tech/lib.analytics
packages/domains/growth/analyticsProduct analytics and growth metrics
Source & scope
Vendor-neutral analytics write boundaries and growth metrics; no particular production collector, tenant feed or dashboard outcome is established. GrowthOS scope includes marketing and referral/affiliate lifecycles. Provider actions and spend require current authority, durable state and qualified integrations.
Product domains / Marketing, growth & distribution↗ @lssm-tech/lib.creative-intelligence-runtime
packages/domains/growth/creative-intelligence-runtimeDeterministic evidence-first creative intelligence runtime.
Source & scope
Pure explainable scoring and privacy-thresholded benchmarks; hypotheses retain evidence/limitations and do not grant campaign authority. GrowthOS scope includes marketing and referral/affiliate lifecycles. Provider actions and spend require current authority, durable state and qualified integrations.
Product domains / Marketing, growth & distribution↗ @lssm-tech/lib.creative-intelligence-spec
packages/domains/growth/creative-intelligence-specEvidence-first creative trend, hypothesis, outcome, and benchmark contracts.
Source & scope
Creative-signal/trend/hypothesis/outcome contracts reuse OSINT evidence. Source acquisition and campaign state have other owners. GrowthOS scope includes marketing and referral/affiliate lifecycles. Provider actions and spend require current authority, durable state and qualified integrations.
Product domains / Marketing, growth & distribution↗ @lssm-tech/module.marketing-evolution
packages/domains/growth/marketing-evolutionOffline marketing evolution pipeline: signal collection, improvement proposals, human-gated PR output, and experiment-variant port.
Source & scope
README absent in the pinned snapshot. Manifest declares an offline proposal pipeline with human-gated PR and experiment ports; no stronger implementation or runtime claim is made. GrowthOS scope includes marketing and referral/affiliate lifecycles. Provider actions and spend require current authority, durable state and qualified integrations.
Product domains / Marketing, growth & distribution↗ @lssm-tech/module.growth-os
packages/domains/growth/moduleReusable participant and admin UI for GrowthOS referral and affiliate programs.
Source & scope
Controlled localized referral/affiliate surfaces consume authoritative GrowthOS projections; UI does not calculate attribution/rewards/balances or grant inference authority. GrowthOS scope includes marketing and referral/affiliate lifecycles. Provider actions and spend require current authority, durable state and qualified integrations.
Product domains / Marketing, growth & distribution↗ @lssm-tech/lib.growth-runtime
packages/domains/growth/runtimePure deterministic runtime for GrowthOS referral, affiliate, reward, and payout lifecycles.
Source & scope
Pure referral/affiliate/reward/payout logic and editorial lifecycle. Sample marketing bookings are synthetic; deployment verification does not fetch or publish. GrowthOS scope includes marketing and referral/affiliate lifecycles. Provider actions and spend require current authority, durable state and qualified integrations.
Product domains / Marketing, growth & distribution↗ @lssm-tech/module.social-analytics
packages/domains/growth/social-analyticsProvider-agnostic social analytics dashboard surfaces.
Source & scope
Provider-agnostic dashboard ports show source gaps and explicit observed/correlated/experiment-supported labels; credentials, jobs and storage remain external. GrowthOS scope includes marketing and referral/affiliate lifecycles. Provider actions and spend require current authority, durable state and qualified integrations.
Product domains / Marketing, growth & distribution↗ @lssm-tech/module.social-media
packages/domains/growth/social-mediaGoverned multi-provider social drafting, scheduling, publication, and reconciliation Hub.
Source & scope
Social publishing defaults to draft-only and requires scoped durable/provider/grant ports. Ambiguous outcomes are not blindly retried; reconciliation is read-only. GrowthOS scope includes marketing and referral/affiliate lifecycles. Provider actions and spend require current authority, durable state and qualified integrations.
Product domains / Marketing, growth & distribution↗ @lssm-tech/lib.growth-spec
packages/domains/growth/specProvider-neutral growth and marketing operation contracts for autonomous-company campaign, lifecycle, and publishing handoffs.
Source & scope
Reviewable acquisition/lifecycle and publishing contracts do not send messages, publish CMS pages, buy ads, write CRM or own personalization runtime decisions. GrowthOS scope includes marketing and referral/affiliate lifecycles. Provider actions and spend require current authority, durable state and qualified integrations.
Product domains / Identity & authority↗ @lssm-tech/lib.identity-rbac
packages/domains/identity/identity-rbacIdentity, Organizations, and RBAC module for ContractSpec applications
Source & scope
Shared identity, organization and RBAC contracts; catalog membership is not an agent-fleet deployment grant. AuthOS names the reusable identity source. Contract/UI/runtime scope does not establish production authentication, issuer activation or permissive effect authority.
Product domains / Identity & authority↗ @lssm-tech/module.auth-os
packages/domains/identity/moduleReusable AuthOS module with fake adapters and UI flows for identity, authentication, organizations, and Connect with LSSM.
Source & scope
Reusable AuthOS atomic UI and host adapter interfaces. Auth providers, account execution and production qualification remain host-owned. AuthOS names the reusable identity source. Contract/UI/runtime scope does not establish production authentication, issuer activation or permissive effect authority.
Product domains / Identity & authority↗ @lssm-tech/lib.authos-runtime
packages/domains/identity/runtimePure deterministic AuthOS runtime projections and security gates over AuthOS contracts.
Source & scope
Pure security/identity projections and subject propagation; it does not authenticate users, call Better Auth, access databases or execute providers. AuthOS names the reusable identity source. Contract/UI/runtime scope does not establish production authentication, issuer activation or permissive effect authority.
Product domains / Identity & authority↗ @lssm-tech/lib.authos-spec
packages/domains/identity/specContract-first AuthOS specifications for identity, authentication, federation, and security-gated account surfaces.
Source & scope
Contract-first federation/security surfaces. High-impact commands need approval evidence and host execution; LSSM-as-IdP activation requires independent security review. AuthOS names the reusable identity source. Contract/UI/runtime scope does not establish production authentication, issuer activation or permissive effect authority.
Product domains / Candidate-authorized applications↗ @lssm-tech/module.job-application
packages/domains/job-application/moduleHeadless candidate-authorized job application orchestration.
Source & scope
Compatibility facade to canonical library headless orchestration; new integrations should use runtime/headless, not treat the facade as another service. Candidate-private applications are isolated from the shared OSINT corpus. Browser sessions, credentials, storage and effects remain injected and candidate-authorized.
Product domains / Candidate-authorized applications↗ @lssm-tech/lib.job-application-runtime
packages/domains/job-application/runtimeProvider-free candidate-authorized application lifecycle and exact-effect runtime.
Source & scope
Pure lifecycle, field proposal, effect fencing and replay. Default is confirmation per application; unsupported interactive challenges have no automatic bypass. Candidate-private applications are isolated from the shared OSINT corpus. Browser sessions, credentials, storage and effects remain injected and candidate-authorized.
Product domains / Job intelligence & acquisition↗ @lssm-tech/lib.job-source-runtime
packages/domains/job-source/runtimeProvider-free job-source discovery, acquisition, normalization, closure, and replay runtime.
Source & scope
Separates discovery, acquisition, parsing, normalization, revalidation and closure. Opaque credentials are resolved transiently by host adapters, never by connector code. Job-source acquisition keeps public intelligence separate from candidate-private application actions. Network access and connector-specific behavior use injected ports.
Product domains / Learning & progression↗ @lssm-tech/module.learning-journey
packages/domains/learning/moduleComprehensive learning journey engine - onboarding, LMS, flashcards, gamification, and AI personalization
Source & scope
Adaptive onboarding/LMS/flashcards/practice runtime and canonical gamification delegation; coaching remains a proposal rather than authority. Learning journeys and coaching proposals are reusable application capabilities; progression does not grant product authority.
Product domains / Opportunity research & evaluation↗ @lssm-tech/lib.opportunity-runtime
packages/domains/opportunity/runtimePure deterministic scoring, gate, simulation, and portfolio projections for autonomous-company opportunities.
Source & scope
Pure scoring, gates, simulation and portfolio ranking over supplied evidence. Does not fetch research, call LLMs/providers, persist or create CompanyOS/Builder workflows. Opportunity contracts and deterministic evaluation operate on caller-provided evidence. They do not research live markets, run providers or approve autonomous-company execution.
Product domains / Opportunity research & evaluation↗ @lssm-tech/lib.opportunity-spec
packages/domains/opportunity/specProvider-neutral opportunity scoring and selection contracts for autonomous-company candidates.
Source & scope
Contract-only opportunity scorecards, evidence and handoff packets. High scores and editorial CAC priors are not measured customer metrics or implementation approval. Opportunity contracts and deterministic evaluation operate on caller-provided evidence. They do not research live markets, run providers or approve autonomous-company execution.
Product domains / Scheduling, booking & meeting work↗ @lssm-tech/module.organization-planning
packages/domains/organization-planning/moduleOrganization planning composition module with typed adapter ports for cross-module integration.
Source & scope
Typed cross-module obligations and exact release acceptance; no side effects by default, and no default receipt-signature verifier. OPA means Organization Planning & Agenda. Planning, booking and meeting work require fresh authority and host adapters; declared features are not production acceptance.
Product domains / Scheduling, booking & meeting work↗ @lssm-tech/opa-booking-react
packages/domains/organization-planning/opa-booking-reactHosted and headless React integration for OPA booking links.
Source & scope
Hosted/headless booking clients validate exact origins and expose public-safe availability; private calendar IDs and credentials stay outside public widgets. OPA means Organization Planning & Agenda. Planning, booking and meeting work require fresh authority and host adapters; declared features are not production acceptance.
Product domains / Scheduling, booking & meeting work↗ @lssm-tech/lib.organization-planning-react
packages/domains/organization-planning/organization-planning-reactHeadless React clients for governed Organization Planning workspaces.
Source & scope
Authenticated headless workspaces keep credentials host-owned. Reviewing meeting outcomes alone does not send messages, publish links or create Work tasks. OPA means Organization Planning & Agenda. Planning, booking and meeting work require fresh authority and host adapters; declared features are not production acceptance.
Product domains / Scheduling, booking & meeting work↗ @lssm-tech/lib.organization-planning-runtime
packages/domains/organization-planning/runtimeOrganization Planning & Agenda (OPA) execution runtime: wires the organization-planning module's adapter ports to real adapters while preserving fail-closed approval gates. Provider SDKs stay in integrations/.
Source & scope
Planning/meeting/capture orchestration uses consent, encrypted staging and injected stores/providers. Saving delegated-autopilot settings does not start background execution. OPA means Organization Planning & Agenda. Planning, booking and meeting work require fresh authority and host adapters; declared features are not production acceptance.
Product domains / Scheduling, booking & meeting work↗ @lssm-tech/lib.organization-planning-spec
packages/domains/organization-planning/specProvider-neutral organization, planning, agenda, booking, and auto-scheduling contracts for autonomous-company operations.
Source & scope
Agenda, booking, capture and follow-up declarations define separate acceptance requirements. Declaring an operation does not install its handler or qualify execution. OPA means Organization Planning & Agenda. Planning, booking and meeting work require fresh authority and host adapters; declared features are not production acceptance.
Product domains / Open-source intelligence↗ @lssm-tech/module.osint
packages/domains/osint/moduleHeadless orchestration for governed company, job, and people OSINT
Source & scope
Executable capability matrix distinguishes implementation, deterministic tests and live receipts; unsupported provider methods remain explicit, never simulated as live. OSINT source explicitly separates implementation, deterministic qualification and live qualification. Provider access, durable stores and production receipts remain distinct.
Product domains / Open-source intelligence↗ @lssm-tech/lib.osint-runtime
packages/domains/osint/runtimeProvider-neutral OSINT lifecycle, ingestion, governance, and knowledge runtime.
Source & scope
Provider-neutral discovery, qualification, ingestion, revalidation and evidence replay. Concrete providers/storage/queues are injected; derived knowledge never authorizes actions. OSINT source explicitly separates implementation, deterministic qualification and live qualification. Provider access, durable stores and production receipts remain distinct.
Product domains / Open-source intelligence↗ @lssm-tech/lib.osint-spec
packages/domains/osint/specEvidence-first, provider-neutral OSINT v0 schemas and contracts.
Source & scope
Evidence-first company/job/person contracts require immutable provenance. V0 does not apply code/config changes, deploy or make automated hiring decisions. OSINT source explicitly separates implementation, deterministic qualification and live qualification. Provider access, durable stores and production receipts remain distinct.
Product domains / Personal life & agency↗ @lssm-tech/module.personal-experience
packages/domains/personal-agency/moduleAuthority-first RoleMorph and reversible Personalization composition for PersonalOS surfaces.
Source & scope
Authority-aware RoleMorph composition then presentation-only preferences; explicit choices win, reset is complete, and missing delegated authority fails closed. PersonalOS keeps subject identity, consent, revision and exact-command authority explicit. Sharing does not transfer employer authority or disclose unrestricted private data.
Product domains / Personal life & agency↗ @lssm-tech/module.personal-community
packages/domains/personal-agency/personal-communitySubject-bound, consent-controlled HCircle community domain runtime.
Source & scope
Consent-bound hCircle community semantics and deterministic orchestration. Hosts own encrypted persistence, moderation, transport and UI. PersonalOS keeps subject identity, consent, revision and exact-command authority explicit. Sharing does not transfer employer authority or disclose unrestricted private data.
Product domains / Personal life & agency↗ @lssm-tech/module.personal-founder-support
packages/domains/personal-agency/personal-founder-supportConsent-bound founder-private cockpit and Pactena handoff runtime for PersonalOS.
Source & scope
Pure founder-private orchestration with minimized read-only handoffs. Historical Pactena founder references map to Tendframe per user confirmation; no forms/conversation/key custody is implemented here. PersonalOS keeps subject identity, consent, revision and exact-command authority explicit. Sharing does not transfer employer authority or disclose unrestricted private data.
Product domains / Personal life & agency↗ @lssm-tech/module.personal-goals
packages/domains/personal-agency/personal-goalsPure PersonalOS mission, goals, outcomes, and observed-metrics runtime.
Source & scope
Self-declared missions, goals and observed metric history with exact human receipts. Missing evidence is never filled with a baseline, target or model estimate. PersonalOS keeps subject identity, consent, revision and exact-command authority explicit. Sharing does not transfer employer authority or disclose unrestricted private data.
Product domains / Personal life & agency↗ @lssm-tech/module.personal-household
packages/domains/personal-agency/personal-householdPure PersonalOS household membership, delegation, and revocation runtime.
Source & scope
Explicit membership/delegation with retained revocation history. The reducer cannot infer permission or let a new delegation authorize its own command. PersonalOS keeps subject identity, consent, revision and exact-command authority explicit. Sharing does not transfer employer authority or disclose unrestricted private data.
Product domains / Personal life & agency↗ @lssm-tech/module.personal-learning
packages/domains/personal-agency/personal-learningConsent-bound PersonalOS learning adapter and reversible coaching runtime.
Source & scope
Subject/consent-bound discovery, enrollment, practice and coaching. Does not claim authoritative catalogs, entitlement, deletion propagation, backup restore or canaries. PersonalOS keeps subject identity, consent, revision and exact-command authority explicit. Sharing does not transfer employer authority or disclose unrestricted private data.
Product domains / Personal life & agency↗ @lssm-tech/module.personal-life-admin
packages/domains/personal-agency/personal-life-adminSubject-bound PersonalOS life administration and personal knowledge runtime.
Source & scope
Calendar, reminder, search, files, care and rights orchestration. Host adapters retain providers, keys and durable authority; local PGlite evidence is not production qualification. PersonalOS keeps subject identity, consent, revision and exact-command authority explicit. Sharing does not transfer employer authority or disclose unrestricted private data.
Product domains / Personal life & agency↗ @lssm-tech/module.personal-operations
packages/domains/personal-agency/personal-operationsFail-closed PersonalOS performance, capacity, release, rollback, and support controls.
Source & scope
Pure performance/capacity, release/rollback and support-access evaluators. Does not deploy, collect telemetry, authenticate support operators or execute rollback. PersonalOS keeps subject identity, consent, revision and exact-command authority explicit. Sharing does not transfer employer authority or disclose unrestricted private data.
Product domains / Personal life & agency↗ @lssm-tech/module.personal-productivity
packages/domains/personal-agency/personal-productivityPure PersonalOS Today planning, habits, recovery, review, and capacity runtime.
Source & scope
Today plans, habits, recovery and weekly review use observed actions; missed days remain unobserved and capacity options require the person's explicit decision. PersonalOS keeps subject identity, consent, revision and exact-command authority explicit. Sharing does not transfer employer authority or disclose unrestricted private data.
Product domains / Personal life & agency↗ @lssm-tech/lib.personal-os-runtime
packages/domains/personal-agency/runtimePure fail-closed PersonalOS authority, replay, projection, and rights runtime.
Source & scope
Pure authorization, event replay and data-rights planning with explicit production transaction ports. Hosts supply verified identity, encrypted stores, clock, audit and effects. PersonalOS keeps subject identity, consent, revision and exact-command authority explicit. Sharing does not transfer employer authority or disclose unrestricted private data.
Product domains / Personal life & agency↗ @lssm-tech/lib.personal-os-spec
packages/domains/personal-agency/specConsent-aware personal mission, agency goal, and projection contracts for LSSM OS.
Source & scope
Revocable personal-mission/agency/projection contracts. CompanyOS, hCircle and founder products receive purpose-limited views rather than unrestricted personal data. PersonalOS keeps subject identity, consent, revision and exact-command authority explicit. Sharing does not transfer employer authority or disclose unrestricted private data.
Product domains / Personal finance & ownership↗ @lssm-tech/module.personal-finance
packages/domains/personal-finance/moduleSubject-bound, non-advisory PersonalOS pocket family-office module.
Source & scope
Pocket family-office orchestration requires exact consent, vault, encryption, state and audit ports; no active account-provider connection is established. Personal finance is a subject-owned, non-advisory PersonalOS scope distinct from business FinanceOS. Hosts own keys, account connections, encrypted stores and execution.
Product domains / Personal finance & ownership↗ @lssm-tech/lib.personal-finance-runtime
packages/domains/personal-finance/runtimePure fail-closed PersonalOS finance runtime.
Source & scope
Pure currency-preserving snapshots, reversible scenarios and cursor/revision-fenced account reconciliation; the package does not own keys or provider effects. Personal finance is a subject-owned, non-advisory PersonalOS scope distinct from business FinanceOS. Hosts own keys, account connections, encrypted stores and execution.
Product domains / Personal finance & ownership↗ @lssm-tech/lib.personal-finance-spec
packages/domains/personal-finance/specSubject-bound, provenance-first, non-advisory PersonalOS finance contracts.
Source & scope
Subject-owned finance records, granular consent and data-rights contracts. Descriptive finance context is distinct from advice or banking execution. Personal finance is a subject-owned, non-advisory PersonalOS scope distinct from business FinanceOS. Hosts own keys, account connections, encrypted stores and execution.
Product domains / Personal health & wellbeing↗ @lssm-tech/module.personal-health
packages/domains/personal-health/moduleSubject-bound non-clinical PersonalOS health ledger orchestration.
Source & scope
Non-clinical ledger orchestration; real providers, encrypted credentials and exports belong to hosts. Simulated PGlite journeys do not qualify live services. Personal health is a consent-controlled, non-clinical wellness ledger. It does not diagnose, treat, monitor emergencies or establish live provider/regulatory qualification.
Product domains / Personal health & wellbeing↗ @lssm-tech/lib.personal-health-runtime
packages/domains/personal-health/runtimePure PersonalOS health authorization, normalization, reconciliation, and sync runtime.
Source & scope
Consent, strict normalization and replay-safe reconciliation preserve missingness and source evidence; no invented causal or clinical interpretation. Personal health is a consent-controlled, non-clinical wellness ledger. It does not diagnose, treat, monitor emergencies or establish live provider/regulatory qualification.
Product domains / Personal health & wellbeing↗ @lssm-tech/lib.personal-health-spec
packages/domains/personal-health/specConsent, provenance, safety, sharing, and rights contracts for non-clinical PersonalOS health data.
Source & scope
Strict wellness provenance, rights and future qualification declarations exclude diagnosis, treatment, emergency monitoring and regulatory claims. Personal health is a consent-controlled, non-clinical wellness ledger. It does not diagnose, treat, monitor emergencies or establish live provider/regulatory qualification.
Product domains / Hiring, cofounding & collaboration↗ @lssm-tech/module.talent
packages/domains/talent/moduleCofounder, hiring, and cobuild application services over canonical references.
Source & scope
Application services for needs, scorecards, candidate stages and cobuild trials; contacts and work remain canonical in CRM and WorkOS. Talent work models needs, candidates and cobuild trials; contacts and work remain canonical elsewhere, and personnel decisions retain CompanyOS governance.
Product domains / Hiring, cofounding & collaboration↗ @lssm-tech/lib.talent-spec
packages/domains/talent/specProvider-neutral cofounder, hiring, and cobuild contracts.
Source & scope
Provider-neutral cofounder/hiring/cobuild contracts; personnel-impacting decisions remain governed by CompanyOS. Talent work models needs, candidates and cobuild trials; contacts and work remain canonical elsewhere, and personnel decisions retain CompanyOS governance.
Product domains / Canonical work & planning↗ @lssm-tech/module.work-management
packages/domains/work/moduleReusable Work OS application services and web/native view models.
Source & scope
Reusable service/view-model and REST/GraphQL/MCP adapters require verified host context and durable ports; no permissive or in-memory fallback. WorkOS owns canonical Work Graph contracts and reusable behavior. Hosts supply current authority, durable stores, providers and production migration/sync qualification.
Product domains / Canonical work & planning↗ @lssm-tech/lib.work-runtime
packages/domains/work/runtimePure Work Graph reducers, event processing, recurrence, idempotency, and sync conflict decisions.
Source & scope
Pure immutable-event reducers, recurrence, merge authority and leased outbox interfaces. Concrete PostgreSQL, queues, search, realtime and providers are integrations. WorkOS owns canonical Work Graph contracts and reusable behavior. Hosts supply current authority, durable stores, providers and production migration/sync qualification.
Product domains / Canonical work & planning↗ @lssm-tech/lib.work-spec
packages/domains/work/specCanonical provider-neutral Work Graph contracts for CompanyOS and modular Work OS consumers.
Source & scope
Canonical Work identity, scope, objects and immutable events. Contracts do not schedule work, persist or grant authority; local PostgreSQL checks are not production migration acceptance. WorkOS owns canonical Work Graph contracts and reusable behavior. Hosts supply current authority, durable stores, providers and production migration/sync qualification.
Foundation primitives / Shared contract execution primitives↗ @lssm-tech/lib.contracts-runtime-kernel
packages/foundation/contracts-runtime-kernelOwns framework-neutral contract engines and registries, policy evaluation/guards, rich-reference resolution/redaction, generic form/data-view lookup, idempotency helpers and prompt/resource/PWA registries over supplied ports.
Source & scope
Registration and declarative policy evaluation do not create live authority, domain semantics, providers, storage or a backend. Host authentication, durable audit and effects remain supplied. Compatibility forwards preserve canonical class/function identity; actual package/consumer qualification was not rerun.
Foundation primitives / Shared specification and portable model foundation↗ @lssm-tech/lib.contracts-spec-core
packages/foundation/contracts-specDefines portable contract models for operations, queries/results, events, capabilities, approval requirements, features, data/graph views, forms, policies, knowledge, references, presentations and Connect reference vocabulary.
Source & scope
These are declarations and pure constructors/validators, not transport binding, provider execution, mutable registries, runtime authorization or rendering. The source repeatedly separates the extracted canonical owner from legacy compatibility paths and from producer/consumer qualification.
Foundation primitives / Portable integrity and cryptographic primitives↗ @lssm-tech/lib.crypto-utils
packages/foundation/crypto-utilsSupplies portable SHA hashing, HMAC, random identifiers, encoding, constant-time comparison and canonical-JSON digest primitives across supported JavaScript hosts.
Source & scope
Cryptographic helpers support integrity and authorization implementations but do not themselves provide identity, key custody, a permission grant or a hosted security service. Canonicalization semantics are source-defined; no independent cryptographic audit is asserted.
Foundation primitives / Schema authoring and cross-surface validation↗ @lssm-tech/lib.schema
packages/foundation/schemaProvides shared typed schema/model/scalar/entity helpers and consistent GraphQL, JSON Schema and Zod projections, including explicit enum wire-name mapping.
Source & scope
Schema generators and entity declarations are not a database, deployed GraphQL endpoint, authorization service or UI renderer. GraphQL name mapping preserves domain values while rejecting collisions; actual application integration is outside this review.
Foundation primitives / Portable developer-language utilities↗ @lssm-tech/lib.utils-typescript
packages/foundation/utils-typescriptProvides portable TypeScript type helpers, exhaustiveness support, filesystem/logger port types and canonical REST/MCP/GraphQL operation-naming helpers.
Source & scope
This is a developer primitive package, not a deployed service. The manifest is authoritative for the current export inventory; historical README counts are not used to infer current package size. The declared Core dependency is recorded without inferring an active runtime service.
Shared platform / Agent sessions & coordination↗ @lssm-tech/lib.agent-collaboration
packages/platform/agents/agent-collaborationTenant-safe multiplayer agent session collaboration primitives with deterministic replay.
Source & scope
Tenant-safe append-only session events and replay with a reference store. README explicitly separates team execution, CRDT documents, transport authentication and durable storage.
Shared platform / Agent verification & local sandbox↗ @lssm-tech/lib.agent-evals
packages/platform/agents/agent-evalsAgent evaluation runners, adapters, graders, and recommendation evidence.
Source & scope
Candidate/baseline and route-bound simulated evaluation with progressive canaries. Live_verified requires complete checkpoint health evidence; evaluation does not grant provider access.
Shared platform / Agent sessions & coordination↗ @lssm-tech/module.agent-fleet
packages/platform/agents/agent-fleetAgent fleet management module — fleet, tree, detail, tool registry, and run console surfaces.
Source & scope
Runtime, control-plane and collaboration packages compose explicit host ports. A session, worker declaration or visible tool is not a permission grant or proof of deployed operation.
Shared platform / Agent protocol & evidence↗ @lssm-tech/lib.agent-protocol-spec
packages/platform/agents/agent-protocol-specProvider-neutral durable agent help, uncertainty and common protocol definitions with exact legacy compatibility.
Source & scope
Pure wire contracts and deterministic validation for agent state, delegation, context, help and evidence. The nested agentpacks README assigns trace/audit declarations here; no provider dispatch or signing is performed.
Shared platform / Agent sessions & coordination↗ @lssm-tech/lib.ai-agent
packages/platform/agents/ai-agentAI agent orchestration with MCP and tool support.
Source & scope
Runtime, control-plane and collaboration packages compose explicit host ports. A session, worker declaration or visible tool is not a permission grant or proof of deployed operation.
Shared platform / Conversational & mobile controls↗ @lssm-tech/module.ai-chat
packages/platform/agents/ai-chatAI chat interface module.
Source & scope
Reusable chat, voice or mobile-control scope. Hosts supply product routing, allowed actions and provider bindings; speech support is not evidence of phone-number/call/SMS infrastructure.
Shared platform / AI routes & provider selection↗ @lssm-tech/lib.ai-providers
packages/platform/agents/ai-providersUnified AI provider abstraction layer.
Source & scope
Constructs provider adapters from exact qualified model routes and expiring run-scoped secret leases. It does not select routes or grant authority; legacy factory paths retain separately scoped compatibility.
Shared platform / Agent context & knowledge↗ @lssm-tech/lib.context-storage
packages/platform/agents/context-storageContext pack and snapshot storage primitives.
Source & scope
Context and retrieval stay source-, tenant- and viewer-scoped. Concrete persistence, provider credentials and execution bindings are host-owned; retrieved knowledge is not action authority.
Shared platform / Agent context & knowledge↗ @lssm-tech/module.context-storage
packages/platform/agents/context-storage-moduleContext storage module with persistence adapters.
Source & scope
Context and retrieval stay source-, tenant- and viewer-scoped. Concrete persistence, provider credentials and execution bindings are host-owned; retrieved knowledge is not action authority.
Shared platform / Agent sessions & coordination↗ @lssm-tech/module.execution-console
packages/platform/agents/execution-consoleOperator-facing execution lane console module.
Source & scope
Read-only operator lane, plan, evidence and Agent Run inspector surfaces. Bindings are validated, and the inspector has no execution or approval authority.
Shared platform / Agent sessions & coordination↗ @lssm-tech/lib.execution-lanes
packages/platform/agents/execution-lanesExecution lanes orchestration contracts and runtime for ContractSpec.
Source & scope
Runtime, control-plane and collaboration packages compose explicit host ports. A session, worker declaration or visible tool is not a permission grant or proof of deployed operation.
Shared platform / Agent verification & local sandbox↗ @lssm-tech/lib.harness
packages/platform/agents/harnessHarness orchestration, policy, evidence, and evaluation runtime.
Source & scope
Controlled evaluation and local adapters are source surfaces. Fixtures, local execution and simulated qualification do not prove production availability or hostile-code isolation.
Shared platform / Agent context & knowledge↗ @lssm-tech/lib.knowledge
packages/platform/agents/knowledgeRAG and knowledge base primitives.
Source & scope
Context and retrieval stay source-, tenant- and viewer-scoped. Concrete persistence, provider credentials and execution bindings are host-owned; retrieved knowledge is not action authority.
Shared platform / Conversational & mobile controls↗ @lssm-tech/lib.mobile-control
packages/platform/agents/mobile-controlBuilder mobile-control primitives for review cards, parity, and deep-link-safe actions.
Source & scope
Reusable chat, voice or mobile-control scope. Hosts supply product routing, allowed actions and provider bindings; speech support is not evidence of phone-number/call/SMS infrastructure.
Shared platform / AI routes & provider selection↗ @lssm-tech/lib.provider-ranking
packages/platform/agents/provider-rankingAI provider ranking: benchmark ingestion, scoring, and model comparison.
Source & scope
Benchmark ingestion and deterministic scoring provide research/discovery guidance, not Protocol V1 qualification, persisted model selection, fallback authority or production routing truth.
Shared platform / AI routes & provider selection↗ @lssm-tech/module.provider-ranking
packages/platform/agents/provider-ranking-moduleAI provider ranking module with persistence and pipeline orchestration.
Source & scope
Adds persistence and pipeline/MCP composition around provider-ranking. The README requires host MCP transport and store lifetime; benchmark recommendations remain distinct from production route qualification.
Shared platform / AI routes & provider selection↗ @lssm-tech/lib.provider-runtime
packages/platform/agents/provider-runtimeBuilder provider-runtime helpers for routing, context prep, runtime targets, and receipt normalization.
Source & scope
Provider discovery, scoring and contracts are distinct from exact live route qualification. Production provider activation, current authority and secret custody remain host-controlled.
Shared platform / AI routes & provider selection↗ @lssm-tech/lib.provider-spec
packages/platform/agents/provider-specProvider routing and runtime-target contracts for ContractSpec Builder.
Source & scope
Provider discovery, scoring and contracts are distinct from exact live route qualification. Production provider activation, current authority and secret custody remain host-controlled.
Shared platform / Agent verification & local sandbox↗ @lssm-tech/lib.runtime-sandbox
packages/platform/agents/runtime-sandboxBrowser-compatible PGLite database abstraction and local SQL runtime ports.
Source & scope
Manifest wording broadly mentions sandboxed workloads, but the inspected README documents a browser-compatible PGLite DatabasePort. Catalog this as local SQL/runtime primitives; hostile-code/container isolation was not established.
Shared platform / Conversational & mobile controls↗ @lssm-tech/lib.voice
packages/platform/agents/voiceVoice capabilities: TTS, STT, and conversational AI.
Source & scope
Reusable provider-neutral TTS/STT, turn/transcript orchestration and streaming-compatible audio. The shared Voice interaction role is distinct from phone-number/PSTN transport and meeting infrastructure. Hosts supply product interactions, consent and provider bindings; VoicePatio remains a proposed brand without an inspected app or deployment.
Shared platform / External integration composition↗ @lssm-tech/module.alpic
packages/platform/delivery/alpicAlpic MCP and ChatGPT App hosting helpers.
Source & scope
Shared integration contracts and host UI/helpers remain distinct from provider SDK adapters, tenant credentials, current authorization and live provider qualification.
Shared platform / Background work & event delivery↗ @lssm-tech/lib.bus
packages/platform/delivery/busEvent bus and messaging primitives.
Source & scope
Event, queue and workflow semantics use injected storage and dispatch. In-memory reference adapters or transport leases do not replace durable state, tenant authority or effect authorization.
Shared platform / Catalogs, workspaces & CLI↗ @lssm-tech/lib.cli-runtime
packages/platform/delivery/cli-runtimeDeterministic command-pack discovery and registration for ContractSpec CLI hosts.
Source & scope
Package discovery, static analysis, command-pack or plugin wiring is developer tooling. Host-bound command actions and canonical owner composition remain required; catalog presence is not public registry or live service qualification.
Shared platform / Contract definitions & compatibility↗ @lssm-tech/lib.contracts
packages/platform/delivery/contractsDeprecated source-only monolith compatibility exports.
Source & scope
Deprecated source-only re-export shim, retained for legacy TypeScript-aware consumers. No compiled dist entrypoint and no new product or hosted service implied.
Shared platform / External integration composition↗ @lssm-tech/lib.contracts-integrations
packages/platform/delivery/contracts-integrationsProvider-neutral integration contracts, scoped channel read/write ports, SMS and email interfaces, restricted LinkedIn messaging, and consent-bound meeting capture.
Source & scope
SDK-free provider declarations, guards and topology metadata. Channel ports/specs are not active provider accounts; LinkedIn messages require exact product approval, and meeting capture requires host consent/authority. Shared roles may support Patio directions but do not establish a Patio deployment. See the targeted channel review for exact source-level boundaries.
Shared platform / Contract definitions & compatibility↗ @lssm-tech/lib.contracts-library
packages/platform/delivery/contracts-libraryReusable contract library and registry primitives for ContractSpec applications.
Source & scope
Contract definitions, transformation and compatibility exports support existing consumers. Canonical owners remain explicit; declarations and compatibility shims do not perform hosted effects.
Shared platform / Contract APIs & data runtimes↗ @lssm-tech/lib.contracts-runtime-client-react
packages/platform/delivery/contracts-runtime-client-reactReact runtime adapters for ContractSpec contracts.
Source & scope
Reusable API, data and transport runtime packages. Hosts supply authenticated context, operation registries, storage and deployment configuration; no new public API endpoint is inferred.
Shared platform / Contract APIs & data runtimes↗ @lssm-tech/lib.contracts-runtime-core
packages/platform/delivery/contracts-runtime-coreFramework-neutral in-house query/cache/offline engine and Transport port for ContractSpec data fetching.
Source & scope
Reusable query/cache/offline/transport engine with compatibility forwarding into canonical runtime owners. README marks physical-consumer and resulting-tree acceptance pending; host authentication and offline-storage policy remain explicit.
Shared platform / Contract APIs & data runtimes↗ @lssm-tech/lib.contracts-runtime-server-graphql
packages/platform/delivery/contracts-runtime-server-graphqlGraphQL server runtime adapters for ContractSpec contracts.
Source & scope
Reusable API, data and transport runtime packages. Hosts supply authenticated context, operation registries, storage and deployment configuration; no new public API endpoint is inferred.
Shared platform / Contract APIs & data runtimes↗ @lssm-tech/lib.contracts-runtime-server-mcp
packages/platform/delivery/contracts-runtime-server-mcpMCP server runtime adapters for ContractSpec contracts.
Source & scope
Reusable MCP server registries and transports; tools-only/resource-only hosts need not load UI presentation dependencies. The marketing MCP subpath is a deprecated compatibility copy, not a second marketing owner.
Shared platform / Contract APIs & data runtimes↗ @lssm-tech/lib.contracts-runtime-server-rest
packages/platform/delivery/contracts-runtime-server-restREST server runtime adapters for ContractSpec contracts.
Source & scope
Reusable API, data and transport runtime packages. Hosts supply authenticated context, operation registries, storage and deployment configuration; no new public API endpoint is inferred.
Shared platform / Contract definitions & compatibility↗ @lssm-tech/lib.contracts-spec
packages/platform/delivery/contracts-spec-compatCompatibility facade forwarding original ContractSpec contracts and registries to canonical owners.
Source & scope
Large compatibility facade preserves original object and schema identities while canonical implementation ownership moves to Foundation, domains and platform packages. Nested editions/agentpacks docs explicitly forward to canonical owners; count this package once.
Shared platform / Contract definitions & compatibility↗ @lssm-tech/lib.contracts-transformers
packages/platform/delivery/contracts-transformersContract format transformations: import/export between ContractSpec and external formats (OpenAPI, AsyncAPI, etc.).
Source & scope
Contract definitions, transformation and compatibility exports support existing consumers. Canonical owners remain explicit; declarations and compatibility shims do not perform hosted effects.
Shared platform / Catalogs, workspaces & CLI↗ @lssm-tech/lib.contractspec-catalog
packages/platform/delivery/contractspec-catalogVersioned, machine-readable ContractSpec package and capability catalog.
Source & scope
Machine-readable inventory and capability metadata. Prepared catalog artifacts explicitly keep registryReconciled=false until signed release reconciliation; workspace discovery is not a public package publication claim.
Shared platform / Telemetry, costs & operational evidence↗ @lssm-tech/lib.cost-tracking
packages/platform/delivery/cost-trackingAPI cost tracking and budgeting.
Source & scope
Legacy number-based totals remain compatibility estimates; authoritative exact-cost helpers are separate. Cost calculations do not authorize providers or become billing invoices.
Shared platform / Governed data exchange & files↗ @lssm-tech/lib.data-exchange-client
packages/platform/delivery/data-exchange-clientShared controllers plus web and native UI surfaces for data interchange.
Source & scope
Import, export, attachment and projection interfaces preserve explicit storage, grant, field and purpose boundaries. Package co-location does not imply unrestricted shared records.
Shared platform / Governed data exchange & files↗ @lssm-tech/lib.data-exchange-core
packages/platform/delivery/data-exchange-coreSchemaModel-first core primitives for data import/export and mapping.
Source & scope
Import, export, attachment and projection interfaces preserve explicit storage, grant, field and purpose boundaries. Package co-location does not imply unrestricted shared records.
Shared platform / Governed data exchange & files↗ @lssm-tech/lib.data-exchange-server
packages/platform/delivery/data-exchange-serverServer-side adapters and execution services for SchemaModel-first data interchange.
Source & scope
Import, export, attachment and projection interfaces preserve explicit storage, grant, field and purpose boundaries. Package co-location does not imply unrestricted shared records.
Shared platform / Governed data exchange & files↗ @lssm-tech/lib.exporter
packages/platform/delivery/exporterCompatibility exporter shim backed by the data-exchange core.
Source & scope
Import, export, attachment and projection interfaces preserve explicit storage, grant, field and purpose boundaries. Package co-location does not imply unrestricted shared records.
Shared platform / Lifecycle, rollout & quality↗ @lssm-tech/lib.feature-flags
packages/platform/delivery/feature-flagsFeature flags and experiments module for ContractSpec applications.
Source & scope
Lifecycle advice, flags, tests and infrastructure intent support reviewed delivery. Plans and fixture evidence do not deploy services or establish operational qualification.
Shared platform / Governed data exchange & files↗ @lssm-tech/lib.files
packages/platform/delivery/filesFiles, documents and attachments module for ContractSpec applications.
Source & scope
Import, export, attachment and projection interfaces preserve explicit storage, grant, field and purpose boundaries. Package co-location does not imply unrestricted shared records.
Shared platform / Forms lifecycle & collection↗ @lssm-tech/lib.forms-runtime
packages/platform/delivery/forms-runtimeComplete caller-port Forms lifecycle, compiler, validation and PII-safe export runtime.
Source & scope
Complete caller-port Forms lifecycle, compiler, consent, navigation and safe export runtime. Concrete authority, storage, clocks, IDs, tokens and event delivery remain injected; module Forms owns UI/composition.
Shared platform / Contract APIs & data runtimes↗ @lssm-tech/lib.graphql-core
packages/platform/delivery/graphql-coreShared GraphQL core: Pothos builder factory, scalars, tracing & complexity.
Source & scope
Reusable API, data and transport runtime packages. Hosts supply authenticated context, operation registries, storage and deployment configuration; no new public API endpoint is inferred.
Shared platform / Contract APIs & data runtimes↗ @lssm-tech/lib.graphql-federation
packages/platform/delivery/graphql-federationPothos federation helpers and subgraph schema export utilities.
Source & scope
Reusable API, data and transport runtime packages. Hosts supply authenticated context, operation registries, storage and deployment configuration; no new public API endpoint is inferred.
Shared platform / Contract APIs & data runtimes↗ @lssm-tech/lib.graphql-prisma
packages/platform/delivery/graphql-prismaPothos + Prisma builder factory with injectable client/DMMF.
Source & scope
Reusable API, data and transport runtime packages. Hosts supply authenticated context, operation registries, storage and deployment configuration; no new public API endpoint is inferred.
Shared platform / Lifecycle, rollout & quality↗ @lssm-tech/lib.infra-ops-spec
packages/platform/delivery/infra-ops-specProvider-neutral infrastructure operations contracts and evidence for autonomous-company deployment and incident loops.
Source & scope
Contract/evidence layer for infrastructure intent and incident/deployment loops. It explicitly does not deploy, page people, resolve secrets, run migrations or call providers.
Shared platform / External integration composition↗ @lssm-tech/module.integration-hub
packages/platform/delivery/integration-hubFour reusable integration-data, credential-setup, model and Markdown-rendering primitives.
Source & scope
README identifies four narrow reusable hooks/model/renderer primitives while the manifest description still says three. Use the explicit current README/export surface; credential setup UI and pure topology validation do not verify a live provider.
Shared platform / Background work & event delivery↗ @lssm-tech/lib.jobs
packages/platform/delivery/jobsBackground jobs and scheduler module for ContractSpec applications.
Source & scope
Queue, scheduler and at-least-once outbox interfaces preserve caller-owned durable storage and domain dispatch. In-memory adapters and transport claims are not runtime effect authority.
Shared platform / Lifecycle, rollout & quality↗ @lssm-tech/lib.lifecycle
packages/platform/delivery/lifecycleContract lifecycle management primitives.
Source & scope
Lifecycle advice, flags, tests and infrastructure intent support reviewed delivery. Plans and fixture evidence do not deploy services or establish operational qualification.
Shared platform / Lifecycle, rollout & quality↗ @lssm-tech/module.lifecycle-advisor
packages/platform/delivery/lifecycle-advisorDeterministic lifecycle recommendations built on shared lifecycle definitions.
Source & scope
Lifecycle advice, flags, tests and infrastructure intent support reviewed delivery. Plans and fixture evidence do not deploy services or establish operational qualification.
Shared platform / Lifecycle, rollout & quality↗ @lssm-tech/module.lifecycle-core
packages/platform/delivery/lifecycle-coreCore lifecycle stage definitions and transitions.
Source & scope
Lifecycle advice, flags, tests and infrastructure intent support reviewed delivery. Plans and fixture evidence do not deploy services or establish operational qualification.
Shared platform / Telemetry, costs & operational evidence↗ @lssm-tech/lib.logger
packages/platform/delivery/loggerComprehensive logging library optimized for Bun with ElysiaJS integration.
Source & scope
Logging, signals and cost projections expose bounded evidence. Signal declarations do not emit telemetry, estimates are not provider actuals or invoices, and observations never grant effects.
Shared platform / Telemetry, costs & operational evidence↗ @lssm-tech/lib.observability
packages/platform/delivery/observabilityOpenTelemetry-based observability primitives.
Source & scope
Logging, signals and cost projections expose bounded evidence. Signal declarations do not emit telemetry, estimates are not provider actuals or invoices, and observations never grant effects.
Shared platform / Telemetry, costs & operational evidence↗ @lssm-tech/lib.observability-spec
packages/platform/delivery/observability-specPure signal declarations, cost evidence models and deterministic validation shared by observability and billing.
Source & scope
Logging, signals and cost projections expose bounded evidence. Signal declarations do not emit telemetry, estimates are not provider actuals or invoices, and observations never grant effects.
Shared platform / Catalogs, workspaces & CLI↗ @lssm-tech/lib.plugins
packages/platform/delivery/pluginsPlugin API and registry for ContractSpec extensions.
Source & scope
Package discovery, static analysis, command-pack or plugin wiring is developer tooling. Host-bound command actions and canonical owner composition remain required; catalog presence is not public registry or live service qualification.
Shared platform / Lifecycle, rollout & quality↗ @lssm-tech/lib.testing
packages/platform/delivery/testingContract-aware testing utilities and runners.
Source & scope
Lifecycle advice, flags, tests and infrastructure intent support reviewed delivery. Plans and fixture evidence do not deploy services or establish operational qualification.
Shared platform / Background work & event delivery↗ @lssm-tech/lib.workflow-composer
packages/platform/delivery/workflow-composerTenant-aware workflow composition helpers for ContractSpec.
Source & scope
Event, queue and workflow semantics use injected storage and dispatch. In-memory reference adapters or transport leases do not replace durable state, tenant authority or effect authorization.
Shared platform / Catalogs, workspaces & CLI↗ @lssm-tech/module.workspace
packages/platform/delivery/workspaceWorkspace discovery and management module.
Source & scope
Static spec/package/import/doc/test graph analysis plus governed maintenance orchestration. Continuous maintenance requires exact source refs, expiring approval, fenced leases, validation and observed merged outcomes, not inferred completion.
Shared platform / Policy, review & audit↗ @lssm-tech/lib.assurance-spec
packages/platform/governance/assurance-specProvider-neutral assurance and compliance evidence correlation contracts for autonomous-company actions.
Source & scope
Correlation-only assurance and pure quality contract/evidence models. Does not store audit events, query logs, detect anomalies, execute providers or replace Connect policy.
Shared platform / Policy, review & audit↗ @lssm-tech/module.audit-trail
packages/platform/governance/audit-trailAudit trail module for tracking and querying system events.
Source & scope
Policy, review and assurance have distinct owners. Hosts supply current identity, policy, durable receipts and effect ports; declarations, UI controls and correlation records do not independently authorize execution.
Shared platform / Policy, review & audit↗ @lssm-tech/lib.contractspec-connect
packages/platform/governance/contractspec-connectProvider-neutral packet authority and durable decision receipts for ContractSpec Connect.
Source & scope
Policy, review and assurance have distinct owners. Hosts supply current identity, policy, durable receipts and effect ports; declarations, UI controls and correlation records do not independently authorize execution.
Shared platform / Decisioning & workflow governance↗ @lssm-tech/lib.decision-runtime
packages/platform/governance/decision-runtimeDeterministic, effect-free DecisionGraph and PredicateSpec runtime.
Source & scope
Effect-free immutable graph branching with trace and exact revision/digest pins. Creator-authored code is never evaluated; operations and authorization remain workflow/product responsibilities.
Shared platform / Economic evidence contracts↗ @lssm-tech/lib.economic-evidence
packages/platform/governance/economic-evidenceProvider-neutral economic evidence primitives for usage, cost, budget, replay, and projection refs.
Source & scope
Side-effect-free references and append-only economic facts distinguish estimates, reservations, usage, actuals and corrections. They do not execute billing, finance or provider actions.
Shared platform / Improvement, editions & release policy↗ @lssm-tech/module.editions
packages/platform/governance/editionsReusable deterministic edition platform surfaces for resources, UI, workflows, storage, agents, and evidence.
Source & scope
Governed improvement, staged release and edition lifecycles preserve evidence, review and rollback. Host effects, durable stores and current independent authority remain separate from UI and pure projections.
Shared platform / Policy, review & audit↗ @lssm-tech/module.governance-suite
packages/platform/governance/governance-suiteGovernance and audit suite — policy editor, audit trail, and compliance surfaces for the Agent + Workflow pillar.
Source & scope
Policy, review and assurance have distinct owners. Hosts supply current identity, policy, durable receipts and effect ports; declarations, UI controls and correlation records do not independently authorize execution.
Shared platform / Policy, review & audit↗ @lssm-tech/module.human-review
packages/platform/governance/human-reviewGeneric tenant-scoped human review contracts, append-only decisions, and optional React surfaces.
Source & scope
Product-neutral scoped review contracts, append-only decisions and optional UI. In-memory store is development/test only; production policy, routing and durable adapters are host-owned.
Shared platform / Runtime topology & conformance↗ @lssm-tech/lib.lssm-os-provider-conformance
packages/platform/governance/lssm-os-provider-conformanceProvider-neutral qualification contracts and runner for LSSM OS execution adapters.
Source & scope
Provider-neutral topology and execution bind exact source, scope, authority and receipts. Offline conformance and reference adapters do not substitute for live provider and durable-store qualification.
Shared platform / Runtime topology & conformance↗ @lssm-tech/lib.lssm-os-runtime
packages/platform/governance/lssm-os-runtimeDeterministic, provider-neutral planning and execution kernel for LSSM OS.
Source & scope
Provider-neutral topology and execution bind exact source, scope, authority and receipts. Offline conformance and reference adapters do not substitute for live provider and durable-store qualification.
Shared platform / Runtime topology & conformance↗ @lssm-tech/lib.lssm-os-spec
packages/platform/governance/lssm-os-specCanonical, provider-neutral context and goal contracts for LSSM OS.
Source & scope
Provider-neutral topology and execution bind exact source, scope, authority and receipts. Offline conformance and reference adapters do not substitute for live provider and durable-store qualification.
Shared platform / Decisioning & workflow governance↗ @lssm-tech/lib.orchestration-spec
packages/platform/governance/orchestration-specProvider-neutral cross-domain orchestration semantics for autonomous-company workflows.
Source & scope
Pure decisions, orchestration contracts and workflow/SOP composition preserve explicit authority and host dispatch. Authored plans, suggestions and deterministic reducers are not proof of end-to-end autonomous company operation.
Shared platform / Improvement, editions & release policy↗ @lssm-tech/lib.progressive-delivery
packages/platform/governance/progressive-deliveryProgressive-delivery contracts and runtime controls for safe staged rollouts.
Source & scope
Governed improvement, staged release and edition lifecycles preserve evidence, review and rollback. Host effects, durable stores and current independent authority remain separate from UI and pure projections.
Shared platform / Policy, review & audit↗ @lssm-tech/module.review-queue
packages/platform/governance/review-queueReview queue module: human-in-the-loop approval, escalation, audit-grade decision flows, and per-domain health probe.
Source & scope
Policy, review and assurance have distinct owners. Hosts supply current identity, policy, durable receipts and effect ports; declarations, UI controls and correlation records do not independently authorize execution.
Shared platform / Improvement, editions & release policy↗ @lssm-tech/module.self-improving-system
packages/platform/governance/self-improving-systemHeadless orchestration for governed, goal-bound self-improvement.
Source & scope
Governed improvement, staged release and edition lifecycles preserve evidence, review and rollback. Host effects, durable stores and current independent authority remain separate from UI and pure projections.
Shared platform / Improvement, editions & release policy↗ @lssm-tech/lib.self-improving-system-runtime
packages/platform/governance/self-improving-system-runtimeDeterministic policy, compilation, and replay runtime for governed self-improvement.
Source & scope
Governed improvement, staged release and edition lifecycles preserve evidence, review and rollback. Host effects, durable stores and current independent authority remain separate from UI and pure projections.
Shared platform / Decisioning & workflow governance↗ @lssm-tech/lib.sop-runtime
packages/platform/governance/sop-runtimeLiving SOP generation, qualification, drift, health-trigger, and workflow compiler runtime.
Source & scope
Deterministic SOP proposals, qualified source snapshots, drift and health triggers compile workflows without effects. Publication and high-impact execution remain governed by Connect and host workflow authority.
Shared platform / Decisioning & workflow governance↗ @lssm-tech/module.workflow-orchestration
packages/platform/governance/workflow-orchestrationWorkflow orchestration module — board, DAG, dashboard, composer, state-machine, instance lifecycle, approvals.
Source & scope
Module-local in-memory authored-run reducer and host-injected workflow store/dispatcher. Governed automation view models always carry effectAuthority:none.
Shared platform / Localization & accessibility↗ @lssm-tech/lib.accessibility
packages/platform/ui/accessibilityAccessibility preferences, reduced-motion behavior and validation utilities.
Source & scope
Reusable accessibility utilities and translation runtime support product experiences. Utilities and pack metadata are not a certification of every composed product screen; actual contrast, locale and interaction qualification stays per host.
Shared platform / Shared design components & navigation↗ @lssm-tech/lib.cockpit-kit
packages/platform/ui/cockpit-kitType-only cockpit component interfaces and canonical density/expansion variants.
Source & scope
Cross-platform contracts and variant unions only. README explicitly says no component implementation or UI framework dependency; web/native implementations are separate packages.
Shared platform / Shared design components & navigation↗ @lssm-tech/lib.cockpit-kit-native
packages/platform/ui/cockpit-kit-nativeNative lane for cockpit primitives — React Native implementations with cockpit-kit type contracts.
Source & scope
Shared UI source has explicit native/web/type-only boundaries. Import the correct platform owner; reusable components do not establish that every product uses the latest implementation.
Shared platform / Shared design components & navigation↗ @lssm-tech/lib.cockpit-kit-web
packages/platform/ui/cockpit-kit-webWeb lane for cockpit primitives — re-exports cockpit-kit types with web-specific ui/ subpath convention.
Source & scope
Shared UI source has explicit native/web/type-only boundaries. Import the correct platform owner; reusable components do not establish that every product uses the latest implementation.
Shared platform / Design selection & publishing↗ @lssm-tech/lib.design-catalog
packages/platform/ui/design-catalogSerializable built-in design pack and theme catalog for ContractSpec applications.
Source & scope
Serializable design packs, themes and visual-scenario validation. Pack metadata is not measured contrast; pure validation neither renders nor collects visual evidence.
Shared platform / Design selection & publishing↗ @lssm-tech/module.design-studio
packages/platform/ui/design-studioTenant-safe design pack selection, drafting, certification, and reusable studio surfaces.
Source & scope
Design pack discovery, drafting and certification are source-backed. Host identity, durable storage and exact certification remain required for tenant publication.
Shared platform / Shared design components & navigation↗ @lssm-tech/lib.design-system
packages/platform/ui/design-systemDesign tokens and theming primitives.
Source & scope
Shared UI source has explicit native/web/type-only boundaries. Import the correct platform owner; reusable components do not establish that every product uses the latest implementation.
Shared platform / Forms lifecycle & collection↗ @lssm-tech/module.forms
packages/platform/ui/formsReusable builder, respondent, results, and administration module for the shared Forms platform.
Source & scope
Reusable web/native form builder/respondent/results/admin composition with feature milestones. Host-owned authenticated authority, PostgreSQL, keys, routing and optional provider ports are required for published policies.
Shared platform / Operating cockpit↗ @lssm-tech/module.operating-cockpit
packages/platform/ui/operating-cockpitOperator cockpit shell — fleet board, navigation surface, and cross-domain operating screens for the Agent + Workflow pillar.
Source & scope
The operator shell composes fleet, workflow, review and health read models. Host routes and authorization remain separate; a dashboard or disabled control is not execution authority.
Shared platform / Adaptive product presentation↗ @lssm-tech/lib.overlay-engine
packages/platform/ui/overlay-engineRuntime overlay engine for ContractSpec personalization and adaptive UI rendering.
Source & scope
Surface, role, preference, overlay and rendering choices stay within server-resolved permission and data boundaries. UI adaptation never grants hidden routes or actions; framework-specific hosts remain explicit.
Shared platform / Adaptive product presentation↗ @lssm-tech/lib.personalization
packages/platform/ui/personalizationBehavior tracking, analysis, and adaptation helpers for ContractSpec personalization.
Source & scope
Transparent behavior/preference recommendations and scoped private presentation caches. Adaptation respects current role/policy boundaries; server reads and commands remain independently authorized.
Shared platform / Adaptive product presentation↗ @lssm-tech/lib.personalized-presentation
packages/platform/ui/personalized-presentationSchema bridge, React provider and hook that resolve lib.personalization preferences and role variant overrides into cockpit-kit variant literals.
Source & scope
Surface, role, preference, overlay and rendering choices stay within server-resolved permission and data boundaries. UI adaptation never grants hidden routes or actions; framework-specific hosts remain explicit.
Shared platform / Adaptive product presentation↗ @lssm-tech/lib.presentation-runtime-core
packages/platform/ui/presentation-runtime-coreCore presentation runtime for contract-driven UIs.
Source & scope
Surface, role, preference, overlay and rendering choices stay within server-resolved permission and data boundaries. UI adaptation never grants hidden routes or actions; framework-specific hosts remain explicit.
Shared platform / Adaptive product presentation↗ @lssm-tech/lib.presentation-runtime-next
packages/platform/ui/presentation-runtime-nextNext.js lane for contract-driven marketing SEO/LLMO: metadata, JSON-LD, sitemap, robots, and llms.txt/agents.json route handlers.
Source & scope
Next-specific marketing metadata, JSON-LD, sitemaps, robots and AI-discovery handlers. Framework-neutral and React presentation packages stay Next-free.
Shared platform / Adaptive product presentation↗ @lssm-tech/lib.presentation-runtime-react
packages/platform/ui/presentation-runtime-reactReact presentation runtime with workflow components.
Source & scope
Surface, role, preference, overlay and rendering choices stay within server-resolved permission and data boundaries. UI adaptation never grants hidden routes or actions; framework-specific hosts remain explicit.
Shared platform / Adaptive product presentation↗ @lssm-tech/lib.presentation-runtime-react-native
packages/platform/ui/presentation-runtime-react-nativeReact Native presentation runtime for mobile apps.
Source & scope
Surface, role, preference, overlay and rendering choices stay within server-resolved permission and data boundaries. UI adaptation never grants hidden routes or actions; framework-specific hosts remain explicit.
Shared platform / Adaptive product presentation↗ @lssm-tech/lib.surface-runtime
packages/platform/ui/surface-runtimeAI-native surface specs and web runtime for adaptive ContractSpec surfaces.
Source & scope
Feature Hub installation is read-only; start is an explicit host-controlled effect boundary. Signed discovery resolves allowlisted code only, and RoleMorph cannot bypass current action or data permissions.
Shared platform / Localization & accessibility↗ @lssm-tech/lib.translation-runtime
packages/platform/ui/translation-runtimeFramework-independent ContractSpec translation runtime.
Source & scope
Reusable accessibility utilities and translation runtime support product experiences. Utilities and pack metadata are not a certification of every composed product screen; actual contrast, locale and interaction qualification stays per host.
Shared platform / Shared design components & navigation↗ @lssm-tech/lib.ui-kit
packages/platform/ui/ui-kitCross-platform UI components for React Native and web.
Source & scope
Shared UI source has explicit native/web/type-only boundaries. Import the correct platform owner; reusable components do not establish that every product uses the latest implementation.
Shared platform / Shared design components & navigation↗ @lssm-tech/lib.ui-kit-core
packages/platform/ui/ui-kit-coreCore UI primitives and utilities.
Source & scope
Shared UI source has explicit native/web/type-only boundaries. Import the correct platform owner; reusable components do not establish that every product uses the latest implementation.
Shared platform / Shared design components & navigation↗ @lssm-tech/lib.ui-kit-web
packages/platform/ui/ui-kit-webWeb UI components with Radix primitives.
Source & scope
Shared UI source has explicit native/web/type-only boundaries. Import the correct platform owner; reusable components do not establish that every product uses the latest implementation.
Shared platform / Shared design components & navigation↗ @lssm-tech/lib.ui-link
packages/platform/ui/ui-linkDeep linking utilities for navigation.
Source & scope
Tiny router-independent shared link component. README excludes Expo-router, Next Link behavior and complex navigation abstractions.
No package matches these filters. Clear a filter or search another term.