Specializes
A specification expresses a more specific responsibility within the ContractSpec architecture.
From shared language
to specific systems.
29 specialized specifications connect the core ContractSpec model to the domains, platforms and services of the LSSM ecosystem.
Explore what each specification defines, its declared package dependencies and the implementations associated with it.
Domain specifications
22 specificationsCompany, commerce & growth
domain specification
Crypto payments specs
Provider-neutral crypto wallet governance and HTTP-native agent payment protocol contracts.
@lssm-tech/lib.crypto-payments-specFollow this specification ↗domain specificationBilling specs
Country-neutral BillingOS quote-to-cash contracts, invariants, and agent action governance types.
@lssm-tech/lib.billing-specFollow this specification ↗domain specificationCompanyOS specs
Contract-first CompanyOS V0/V1 specifications for bounded company operations.
@lssm-tech/lib.companyos-specFollow this specification ↗domain specificationFinance specs
Provider-neutral internal finance operations contracts beyond BillingOS quote-to-cash.
@lssm-tech/lib.finance-ops-specFollow this specification ↗domain specificationGrowth specs
Provider-neutral growth and marketing operation contracts for autonomous-company campaign, lifecycle, and publishing handoffs.
@lssm-tech/lib.growth-specFollow this specification ↗People, life & work
domain specification
Founder intelligence specs
Provider-neutral contracts for founder-private intelligence, executive projections, and operating archetypes.
@lssm-tech/lib.founder-intelligence-specFollow this specification ↗domain specificationOrganization & planning specs
Provider-neutral organization, planning, agenda, booking, and auto-scheduling contracts for autonomous-company operations.
@lssm-tech/lib.organization-planning-specFollow this specification ↗domain specificationPersonalOS specs
Consent-aware personal mission, agency goal, and projection contracts for LSSM OS.
@lssm-tech/lib.personal-os-specFollow this specification ↗domain specificationPersonal finance specs
Subject-bound, provenance-first, non-advisory PersonalOS finance contracts.
@lssm-tech/lib.personal-finance-specFollow this specification ↗domain specificationPersonal health specs
Consent, provenance, safety, sharing, and rights contracts for non-clinical PersonalOS health data.
@lssm-tech/lib.personal-health-specFollow this specification ↗domain specificationTalent specs
Provider-neutral cofounder, hiring, and cobuild contracts.
@lssm-tech/lib.talent-specFollow this specification ↗domain specificationWork Graph specs
Canonical provider-neutral Work Graph contracts for CompanyOS and modular Work OS consumers.
@lssm-tech/lib.work-specFollow this specification ↗Channels & experiences
domain specification
Communication specs
Canonical communication contracts, operations, events, and validation helpers for ContractSpec.
@lssm-tech/lib.communication-specFollow this specification ↗domain specificationCreator operations specs
Provider-neutral creator-operations contract definitions: campaign, submission, wallet, training, quiz and accrual operation, schema, port and feature specs extracted unchanged from ContractSpec compatibility.
@lssm-tech/lib.creator-operations-specFollow this specification ↗domain specificationSupport specs
Provider-neutral SupportOS customer-support contract definitions: case, authority, operation, event, schema and feature specs extracted unchanged from ContractSpec compatibility.
@lssm-tech/lib.customer-support-specFollow this specification ↗domain specificationGamification specs
Portable cross-vertical gamification campaign contracts and validation.
@lssm-tech/lib.gamification-specFollow this specification ↗Data & intelligence
domain specification
Content analysis specs
Evidence-first provider-neutral content analysis and content-generation contracts.
@lssm-tech/lib.content-analysis-specFollow this specification ↗domain specificationCreative intelligence specs
Evidence-first creative trend, hypothesis, outcome, and benchmark contracts.
@lssm-tech/lib.creative-intelligence-specFollow this specification ↗domain specificationOSINT specs
Evidence-first, provider-neutral OSINT v0 schemas and contracts.
@lssm-tech/lib.osint-specFollow this specification ↗Agents & governance
domain specification
Identity & AuthOS specs
Contract-first AuthOS specifications for identity, authentication, federation, and security-gated account surfaces.
@lssm-tech/lib.authos-specFollow this specification ↗domain specificationOpportunity specs
Provider-neutral opportunity scoring and selection contracts for autonomous-company candidates.
@lssm-tech/lib.opportunity-specFollow this specification ↗Platform specifications
7 specificationsBuild & runtime
platform specification
Infrastructure operations specs
Provider-neutral infrastructure operations contracts and evidence for autonomous-company deployment and incident loops.
@lssm-tech/lib.infra-ops-specFollow this specification ↗platform specificationObservability specs
Pure signal declarations, cost evidence models and deterministic validation shared by observability and billing.
@lssm-tech/lib.observability-specFollow this specification ↗platform specificationLSSM OS specs
Canonical, provider-neutral context and goal contracts for LSSM OS.
@lssm-tech/lib.lssm-os-specFollow this specification ↗Agents & governance
platform specification
Agent protocol specs
Provider-neutral durable agent help, uncertainty and common protocol definitions with exact legacy compatibility.
@lssm-tech/lib.agent-protocol-specFollow this specification ↗platform specificationProvider routing specs
Provider routing and runtime-target contracts for ContractSpec Builder.
@lssm-tech/lib.provider-specFollow this specification ↗platform specificationAssurance specs
Provider-neutral assurance and compliance evidence correlation contracts for autonomous-company actions.
@lssm-tech/lib.assurance-specFollow this specification ↗platform specificationOrchestration specs
Provider-neutral cross-domain orchestration semantics for autonomous-company workflows.
@lssm-tech/lib.orchestration-specFollow this specification ↗Read the relationship, then its evidence.
Declares a dependency
A pinned package manifest names another package. The source records the direction of that dependency.
Supports a system
The inspected inventory connects the specification to the products and service roles it describes. Production bindings are documented separately.
LSSM owns the ecosystem. Patio is its specialized infrastructure and data holding; the graph keeps this organization separate from technical dependencies.
Inspect the full package inventory ↗