Contexte et intelligence
BrainOS
Connaissances, mémoire et intelligence, disponibles dans le bon contexte.
LA DIRECTION LSSM
Un système connecté, conçu pour évoluer avec vous.
Des produits connectés peuvent partager du sens, de l’intelligence et des services tout en conservant des expériences distinctes. BrainOS apporte le contexte et l’intelligence, ContractSpec définit et construit, et Patio fournit l’infrastructure et les données partagées. LSSM OS compose ces apports, puis fait fonctionner et exploite les environnements qui les utilisent.
Des logiciels qui s’adaptent à votre vie, à votre organisation et à vos appareils, et qui continuent à s’améliorer lorsque vos besoins évoluent.
LE SYSTÈME CONNECTÉILLUSTRATION
Créer, adapter et exécuter. Ensemble.
Un modèle commun relie la finalité du logiciel, sa création et son fonctionnement.
Défini avec ContractSpec
Objectifs, sens métier, données, comportements, contrats et politiques.
Créer et adapter
L’IA aide à générer des composants source ou à composer des interfaces prises en charge dans une application.
Exécuter et réutiliser
Des composants existants et des moteurs déterministes exécutent directement le travail défini.
L’IA peut aider à faire évoluer l’expérience. Les opérations quotidiennes peuvent fonctionner sans nouvel appel à un modèle.
LSSM / Des logiciels connectés qui évoluent
Contrats. Intelligence. Infrastructure et données.
Composés et exploités ensemble.
Des rôles distincts.
Une architecture d’exploitation.
Au sein de LSSM, ContractSpec et les spécifications spécialisées définissent les contrats. BrainOS apporte le contexte et l’intelligence. Patio porte le périmètre de l’infrastructure et des données partagées. LSSM OS réunit ces responsabilités dans les environnements d’exploitation.
LSSM Un écosystème propriétaire · des responsabilités distinctes
Contrats et construction
ContractSpec
Définir les comportements, construire des capacités réutilisables et vérifier le travail.
Spécifications spécialisées des domaines et plateformesInfrastructure et données partagées
Patio
La holding spécialisée de LSSM pour l’infrastructure, les données, la transmission et les flux. Des rôles partagés dans tous les domaines.
Périmètre de l’infrastructure et des donnéesRÉUNIS PAR
LSSM OS
Compose les contrats, l’intelligence, l’infrastructure et les données. Fait fonctionner et exploite les environnements qui les utilisent.
EXÉCUTION ET EXPLOITATIONArchitecture cible de l’écosystème. ContractSpec se spécialise en contrats de domaine et de plateforme. Les fondations se réunissent à travers LSSM OS ; chaque relation technique conserve ses propres éléments probants.
Patio: la holding spécialisée dans l’infrastructure et les données au sein de LSSM, avec des marques produit ciblées. La mise en œuvre et la disponibilité sont documentées pour chaque service. Examiner le périmètre ↗ · Explorer les produits ↗
One language.
Specialized responsibilities.
Follow ContractSpec into the specifications that define a domain or platform, then into the systems and services that use them.
PRODUCT PLATFORMS & SHARED CAPABILITIES
Technology with
a clear job to do.
Alongside the shared architecture, focused platforms support communication, commercial operations, research and personal applications.
Explore the technical platforms ↗Product platform · app & reusable bundle
CommunicationOS
Conversations with clear context and boundaries
Un kit applicatif de communication réutilisable comprenant boîte de réception, espaces, salons, connexions aux canaux officiels, recherche, réunions, travail encadré et formulaires. Le même modèle canonique de routes et d’autorité sert les hôtes autonomes et intégrés.
StandaloneWeb and PWA application
EmbeddedReusable application kit and contextual slots
Expérience produithCircle Human Topography and Chat
Inspected app & reusable bundle source
Source & current scope
Inspected standalone app and reusable bundle source; no new live verification. Inspected lssm-tech/contractspec@17053b80fbb6ef6e8600cbdf9e03015d5b421eda on tboutron/completion-2026-10-20. Source composition does not establish a newly launched service.
Inspect the pinned component source ↗Component provenance & replacement targets ↗Original app and hCircle landing components
SIGNAL AUTORISÉ
Boîte de réception des communications
Revenez à la conversation active ou passez volontairement d’un salon à l’autre.
SALON ACTIF
Direction
Un message enregistré durablement
Ouvrir la conversation
DIRECTION · JEU D’ESSAI SOURCE
Un message enregistré durablement
Extrait de conversation en lecture seule. Aucun message n’est envoyé.
Composant CommunicationInbox · jeu d’essai du code source · hCircle est une projection produit de cette plateforme
hCercle
FonctionnalitésPour les personnesConfiance
Le lien humain, sans la machine à capter l’attention
Un espace pour les relations qui font une vie.
hCircle réunit les conversations, les cercles et les communautés sans transformer les personnes en contenu, en métriques ou en une seule immense audience.
Aucun fil d’engagement · aucun score relationnel caché · aucun partage silencieux entre contextes
vousfoyeramiscercle
le contexte ne circule
que lorsque vous le décidez
hCircle Human Topography · véritable composant marketing du code source CommunicationOS
Billing & finance
Commercial work, financial records and the handoff between them.
Acquisition & intelligence
Acquire information, preserve its provenance and investigate it.
Usage & measurement
Connect usage evidence and metrics while preserving their purpose.
Embedded correspondence
Explore the proposed email infrastructure through its own website.
Composed personal applications
See how focused personal experiences form a coherent application.
REUSABLE SERVICESUnderstand.
Understand.
Build. Operate. Improve.
Follow the shared services underneath the products, from useful evidence to governed execution. Each role connects its source, scope and related work.
Explore the complete package map ↗01 / DATA PLATFORMSFrom collection to useful evidence.
Shared entities, social signals, temporal context and governed exchange.
Explore data services ↗02 / INFRASTRUCTUREReusable systems beneath the work.Email with MailPatio, a proposed phone channel with PhonePatio, communication, billing and operating services.
Explore infrastructure ↗03 / TOOLCHAIN & AGENTSFrom an idea to a system that improves.Opportunity evaluation, builders, agents, verification, delivery, recovery and governance.
Explore the toolchain ↗PATIO / SHARED INFRA/DATAShared infrastructure.
Shared infrastructure.
Connected data.
Patio is LSSM’s specialized infrastructure and data holding. Shared services connect every area; specialized brands turn parts of this common core into focused experiences.
THE COMPLETE SOURCE MAP
Explore the inspected package map ↗Every package has a place.
Follow product domains, platform primitives and composed bundles into their roles across the ecosystem.
LES CAPACITÉS / DES CHAMPS DE TRAVAIL RELIÉS
Quel travail faut-il accomplir ?
Les capacités relient les produits et les publics. Explorez le travail, puis les expériences qui y répondent.
Personnes, travail et contribution
Career progress, useful missions, learning and community coordination.
Voir cette catégorie dans l’atlasOpérations de l’entreprise
Assistance, administration, commercial work and company operating modes.
Voir cette catégorie dans l’atlasMise sur le marché, identité de marque et croissance
Position an offer, build demand, distribute it, sell and learn from outcomes.
Voir cette catégorie dans l’atlasProduit, connaissances et intelligence
Turn context and product evidence into decisions, specifications and reviewed delivery.
Voir cette catégorie dans l’atlasDonnées, acquisition et investigation
Acquire source material, trace evidence and investigate a question.
Voir cette catégorie dans l’atlasFinance, facturation et mesure
Keep financial work, quote to cash, billable usage and product metrics distinct.
Voir cette catégorie dans l’atlasVie personnelle, autonomie et santé
Connect personal goals, daily plans and health context through bounded experiences.
Voir cette catégorie dans l’atlasBUILD WITH THE PIECESStart with a purpose.
Start with a purpose.
Shape the system.
A portal, a launch, a personal space or an operating system. Add a capability and watch the experience take a different form.
01 Choose a starting point
02 Make it your own
An authored composition illustration. These controls assemble sample views locally.
studio-you.local / webLIVE ILLUSTRATION
VOTRE COMPOSITION
Studio & you
A clear home for the relationship.
Meaning & policy→3 capacités→Application web
MAKE A CHANGE. SEE THE EFFECT.
This is your kept starting point. Try changing a capability or interface.
GO DEEPER
Every piece has a place to begin.
Select a capability to inspect its source foundations and customization seams.
Fit access to people and organizations.
Give people and organizations clear sign-in flows, roles and access boundaries.
- Customize
- Choose authentication providers, sign-in flows, roles and access policies.
- Personalize
- Present the account and organization context appropriate to the signed-in person.
Inspect the composition JSON · illustrative
Presentation choices do not create permissions. Production composition still needs the selected runtime, provider configuration and validation.
{
"kind": "local-composition-illustration",
"purpose": "Customer portal",
"name": "Studio & you",
"capabilities": [
"identity",
"billing",
"communication"
],
"surface": "web",
"creationPath": "source-generation",
"authority": "supplied separately by the host",
"execution": "sample rendering only"
}BUILT TO EVOLVE
Generate. Regenerate. Keep improving.
Express a new goal, workflow or experience in shared definitions. Reuse existing pieces, generate what is needed and regenerate supported outputs as those definitions change. The same direction connects reviewed source changes with controlled adaptation inside an app.
- 01
Describe the intent
Make the goal, domain meaning and expected behavior explicit.
- 02
Compose or generate
Reuse known pieces, generate source or propose a runtime interface.
- 03
Validate the change
Check contracts, policies, compatibility and the required review.
- 04
Run, observe, refine
Use the resulting software and evolve it as needs change.
FOLLOW A CHANGE
A team needs a new operating view and an additional approval step.
- Ce qui change
- Update the shared definitions, reuse domain components and let AI propose the source changes. Regenerate the supported artifacts that depend on those definitions.
- Rules and review
- Validate the proposal and affected contracts, inspect the differences and apply the configured checks and approval path.
- The intended result
- The accepted components become part of the application. Ordinary rendering and workflow execution can run without asking a model to recreate them.
A person needs a different view of the same work for their current task.
- Ce qui change
- AI can plan or adapt a supported surface using registered components. Role, context and preferences help shape the resulting interface.
- Rules and review
- Validate the surface or patch, preserve permission and action boundaries, and keep explicit preferences under the person’s control.
- The intended result
- The adapted interface uses known components and calls existing operations. Its everyday behavior follows the application’s configured rules.
Illustrative flows. Generation targets, runtime adaptation and review depend on the selected composition.
Explore the generation foundations ↗Illustration : In the source.
A change has an owner and a set of consequences.Trace the mechanism · 3 ways to look closer＋
A report export now needs a reason. Follow the change through authored meaning, derived output and a caller that still uses the old input.
Which part are you changing?
UNE SITUATION CONCRÈTE
The requirement becomes part of declared behavior.
A required reason is added to the operation input.
01 / Author
Change the declaration that owns the required input.
Ce qui change
Callers must now supply the new field for that contract version.
Ce qui reste explicite
The handler still decides how the reason affects the business work.
SUIVRE LA CONSÉQUENCE
Plan compatibility for existing consumers. A required input can be a behavioral break even if the handler’s main implementation is unchanged.
CONTINUE WITH THE DETAIL
Where this explanation comes from
An authored situation, grounded in the linked source guides. Choosing a case explores its expected responsibilities; it does not execute an operation.
AI CREATION + DETERMINISTIC EXECUTION
Create with AI. Run on dependable foundations.
AI can help create the software and reshape the experience. The resulting work can run through prebuilt components, domain logic and conventional runtimes.
Generate and adapt.
- Propose components, interfaces and source changes.
- Compose supported surfaces while an app is in use.
- Evolve the experience around goals, tasks and context.
Execute and reuse.
- Render registered components and run defined operations.
- Apply calculations, state transitions and configured policy checks.
- Handle routine work without requiring a model call.
ContractSpec carries the meaning across both paths: what a capability does, which data it uses, how it connects to other pieces and which policy boundaries apply.
A new interface. The same reusable operations.
An AI-composed task view can use existing form, data-view and action components. Those controls call the registered domain operations, with the same configured permissions and validation as an authored view.
Reuse the foundations. Optimize the common paths.
Start with prebuilt renderers, domain logic and runtime services. Caching, request deduplication and replay can avoid repeated work in supported paths. The aim is flexible software with predictable behavior, controlled model costs and performance that can be measured and improved.
Choose where intelligence helps this task.Compare the choices · 3 ways to look closer＋
Consider a team that needs a new task view. Creating the view, rendering it and changing business state are different kinds of work.
What needs to happen now?
UNE SITUATION CONCRÈTE
Use generation to propose a change.
The team needs a new arrangement of fields and actions.
Défini avec ContractSpec
- Objectif
- Sens
- Contrats
- Politique
FAÇONNER LE LOGICIEL
Create & adapt
AI proposes the arrangement of fields, context and actions.
UTILISER LE LOGICIEL
Run & reuse
Accepted components and operations supply the working experience.
A proposed component or surface, ready to inspect.
Review the proposed change before it becomes the accepted view.
Pourquoi la création et l’exécution restent liées
Ce qui change
AI can propose source components or a supported surface composition.
Ce qui reste explicite
The proposal needs declared meaning, valid component bindings and the applicable review.
SUIVRE LA CONSÉQUENCE
Keep the generated proposal reviewable. Accepted source or registered components can then serve ordinary interactions without recreating the interface on every request.
CONTINUE WITH THE DETAIL
Where this explanation comes from
An authored task-view example based on the captured LSSM direction and source guides. It distinguishes AI proposals, supported runtime surfaces and ordinary execution; it is not a performance benchmark.
SHAPED AROUND PEOPLE
Customize the system. Personalize the experience.
Shape the workflow, the interface and the way people interact with it—all around shared meaning and behavior.
Fit the organization.
Choose domain capabilities, business rules, integrations, workflows and components. Extend or generate the pieces your organization needs.
Fit the person.
Shape supported experiences around the person, task, role and permitted context: relevant information, layouts, interaction choices and level of detail.
Shared meaning. Experiences that fit the interface.
The direction spans web, mobile, native and agent interfaces. Reuse the underlying contracts and capabilities, then adapt layout, navigation and interaction to the host, device and task.
- Web workspaces
- Mobile & native
- Adaptive UI & UX
- Agent interfaces
Explicit choices stay in the person’s control. Explainable suggestions and reversible preferences help the experience improve over time.
See what a personal choice should change.Compare the choices · 3 ways to look closer＋
The same work can be shown in a quiet sequence, a dense overview or a detailed review. Inspect the boundary behind each choice.
What would help in this moment?
UNE SITUATION CONCRÈTE
Reduce the presentation load.
A person wants to focus on the current task without losing the rest of the workflow.
Ce qui change
A focused surface can show one section, a clear next step and optional supporting context.
Ce qui reste explicite
The complete underlying work and the person’s actual permissions do not change.
SUIVRE LA CONSÉQUENCE
Give a visible route back to the full picture. This site’s Focus and Step by step controls demonstrate a reversible reading projection.
CONTINUE WITH THE DETAIL
Where this explanation comes from
Source-informed presentation examples. The local website applies its own authored projections; the V9 source review inspected preference precedence, role independence, shell boundaries and reversible adaptation in ContractSpec.
VOIR L’IDÉE PRENDRE FORMEDe l’intention à une expérience
De l’intention à une expérience
que vous pouvez vous approprier.
Une courte présentation illustrée du sens partagé, de la création assistée par l’IA et de l’exécution réutilisable.
Puis essayez vous-même ↗Lire la présentation
Intention. Partez d’un objectif. ContractSpec donne aux éléments un sens, des données, un comportement et des règles communs.
Créer et exécuter. L’IA peut aider à générer du code source ou à composer les interfaces prises en charge. Des composants réutilisables et des moteurs d’exécution classiques exécutent le travail défini.
Adapter. Un même travail peut se présenter différemment sur ordinateur, sur mobile ou pour un agent, dans les limites d’action applicables.
Composer. Réunissez les capacités des domaines autour du résultat : communication, facturation, croissance, création et bien plus.
Télécharger la transcription complète ↓REUSABLE DOMAIN PIECES
Start with a domain. Make it yours.
Prebuilt pieces for the recurring work of a product: billing, build, communication, content, growth and more. Assemble the capabilities you need, adapt the workflow and shape the experience around the people using it.
Prebuilt for the domain
Start with defined behavior, schemas, modules and integration points.
Customizable by the team
Adapt rules, providers, workflows and interfaces to the product.
Personalizable for people
Use roles, preferences and permitted context to shape the experience.
Choose a domain to see its pieces and what you can adapt.
Billing & finance
Make commercial lifecycles explicit.
Model quotes, invoices and payment lifecycles with the rules and review steps your business needs.
EXPLORE THE CAPABILITIES
Customize the workflow
Choose tax rules, review steps and the host that executes billing actions.
Personalize the experience
Compose billing views for each role, with the selected level of detail.
Build & delivery
Take a requirement into reviewable work.
Turn requirements and source material into blueprints, implementation plans and reviewable changes.
EXPLORE THE CAPABILITIES
Customize the workflow
Choose source adapters, implementation policies and the panels your workbench needs.
Personalize the experience
Shape the workbench around the current role, task and chosen preferences.
Communication
Keep conversations connected to the next step.
Bring conversations, channels and reviewed replies into your product.
EXPLORE THE CAPABILITIES
Customize the workflow
Select channels, supply sending authority and embed communication in your product.
Personalize the experience
Choose contextual panels and views for each role, using information that person can access.
Content & publishing
Turn source material into a useful draft.
Analyze source material and shape drafts for the channels and formats you use.
EXPLORE THE CAPABILITIES
Customize the workflow
Supply the model or media providers, choose formats and keep the review steps you need.
Personalize the experience
Use the selected brief, source material and output format to shape each draft.
Growth & referrals
Give referral programs clear rules.
Build referral and affiliate programs with explicit attribution, rewards and payout decisions.
EXPLORE THE CAPABILITIES
Customize the workflow
Define programs, reward policies and the integrations that handle persistence and payments.
Personalize the experience
Compose participant and administrator experiences around their different tasks.
Identity & access
Fit access to people and organizations.
Give people and organizations clear sign-in flows, roles and access boundaries.
EXPLORE THE CAPABILITIES
Customize the workflow
Choose authentication providers, sign-in flows, roles and access policies.
Personalize the experience
Present the account and organization context appropriate to the signed-in person.
Company & work
Give shared work a durable structure.
Connect tasks, responsibilities, planning and operating reviews around shared work.
EXPLORE THE CAPABILITIES
Customize the workflow
Supply durable storage, effect adapters, recurrence rules and planning views.
Personalize the experience
Organize work around the current person’s responsibilities and permitted workspace context.
Knowledge & retrieval
Bring the right source into the answer.
Turn selected material into retrievable context with references and controlled access.
EXPLORE THE CAPABILITIES
Customize the workflow
Select sources, knowledge spaces, access rules and concrete retrieval providers.
Personalize the experience
Resolve the permitted knowledge context for the person, team and task requesting it.
Agents & workflows
Compose tools, context and checkpoints.
Compose assistants and repeatable workflows with defined tools, state and human checkpoints.
EXPLORE THE CAPABILITIES
Customize the workflow
Select tools, models, persistence, workflow steps and human checkpoints.
Personalize the experience
Supply the current goal and approved context to the agent or workflow you compose.
Forms & data
Collect the right input. Carry it forward.
Collect structured input and move data through reviewed mappings and reusable forms.
EXPLORE THE CAPABILITIES
Customize the workflow
Author form schemas, branching rules and mappings; connect storage and delivery.
Personalize the experience
Use explicit form branches and respondent context to show the relevant questions.
Adaptive interfaces
Let the interface fit the task and person.
Adapt views to roles and preferences while keeping shared product contracts.
EXPLORE THE CAPABILITIES
Customize the workflow
Define role variants, layouts and the preferences a product supports.
Personalize the experience
Resolve view, density, data depth and page size from supported preferences; keep access rules separate.
Governance & operations
Keep consequential work reviewable.
Give approvals, deployment plans and operational decisions a clear review trail.
EXPLORE THE CAPABILITIES
Customize the workflow
Bind approval policies, durable review stores and the adapters that execute operations.
Personalize the experience
Compose review views around the decisions and operational responsibilities of each role.
Showing 01Billing & finance↗
SOURCE / LSSM-TECHGitHub ↗
The work continues on GitHub.
The lssm-tech organization is the source home for the technical ecosystem. Use the product guides to understand a boundary, the package directory to find a component, and GitHub to follow the implementation.
THE BUILDING BLOCKS
Explore the guides and packages behind each piece.
Go deeper into the technical areas, inspect the available packages and choose the composition that fits your product.
Open the package directory ↗Domaine de capacité
Core contracts and features
Model one operation and its outcomes
Define the behavior, references and composition rules that other parts of a product can share.
6Packages in this area
Captured source · bcc79fcc
Find your starting pointTasks · package choices · related areas
Questions this area helps answer
- Where should a command, query or event be declared?
- Which package owns portable models and which supplies registries?
- How does a feature connect related contracts?
Model one operation and its outcomes
Why start with these packages
- @lssm-tech/lib.contracts-spec-core
Begin with portable operation, event, capability and feature definitions when authoring a reusable contract.
- @lssm-tech/lib.contracts-spec
Use the compatibility distribution to understand existing consumers and forwarding paths in this source snapshot.
- @lssm-tech/lib.contracts-library
Inspect the maintained documentation, review and platform contract families for complete source examples.
What connects to this area
- Schemas and results
Inputs, outputs and outcomes need explicit models before a handler or transport can validate them.
- Runtime adapters
Registries, handlers and adapters turn declarations into an executed request.
- App composition
Features become useful product capabilities when a host supplies their dependencies.
Domaine de capacité
Schemas, types and results
Define a reusable input/output model
Make input, output, serialization and failure behavior explicit across the boundaries your product exposes.
2Packages in this area
Captured source · bcc79fcc
Find your starting pointTasks · package choices · related areas
Questions this area helps answer
- How do Zod, JSON Schema and GraphQL representations relate?
- Where do standard results and errors live?
- Which types are runtime validation and which are compile-time helpers?
Define a reusable input/output model
Why start with these packages
- @lssm-tech/lib.schema
Use schema models and the existing Zod, JSON Schema, GraphQL and entity surfaces.
- @lssm-tech/lib.contracts-spec-core
Use canonical result and query primitives shared by contracts and adapters.
- @lssm-tech/lib.utils-typescript
Use existing utility types for compile-time transformations without confusing them with runtime validation.
What connects to this area
- Core contracts
A schema becomes meaningful at an operation, event, entity or presentation boundary.
- Runtime adapters
Adapters must preserve the validated input and canonical result semantics.
- Forms and data
Forms and import/export workflows consume these shared schema models.
Domaine de capacité
Handlers, runtimes and transports
Trace an operation from request to handler
Connect declared operations to supplied handlers, client state and the transport your application actually runs.
9Packages in this area
Captured source · bcc79fcc
Find your starting pointTasks · package choices · related areas
Questions this area helps answer
- What belongs in the portable runtime kernel?
- Which adapter matches my REST, GraphQL or MCP host?
- Where are approvals and authenticated context enforced?
Trace an operation from request to handler
Why start with these packages
- @lssm-tech/lib.contracts-runtime-kernel
Start with the framework-neutral engine, canonical registries and caller-supplied runtime ports.
- @lssm-tech/lib.contracts-runtime-server-rest
Inspect the REST adapter matching your framework and its request/context handling.
- @lssm-tech/lib.contracts-runtime-server-mcp
Use the existing contract-to-MCP adapter when exposing a selected operation registry to tools.
- @lssm-tech/lib.contracts-runtime-client-react
Locate the React consumer integration for the shared query/cache runtime.
What connects to this area
- Core contracts
The operation definition fixes the input, outcome and policy the runtime must preserve.
- Schemas and results
Validation and serialization must match at both sides of the request.
- Identity and access
The host constructs trusted request authority.
- Governance and approvals
Required approval evidence belongs in the execution context.
Domaine de capacité
Interfaces, presentations and design
Choose a rendering layer
Compose contract-driven views, role-aware operating surfaces and shared design primitives for web and native hosts.
26Packages in this area
Captured source · bcc79fcc
Find your starting pointTasks · package choices · related areas
Questions this area helps answer
- Do I need a presentation renderer, a design component or a complete surface?
- How are resolved preferences passed into UI?
- Where do role-aware actions and feature hubs belong?
Choose a rendering layer
Why start with these packages
- @lssm-tech/lib.presentation-runtime-core
Use presentation transforms, adaptive defaults and bundler helpers shared across renderers.
- @lssm-tech/lib.presentation-runtime-react
Use the React rendering and workflow-facing presentation layer.
- @lssm-tech/lib.surface-runtime
Inspect surface specs, planners, RoleMorph, feature hubs and React integration.
- @lssm-tech/lib.design-system
Use the shared design-system component surface for product UI composition.
What connects to this area
- Core contracts
Presentation descriptors refer to behavior and data contracts.
- Identity and access
A role-aware view must receive trusted actor and policy context.
- Forms and data
Tables and forms need schema-aware state and validation.
- App composition
The host chooses the design pack, route and available capabilities.
Domaine de capacité
Forms, data views and data exchange
Compose a form respondent and management surface
Collect structured input, present records, and plan governed import/export flows using shared models and explicit host ports.
10Packages in this area
Captured source · bcc79fcc
Find your starting pointTasks · package choices · related areas
Questions this area helps answer
- Which package owns form lifecycle versus form UI?
- How do immutable form publications relate to responses?
- Where can I preview a mapping before applying it?
Compose a form respondent and management surface
Why start with these packages
- @lssm-tech/lib.forms-runtime
Use the canonical caller-port form lifecycle, document compiler and validation helpers.
- @lssm-tech/module.forms
Choose reusable builder, respondent, results and administration composition for the host.
- @lssm-tech/lib.data-exchange-core
Start with codecs, mapping, plans and preview contracts before binding a transport or store.
What connects to this area
- Schemas and results
Form documents and mappings rely on the selected schema model.
- Identity and access
Management and response sessions require distinct trusted scopes.
- Ui and presentations
Renderers display the selected form/data-view state.
- Integrations and providers
Concrete stores, delivery and external data sources implement supplied ports.
Domaine de capacité
Agents, execution and context
Inspect an agent run boundary
Build agent behavior from explicit tools, bounded execution, qualified models and provenance-aware context.
17Packages in this area
Captured source · bcc79fcc
Find your starting pointTasks · package choices · related areas
Questions this area helps answer
- What belongs in AgentProtocol versus the AI Agent runtime?
- How does an agent receive verified context?
- Which host supplies execution, storage and approvals?
Inspect an agent run boundary
Why start with these packages
- @lssm-tech/lib.agent-protocol-spec
Start with wire contracts, runtime capabilities and validation vocabulary shared by agent hosts.
- @lssm-tech/lib.ai-agent
Use the canonical runtime, task-tree, context compiler, approval and tool orchestration surfaces.
- @lssm-tech/lib.context-storage
Locate context-pack/snapshot contracts and in-memory or supplied storage primitives.
- @lssm-tech/lib.harness
Inspect the reusable execution harness and its declared environment boundaries.
What connects to this area
- Core contracts
Tools and agent lifecycle operations need exact contracts.
- Identity and access
Agent principals and delegated subjects must be constructed by a trusted host.
- Knowledge and retrieval
Retrieval supplies evidence that the context compiler can classify and budget.
- Governance and approvals
A plan or model response does not issue its own authority.
Domaine de capacité
Knowledge, retrieval and evidence
Trace ingestion through retrieval
Turn authorized source material into retrievable, cited context while preserving its source, scope and freshness.
3Packages in this area
Captured source · bcc79fcc
Find your starting pointTasks · package choices · related areas
Questions this area helps answer
- What is a knowledge space versus a vector-store collection?
- How does ingestion become usable evidence?
- Which provider and access boundaries does a knowledge host supply?
Trace ingestion through retrieval
Why start with these packages
- @lssm-tech/lib.knowledge
Use ingestion, retrieval, query, access and knowledge-runtime composition primitives.
- @lssm-tech/integration.provider-embedding
Inspect the concrete embedding provider boundary selected by an ingestion host.
- @lssm-tech/integration.provider-vector-store
Inspect the concrete vector-store adapter used by indexing and retrieval.
- @lssm-tech/lib.context-storage
Store the selected pack or snapshot when the caller needs a durable context identity.
What connects to this area
- Schemas and results
Source records, queries and evidence references must keep their declared shapes.
- Identity and access
Knowledge selection must use trusted tenant, actor and purpose context.
- Agents and context
Retrieved content becomes classified input to a bounded agent context.
- Intelligence and research
Research runtimes supply versioned evidence and suppression policy.
Domaine de capacité
Workflows, jobs and automation
Compose an existing workflow
Compose repeatable work with explicit state, persistence, branching and operation-execution responsibilities.
12Packages in this area
Captured source · bcc79fcc
Find your starting pointTasks · package choices · related areas
Questions this area helps answer
- Do I need workflow composition, a scheduler or a product module?
- How are extensions applied without breaking the graph?
- Where are state and effect execution supplied?
Compose an existing workflow
Why start with these packages
- @lssm-tech/lib.workflow-composer
Use the workflow registry, composition/validation and supplied-authority runner surfaces.
- @lssm-tech/module.workflow-orchestration
Inspect reusable boards, DAG/composer views, instance lifecycle and approval composition.
- @lssm-tech/lib.jobs
Inspect the shared job scheduling/execution abstractions used by a host.
- @lssm-tech/lib.sop-runtime
Explore the source runtime for living operating procedures and their generation context.
What connects to this area
- Core contracts
A step refers to a known operation or event, with its declared outcomes.
- Governance and approvals
Branching and planning must preserve the effect authority of each step.
- Agents and context
Agents can propose or perform bounded work inside a declared workflow.
- Delivery and infrastructure
Durable workers and execution environments implement operational concerns.
Domaine de capacité
Identity, access and subject context
Trace authenticated subject construction
Carry trusted actor and tenant context through product requests, agent actions and shared runtime projections.
6Packages in this area
Captured source · bcc79fcc
Find your starting pointTasks · package choices · related areas
Questions this area helps answer
- Which layer authenticates a person and which projects authority?
- How does subject context reach server-rendered UI?
- How do provisioning and delegation remain scoped?
Trace authenticated subject construction
Why start with these packages
- @lssm-tech/lib.authos-spec
Start with the identity, authentication, federation and account-surface contracts.
- @lssm-tech/lib.authos-runtime
Use subject providers, SSR scope and deterministic security/provisioning projections.
- @lssm-tech/integration.authos-better-auth
Inspect the concrete Better Auth integration used by the selected host.
- @lssm-tech/lib.identity-rbac
Locate reusable role and permission composition already used by domain modules.
What connects to this area
- Core contracts
An operation must describe the authority context its host needs.
- Governance and approvals
Identity is one input to a policy or approval decision.
- Ui and presentations
Role-aware presentation consumes resolved subject and policy state.
- Personal and learning
Personal data and delegated household actions need subject-specific scope.
Domaine de capacité
Governance, decisions and approvals
Inspect a digest-bound permit
Resolve policy and review decisions into explicit evidence before consequential work is allowed to proceed.
10Packages in this area
Captured source · bcc79fcc
Find your starting pointTasks · package choices · related areas
Questions this area helps answer
- What is a decision trace versus an execution permit?
- How does Connect bind a decision to the exact work?
- Where do human review and obligations enter the flow?
Inspect a digest-bound permit
Why start with these packages
- @lssm-tech/lib.contractspec-connect
Use the existing packet authority and durable, signed decision boundaries.
- @lssm-tech/lib.decision-runtime
Use deterministic predicates and decision-graph evaluation/conversion.
- @lssm-tech/module.human-review
Inspect reusable human-review composition around governed work.
- @lssm-tech/module.review-queue
Locate review queue, assignment and decision-facing composition.
What connects to this area
- Identity and access
A decision must use trusted actor, scope and current entitlement.
- Core contracts
The proposed action and its required approval must be named precisely.
- Workflows and automation
The selected branch can reference a permitted workflow operation.
- Delivery and infrastructure
Execution verifies the permit against the exact plan and current state.
Domaine de capacité
Communication and notifications
Embed a communication surface
Compose messaging, delivery, channels and notifications around scoped journals and current send authority.
27Packages in this area
Captured source · bcc79fcc
Find your starting pointTasks · package choices · related areas
Questions this area helps answer
- Which layer is the protocol, runtime, reusable UI or host?
- What changes between a message draft and an authorized send?
- How do provider events become durable communication records?
Embed a communication surface
Why start with these packages
- @lssm-tech/lib.communication-spec
Inspect the canonical messaging and governance contracts before selecting a channel.
- @lssm-tech/lib.communication-runtime
Use journal, projection, delivery and authority logic with supplied persistence/provider ports.
- @lssm-tech/module.communication-os
Choose reusable routes, contextual slots and communication UI composition.
- @lssm-tech/integration.communication-channel-core
Inspect the shared concrete channel integration boundary before selecting Discord, email, Slack, SMS or Telegram.
What connects to this area
- Identity and access
Membership, tenant scope and principal identity determine permitted communication.
- Core contracts
Provider events and message actions need stable semantic contracts.
- Company and work
Conversations can create handoffs, support cases and work proposals.
- Integrations and providers
Channel SDKs, credentials and external delivery live in adapters.
Domaine de capacité
Billing, finance and economic evidence
Inspect quote-to-cash state
Model commercial lifecycles, exact money and reviewable financial handoffs with provider and country boundaries kept explicit.
10Packages in this area
Captured source · bcc79fcc
Find your starting pointTasks · package choices · related areas
Questions this area helps answer
- Where do country-neutral billing contracts stop?
- How do billing facts become a FinanceOS handoff?
- Which operations require a concrete adapter and approval?
Inspect quote-to-cash state
Why start with these packages
- @lssm-tech/lib.billing-spec
Begin with country-neutral quote-to-cash contracts, lifecycle evidence and operation descriptions.
- @lssm-tech/lib.billing-runtime
Use deterministic lifecycle projections, supplied persistence ports and economic-truth helpers.
- @lssm-tech/lib.finance-os-runtime
Inspect exact-money, budget, posting and consolidation projections.
- @lssm-tech/lib.billing-france
Inspect the separate France-specific package when a selected composition needs that country layer.
What connects to this area
- Schemas and results
Money, currency, scale and evidence must retain exact representations.
- Governance and approvals
Consequential financial handoffs need current, bound approval.
- Integrations and providers
Payment, invoicing and banking providers supply external effects.
- Observability and testing
Financial evidence must be correlatable without exposing sensitive payloads.
Domaine de capacité
Company, work and service operations
Trace an operating proposal into Work
Connect operating goals, shared work, planning, meetings and support through their canonical domain boundaries.
36Packages in this area
Captured source · bcc79fcc
Find your starting pointTasks · package choices · related areas
Questions this area helps answer
- Which package owns tasks and project state?
- How do CompanyOS projections use shared work?
- How can support and meeting workflows hand off work without copying another domain?
Trace an operating proposal into Work
Why start with these packages
- @lssm-tech/lib.work-runtime
Start with immutable Work events, recurrence, sync conflict handling and durable-store ports.
- @lssm-tech/lib.companyos-runtime
Use CompanyOS authority, operating-loop, graph and outcome projections over shared references.
- @lssm-tech/lib.organization-planning-runtime
Inspect OPA planning/meeting services and their current authority and consent boundaries.
- @lssm-tech/lib.customer-support-runtime
Inspect SupportOS lifecycle, case concurrency, routing and reference-based ecosystem handoffs.
What connects to this area
- Core contracts
Each domain declares the operation and event identity it owns.
- Identity and access
Work and service operations are scoped to the current subject and workspace.
- Communication and notifications
Communication owns message bodies and delivery used by these workflows.
- Forms and data
Forms owns submitted answers and verification evidence.
Domaine de capacité
Intelligence, research and applications
Follow source qualification and revalidation
Manage discovered sources, evidence-backed facts and candidate-authorized application work through explicit lifecycle boundaries.
38Packages in this area
Captured source · bcc79fcc
Find your starting pointTasks · package choices · related areas
Questions this area helps answer
- How do discovered sources become eligible facts?
- What makes a research result traceable?
- Where does a candidate authorize an application effect?
Follow source qualification and revalidation
Why start with these packages
- @lssm-tech/lib.osint-spec
Start with the source, policy and evidence contract vocabulary for OSINT.
- @lssm-tech/lib.osint-runtime
Use source lifecycle, ingestion, qualification and scoped evidence projection logic.
- @lssm-tech/lib.job-application-runtime
Inspect candidate-private lifecycle, headless orchestration and effect-fencing responsibilities.
- @lssm-tech/lib.opportunity-spec
Inspect the opportunity domain’s declared models and references before composing an opportunity workflow.
What connects to this area
- Identity and access
Actor, candidate, purpose and grant scope are inputs to each effect and read.
- Knowledge and retrieval
Searchable knowledge is a derived aid with source/evidence bindings.
- Integrations and providers
Web access, browser, email, storage and transport adapters execute selected external work.
- Company and work
Company and talent workflows consume eligible research through explicit references.
Domaine de capacité
Content, growth and creator operations
Inspect a generated content draft
Move from source-grounded drafts and optimization reports to reviewed publishing, measurement and commercial lifecycle evidence.
30Packages in this area
Captured source · bcc79fcc
Find your starting pointTasks · package choices · related areas
Questions this area helps answer
- Which package drafts content and which can publish it?
- What invalidates an editorial approval?
- How do creator earnings and growth rewards preserve evidence?
Inspect a generated content draft
Why start with these packages
- @lssm-tech/lib.content-gen
Use blog, email, social and marketing draft generators plus optimization reports.
- @lssm-tech/lib.growth-runtime
Inspect referral/reward lifecycle and optional marketing/editorial execution over supplied ports.
- @lssm-tech/lib.creator-operations-runtime
Use creator campaign, agreement, submission and settlement lifecycle composition.
- @lssm-tech/lib.content-analysis-runtime
Inspect content analysis behavior separately from generation and publication.
What connects to this area
- Core contracts
Drafts, observations and publication actions need distinct contracts.
- Governance and approvals
A publishing decision must bind the content actually reviewed.
- Integrations and providers
Social, publishing, advertising and payment adapters own provider-specific effects.
- Billing and finance
Commercial rewards and settlements need exact money and evidence.
Domaine de capacité
Personal workflows, learning and progress
Trace a personal command and receipt
Compose subject-controlled personal workflows and learning experiences with explicit consent, replay and progress semantics.
29Packages in this area
Captured source · bcc79fcc
Find your starting pointTasks · package choices · related areas
Questions this area helps answer
- How is personal authority bound to a command?
- Which runtime owns learning progress or gamification?
- How are private records kept separate from organization views?
Trace a personal command and receipt
Why start with these packages
- @lssm-tech/lib.personal-os-runtime
Use subject-bound authorization, command builders, replay and rights projections.
- @lssm-tech/module.learning-journey
Explore onboarding, drills, coaching and progress adapters.
- @lssm-tech/lib.gamification-runtime
Inspect deterministic campaign, activity, XP, streak and replay behavior.
- @lssm-tech/lib.personal-health-runtime
Inspect strict consent, normalization, sync and evidence boundaries for health-domain data.
What connects to this area
- Identity and access
Personal actions need an exact trusted subject and delegated scope.
- Schemas and results
Progress and personal records must preserve explicit units, time and provenance.
- Forms and data
Personal inputs and consent-bearing records often enter through forms or exchanges.
- Agents and context
Assistive agents receive only the selected, authorized personal context.
Domaine de capacité
Integrations and provider selection
Find a capability-level provider contract
Choose concrete external capabilities through provider-neutral contracts, explicit connections and observable runtime bindings.
60Packages in this area
Captured source · bcc79fcc
Find your starting pointTasks · package choices · related areas
Questions this area helps answer
- Where is the portable interface for a provider capability?
- How do connection credentials differ from runtime mode?
- What makes a provider supported for a particular operation?
Find a capability-level provider contract
Why start with these packages
- @lssm-tech/lib.contracts-integrations
Start with integration specs, connections, secrets, provider interfaces and runtime/health contracts.
- @lssm-tech/lib.provider-spec
Inspect routing, runtime-target, observation, execution-receipt and comparison contracts.
- @lssm-tech/lib.provider-runtime
Use runtime-target, routing and receipt normalization shared by provider hosts.
- @lssm-tech/module.integration-hub
Inspect reusable integration-management composition for a selected product.
What connects to this area
- Core contracts
The consumer needs a declared capability and operation boundary.
- Identity and access
A connection is usable only in its current trusted scope.
- Agents and context
Agent model/tool routes consume explicit provider capabilities.
- Delivery and infrastructure
Execution targets and infrastructure providers have their own operational ports.
Domaine de capacité
Delivery, infrastructure and runtime operations
Trace a desired-state plan
Connect source intent, governed plans and provider execution through exact revisions, receipts and recoverable operational state.
46Packages in this area
Captured source · bcc79fcc
Find your starting pointTasks · package choices · related areas
Questions this area helps answer
- What does LSSM OS planning own and what does a provider execute?
- How are source changes admitted before mutation?
- Which evidence supports deployment or recovery?
Trace a desired-state plan
Why start with these packages
- @lssm-tech/lib.lssm-os-spec
Inspect canonical delivery, runtime and execution contract families.
- @lssm-tech/lib.lssm-os-runtime
Use deterministic planning/execution, authorization verification and injected runtime-node ports.
- @lssm-tech/lib.infra-ops-spec
Start with infrastructure intent, deployment, incident and evidence contracts.
- @lssm-tech/lib.builder-runtime
Inspect source ingestion, readiness, planning and governed patch boundaries.
What connects to this area
- Governance and approvals
Execution uses authority bound to the exact work and current context.
- Observability and testing
Operational claims need source- and environment-bound evidence.
- Integrations and providers
Concrete cloud, queue, state and ingress adapters implement supplied ports.
- App composition
The selected host connects these capabilities into an actual product.
Domaine de capacité
CLI, authoring and agent tooling
Find the owner of a command
Navigate the command host, source analysis, documentation generators and native agent-pack delivery used to work on ContractSpec projects.
36Packages in this area
Captured source · bcc79fcc
Find your starting pointTasks · package choices · related areas
Questions this area helps answer
- Which package owns a CLI command?
- How are optional command packs discovered?
- Where do docs, skills and editor integrations get their context?
Find the owner of a command
Why start with these packages
- @lssm-tech/lib.cli-runtime
Use deterministic command-pack discovery, host ports and canonical workspace analysis/rendering leaves.
- @lssm-tech/app.cli-contractspec
Inspect the actual CLI application that composes commands for users.
- @lssm-tech/agentpacks
Explore pack loading, target-specific configuration, skills and plugin export.
- @lssm-tech/tool.docs-generator
Inspect the Markdown/registry-to-reference-index generation stage.
What connects to this area
- Core contracts
Authoring commands operate on declared specs and their source conventions.
- Agents and context
Coding tools need scoped context and explicit instruction authority.
- Delivery and infrastructure
Source changes and generated artifacts enter existing quality/release workflows.
- Examples and patterns
Command and editor flows should point to maintained examples.
Domaine de capacité
Observability, testing and qualification
Instrument one request path
Follow behavior across boundaries and distinguish declared support from evidence that a selected composition works.
8Packages in this area
Captured source · bcc79fcc
Find your starting pointTasks · package choices · related areas
Questions this area helps answer
- Where do signal declarations differ from telemetry emission?
- How does trace context cross asynchronous boundaries?
- Which test proves the behavior I am claiming?
Instrument one request path
Why start with these packages
- @lssm-tech/lib.observability
Use vendor-neutral instrumentation, signals and evidence-facing surfaces.
- @lssm-tech/lib.observability-spec
Inspect declarative observability contracts before binding a backend.
- @lssm-tech/lib.testing
Locate contract-aware testing utilities, generators, recorders and adapters.
- @lssm-tech/lib.agent-evals
Inspect the agent evaluation package for the selected agent task and environment.
What connects to this area
- Core contracts
Expected input, result and error behavior defines the test boundary.
- Runtime adapters
Instrumentation and assertions must follow the actual handler/transport path.
- Agents and context
Agent evaluations need a bound model, context and tool environment.
- Delivery and infrastructure
Source-bound quality evidence participates in release decisions.
Domaine de capacité
Application composition and product hosts
Trace a product route to its module owner
Assemble reusable modules, runtimes and integrations into an actual product with owned routes, authority and operational dependencies.
15Packages in this area
Captured source · bcc79fcc
Find your starting pointTasks · package choices · related areas
Questions this area helps answer
- What belongs in a module, bundle and app?
- How does LSSM OS compose the reusable pieces?
- Where is the product’s installed capability and journey coverage recorded?
Trace a product route to its module owner
Why start with these packages
- @lssm-tech/bundle.managed-companyos
Inspect shared product composition, feature hubs, shell and experience-coverage surfaces.
- @lssm-tech/bundle.founder-suite
Inspect the selected founder-suite bundle and the product/domain components it composes.
- @lssm-tech/app.web-application-monolith
Locate web routes and host-bound UI/server composition for the integrated application.
- @lssm-tech/app.api-application-monolith
Locate the API host that binds operations to application authority and concrete services.
What connects to this area
- Core contracts
Composition connects exact capabilities, operations and references.
- Runtime adapters
Each host must select and configure an execution/delivery boundary.
- Ui and presentations
Design packs, feature hubs and role-aware views become product UI here.
- Delivery and infrastructure
Providers, workers, secrets and durable state are operational host responsibilities.
Domaine de capacité
Examples and implementation patterns
Follow a minimal operation end to end
Learn from maintained source and fixtures, then adapt the smallest pattern that demonstrates the behavior you need.
91Packages in this area
Captured source · bcc79fcc
Find your starting pointTasks · package choices · related areas
Questions this area helps answer
- Which example teaches my task?
- Is this a source walkthrough, fixture or rich preview?
- What must change when moving the example into my product?
Follow a minimal operation end to end
Why start with these packages
- @lssm-tech/module.examples
Use catalog-only discovery, then load runtime/host ports when a rich preview is needed.
- @lssm-tech/example.minimal
Start with the maintained user-contract source and its small feature/handler structure.
- @lssm-tech/example.data-grid-showcase
Inspect the maintained table showcase and its declared source surfaces.
- @lssm-tech/example.policy-safe-knowledge-assistant
Explore the source pattern for knowledge retrieval combined with policy boundaries.
What connects to this area
- Core contracts
Recognize the contract, handler and adapter responsibilities in an example.
- Runtime adapters
Know which host and execution path the example actually uses.
- Ui and presentations
Table, RoleMorph and other UI examples illuminate rendering boundaries.
- Agents and context
Agent examples need context, provider and tool evidence of their own.
No matching area. Try a broader word, or open the full package directory.
Architecture
Know which layer you need.
Core specifications
The shared description of behavior, schemas and expectations.
Look inside the guideOpening context · complete reading path
The contract describes the behavior
An operation contract names a command or query and describes its data and requirements. The model includes metadata, input and output schemas, result definitions, policy, declared effects, transport hints and links to related presentations or tests.
Work through the guide
- The contract describes the behavior
- The handler performs the work
- The adapter translates an interface
- Follow a change through the layers
4 authored sections; open any section to continue.
Capabilities & composition
Interfaces, agents, integrations and modules that make behavior useful.
Read a little furtherAn opening passage · the reading path
Begin with an operation your product already understands.
Invite a member. Publish a report. Request an approval. Each action has inputs, outcomes, requirements and a reason to exist.
Explore the argument
- Begin with an operation your product already understands.
- Understand the parts you connect.
- Connect the interfaces that need to agree.
- Give each person a useful view of the same product.
- Reuse capabilities without hiding their dependencies.
- Make decisions and consequential changes inspectable.
- Use authoring tools according to their current scope.
- Start with a small, complete evaluation.
Integrated applications
Product experiences assembled from the ecosystem’s pieces.
Voir comment l’intégrerSystem role · useful paths · source context
Its place in the system
The ecosystem-wide infrastructure layer; distinct from any one end-user product.
Choose a next step
The source behind the direction
- Founder clarification of ecosystem-wide roles
28 October 2026: ContractSpec powers the ecosystem; LSSM OS is its infrastructure layer; BrainOS connects the CompanyOS family and almost all products/categories.
A reusable piece comes with a set of relationships.Trace the mechanism · 3 ways to look closer＋
A communication capability might need an operation, a provider port and a policy binding. Explore what happens when one piece is missing.
What is ready in the composition?
UNE SITUATION CONCRÈTE
You can inspect the promise before enabling an effect.
The capability is described, but no active installation or provider has been selected.
01 / Declare
Name the operations, capabilities and required ports.
Ce qui change
The product can discover the capability and its requirements.
Ce qui reste explicite
A declaration alone does not send a message or initialize a provider.
SUIVRE LA CONSÉQUENCE
Use the dependency map to choose what to bind. Do not treat catalogue presence as runtime readiness.
CONTINUE WITH THE DETAIL
Where this explanation comes from
An authored situation, grounded in the linked source guides. Choosing a case explores its expected responsibilities; it does not execute an operation.
Continue from your current codebase.
Adopt in an existing codebase →Use docs in a coding agent →Browse examples →Contribute through the existing project →LSSM.XYZ / THE LIVING ATLASSee the whole.
See the whole.
Follow a connection.
Explore families, projects and the many areas they belong to. Open a real product experience along the way.
Enter the atlas ↗