LSSM.

Adaptable software

Build software that can keep evolving

Copying entire applications makes common behaviour drift. Forcing everyone into one interface loses the context that makes a product useful.

WHAT MAKES IT DIFFICULT
  1. 01

    Keeping shared domain meaning and behaviour consistent across products.

  2. 02

    Reusing components while allowing different language, navigation and visual identities.

  3. 03

    Separating source generation, supported interface adaptation and everyday execution.

  4. 04

    Making the implemented foundations and the intended migration path clear.

CONNECTED ACROSS LSSM

Where this area connects.

Select an entry to explore its neighbours. Move between ownership, specifications, areas, products, data and infrastructure without leaving this page.

17 entries · 91 recorded relationships

Arrow keys navigate entries. Enter selects. Alt + arrows rearranges. F fits the view; Shift + F fits the selection. + and − zoom. Shift + F10 opens actions.

Communication & channels6Finance & commerce3Data & intelligence3Product & software delivery3Shared platforms & governance2Patio — Patio is LSSM’s specialized holding for shared data, infrastructure, transmission and streams. The central Patio brand organizes these responsibilities across every problem area; specialized brands provide focused interfaces into parts of that scope.PatioAdaptable software — Copying entire applications makes common behaviour drift. Forcing everyone into one interface loses the context that makes a product useful.Adaptable softwareContractSpec Studio — A review-first product decision and delivery workspace. ContractSpec Studio connects meetings and product signals to briefs, priorities, issues and approved handoffs, with the evidence and review history kept close to the work.ContractSpec StudioOSINT — A source-backed intelligence and acquisition platform for datasets, companies, jobs and people. Its console connects source health, research, evidence, freshness and recovery; API, CLI, MCP and worker hosts share the same OSINT bundle.OSINTWeb acquisition & scraping — The shared web-access layer routes search, extraction, crawling, research, rendered browser sessions and proxies through explicit provider adapters. Supported surfaces are recorded individually instead of assuming every provider supports every transport.Web acquisition &scrapingBillingOS — Country-neutral billing contracts and reusable workspaces for quotes, invoices, credit notes, payments and reconciliation. Optional France-specific readiness and provider adapters sit around the core, while CompanyOS supplies operator review composition.BillingOSFinanceOS — A finance operations platform for budgets, commitments, cashflow, multi-entity ledgers, consolidation, planning and close. BillingOS owns commercial quote-to-cash; FinanceOS owns the financial acceptance and planning boundary. The source also contains a deterministic Finance Ops workflow template.FinanceOSUsage & metering — Shared metering records feature and operation usage with allocation dimensions, exact quantities, idempotency and superseding corrections. PostHog metering and company-metrics adapters provide related reads; business aggregates remain distinct from the usage evidence that BillingOS rates.Usage & meteringCommunicationOS — A reusable communication application kit with inbox, spaces, rooms, official channel connections, search, meetings, governed work and forms. The same canonical route and authority model supports standalone and embedded hosts.CommunicationOSMailPatio — Give each person, project or process a place for the email that belongs there. Define what your application may read, draft and send while keeping personal correspondence separate.MailPatioPhonePatio — Bring calls and carrier messages into the right workflow. PhonePatio is a proposed service for dedicated numbers, application access and accountable routing.PhonePatioLetterPatio — Connect document preparation, review and postal dispatch in one workflow. LetterPatio is a proposed service for correspondence that needs to leave the screen.LetterPatioSocialPatio — Connect account authority, publishing and conversation to the work behind them. SocialPatio is a proposed infrastructure layer for products that operate across social channels.SocialPatioVoicePatio — Connect transcription, spoken responses and conversation turns to your application. VoicePatio is a proposed service for voice experiences with explicit recording and action permissions.VoicePatioContractSpec — ContractSpec powers the whole LSSM ecosystem through specifications, contracts and reusable capabilities. Its role applies across product families, brands and areas.ContractSpecLSSM OS — LSSM OS is the ecosystem operating layer. It composes and uses BrainOS context and intelligence, ContractSpec specifications and reusable capabilities, and Patio shared infrastructure and data beneath the products and experiences that run on it.LSSM OSBrainOS — BrainOS is the cross-ecosystem context and intelligence layer for personal, company and product knowledge. It connects the Company assistance family and the other products and areas while preserving the boundaries of each context.BrainOS
Accessible entry list (17)
  • Shared foundations
  • Problem areas
  • Products & experiences
  • Products & experiences
  • Products & experiences
  • Products & experiences
  • Products & experiences
  • Products & experiences
  • Products & experiences
  • Products & experiences
  • Products & experiences
  • Products & experiences
  • Products & experiences
  • Products & experiences
  • Shared foundations
  • Shared foundations
  • Shared foundations

01 / WITHIN Adaptable software

Contracts & application foundations

Define behaviour, compose interfaces and evolve the underlying capabilities.

Explore this group

Meeting-to-Execution

Turn meetings and product signals into approved work

Start with one meeting or product signal. Review the work, approve the handoff, and export it into the tools your team already uses.

Source stays attachedReview stays visibleKeep your stack

Marketing component excerpt

Independent projectExisting source · revival requested

ContractSpec Studio

We need to turn meetings, feedback and product evidence into a decision and an approved handoff.

Review a product brief, plan the work, approve the handoff and keep the outcome check connected.

Who it fits & where to start

For Product owners, product managers, product teams, operators and agencies turning signals into reviewed work.

A useful first step Bring a meeting or product signal into a reviewable brief and make the next decision explicit.

Explore ContractSpec Studio

02 / WITHIN Adaptable software

Acquisition & investigation infrastructure

Reusable source acquisition and investigative systems.

Explore this group
SOURCE DOCUMENT · SHARED CAPABILITY

Web access provider matrix

Search, research, extraction, browser sessions and proxies keep their individual provider capabilities.

Recorded adapter support · selected columns from the source matrix
ProviderRESTTypeScript SDKNative MCPProxy
Bright DataYes@brightdata/sdkHosted and localHTTP, HTTPS, SOCKS
MassiveYesNot advertisedNot advertisedResidential HTTP, HTTPS, SOCKS
BrowserbaseYes@browserbasehq/sdk + Stagehand v4Hosted and localSession-managed or custom
SerperYes · ten result categoriesNot advertisedNot advertisedNot advertised
LinkupYes · including x402linkup-sdkHosted and localNot advertised
TavilyYes@tavily/coreHosted and localNot advertised
Direct fetchYesNoContractSpec projection onlyNo
ReworkdYesNo public client boundContractSpec projection onlyNo
FirecrawlYesREST preferredDocumented, not boundNo
ApifyYesREST preferredDocumented, not boundNo
OxylabsYesNoLocal server, not boundHTTP, HTTPS, SOCKS5/SOCKS5H
Full support and qualification matrix ↗

Source documentation excerpt · adapter support is not a claim of completed live qualification

Shared capabilityExisting shared capability · provider qualification required

Web acquisition & scraping

Each search, scraper, browser and proxy provider exposes different methods, limits and evidence.

One governed acquisition layer with explicit provider capabilities and preserved provenance.

Who it fits & where to start

For Builders and operations teams collecting information for research, intelligence and application workflows.

A useful first step One governed acquisition layer with explicit provider capabilities and preserved provenance.

Explore Web acquisition & scraping

OSINT operations and governed improvement

Source health, evidence, freshness, recovery, rights, and qualified improvement effects from one authority-neutral command center.

Intelligence

DatasetsCompaniesJobs and freshnessPeople

Acquisition

Source healthAcquisition activityResearchEvidence

Governance

CurationSubject rights

Recovery

Dead lettersWebhook delivery

Self-improvement

ProgramsSignalsReviews

Dead letters

1 authorized record · source fixture

Partial provider

Some providers are unavailable. Available evidence remains visible and canonical promotion stays server-controlled.

France ATS ingestiondead_lettered

France ATS ingestion

dead_lettered
attempt3
Provider health
direct: readybrowserbase: degraded
Evidence

evidence-1

Actual console component excerpt · source fixture · no acquisition or recovery request is sent

Product / platformExisting source · console, API, CLI, MCP and worker

OSINT

We need to collect outside information, check its freshness, and understand which source supports it.

An inspectable intelligence workspace with source health, provenance, curation and recovery.

Who it fits & where to start

For Research, data and operations teams working with external evidence.

A useful first step An inspectable intelligence workspace with source health, provenance, curation and recovery.

Explore OSINT

03 / WITHIN Adaptable software

Communication channels & infrastructure

Communication workflows, email models and proposed phone, postal and social channel products, with messaging, notifications and live-conversation roles.

Explore this group
CommunicationOSCalm Signal

AUTHORIZED SIGNAL

Communication inbox

Return to the active conversation or move deliberately between rooms.

1 room

ACTIVE ROOM

Leadership

A persisted message

Open conversation

CommunicationInbox component · source test fixture · hCircle is a product projection of this platform

Product / platformInspected standalone app and reusable bundle source; no new live verification

CommunicationOS

Conversations and channels need one clear workspace with explicit boundaries.

Move between authorized conversations, shared rooms and communication work without losing context.

Who it fits & where to start

For People, community hosts, operations teams and builders composing communication experiences.

A useful first step Move between authorized conversations, shared rooms and communication work without losing context.

Explore CommunicationOS
MailPatioOpen the full experience

The Patio atlas

Inside MailPatio.

Choose a topic or browse every data resource, capability and integration. Open an item to see what connects to it.

52items

Explore by topic

MailPatio

Browse all items 52

1–18 of 52 items
Page 1 of 3

The catalog distinguishes upstream building blocks from proposed Patio connections. These are not live account bindings.

Inspect item

The workflow lab

See the records change.

Choose an incoming case and a recipient permission. Inspect the field mapping, the records kept and the exact handoff.

Fictional sample data

MailPatio / Workflow

Turn an invoice email into a cited reply

Keep the original attachment, extract a precise source fragment and prepare a draft tied to its conversation.

Recipient permissionDocument review in LetterPatio
Current resultOriginal → cited fragment → reviewable draft
3local records1immutable originals1source relationships
MailPatio. Readable original. Original → cited fragment → reviewable draft. Selected projection available. 4 Fields received.
01

Source records

What arrived, with its context

Invoice attachment
email.attachment
fileName
invoice-42.txt
content
Invoice INV-42 · EUR 84.00 Due: 2026-11-15
mediaType
text/plain; charset=utf-8
All fields & provenance7
sourceAccount
mailbox:studio-demo
sourceObject
message:m-104/attachment:a-1
contentIdentity
demo-content:c41
tenant
studio-demo

The acquired bytes and account-bound source relationship are separate evidence.

Message context
email.message
messageId
m-104
threadId
t-29
from
accounts@example.invalid
All fields & provenance5
subject
Invoice INV-42
receivedAt
2026-10-28T09:12:00Z

Sender, message identity and time stay tied to this mailbox.

02

Mapping & decisions

What changes, what stays separate

01Mapped
sourceObject + contentIdentitymessage:m-104/attachment:a-1
originalReforiginal:invoice-42
Mapping rule

Preserve content once; bind every source separately.

02Retained
content / lines 1–2Invoice INV-42 · EUR 84.00 Due: 2026-11-15
citation.quoteInvoice INV-42 · EUR 84.00 Due: 2026-11-15
Mapping rule

UTF-8 extraction preserves the exact quotation.

03Mapped
message.threadIdt-29
draft.contextRefthread:t-29
Mapping rule

Only a successful extraction can support a cited draft.

Retain one immutable original
Why this decision?

Content identity is scoped to the tenant. A matching filename would not be enough to deduplicate.

Cite before drafting
Why this decision?

The draft references a specific source fragment rather than presenting extracted text as an original fact without evidence.

03

Resulting records

What this product keeps

Preserved original
knowledge.original-document
originalRef
original:invoice-42
immutable
true
sourceRelationships
1
All fields & provenance5
contentIdentity
demo-content:c41
readable
true

Deduplication saves one original; it does not combine account permissions.

Exact source citation
knowledge.document-citation
quote
Invoice INV-42 · EUR 84.00 Due: 2026-11-15
location
lines:1-2
originalRef
original:invoice-42
All fields & provenance4
extractionRef
extract:utf8:42

The quotation points to the original and this extraction run.

Reply draft
communication.reply-draft
subject
Re: Invoice INV-42
body
Thank you. I have received invoice INV-42 for EUR 84.00, due 15 November 2026.
sourceCitation
citation-42
All fields & provenance7
draftId
draft-42:v1
contextRef
thread:t-29
reviewed
false
deliveryState
not_sent

A cited draft is prepared; sending still requires its own content and recipient approval.

Typed handoff

MailPatioLetterPatio

document.review-projection.v1
Selected projection available
Fields received
originalRef
original:invoice-42
citationRef
citation-42
excerpt
Invoice INV-42 · EUR 84.00
purpose
document_review
Remain outside this handoff
emailBodyallAttachmentsaccountCredentialsunrelatedDocuments

Only these selected fields cross into the receiving product.

Sample grantdemo-grant:mailpatio:letterpatio:document.review-projection.v1
Inspect the rules and source foundations6

One tenant, mailbox and document-review purpose. Draft preparation does not send email.

ContractSpec supplies the cited building blocks. This end-to-end recipe is a proposed Patio composition; its fixture decisions do not run those services.

A local simulation. No account is connected and no message, publication or deployment is sent.

Infrastructure product / PatioWebsite published · mailbox service in development

MailPatio

Our product needs the emails for one workflow without access to the user’s whole personal inbox.

A dedicated correspondence boundary with explicit read, draft and send permissions.

Who it fits & where to start

For Builders of products and agents needing purpose-specific correspondence for job searches, creator collaborations or supplier workflows.

A useful first step A dedicated correspondence boundary with explicit read, draft and send permissions.

Explore MailPatio
PRODUCT DIRECTIONConcept schematic

PhonePatioNumbers. Calls. Messages.

A phone channel for products, teams and agents.

THE PLANNED ENTRY POINTA managed phone identity
CallsVoice & routing
MessagesSMS, MMS & future RCS
EventsApplication & agent handoffs

Concept schematic · service implementation and provider setup to establish.

Infrastructure product / PatioProduct concept · phone service not established

PhonePatio

Our app needs a reachable phone identity and the calls or messages for one workflow, without taking over a person’s whole phone.

A proposed phone boundary for voice calls, SMS, MMS and RCS, with scoped routing, consent and delivery evidence.

Who it fits & where to start

For Product and agent builders, platform teams and operators who need phone numbers, calls and SMS tied to an application or workflow.

A useful first step Choose the workflow that needs a phone identity, then define its routing and allowed actions.

Explore PhonePatio
PRODUCT DIRECTIONConcept schematic

LetterPatioDocuments. Addresses. Post.

Physical correspondence connected to a digital workflow.

THE PLANNED ENTRY POINTA document and its delivery address
PrepareDocuments & address checks
DispatchPrint, envelope & post
TrackDelivery events & evidence

Concept schematic · service implementation and provider setup to establish.

Infrastructure product / PatioProduct concept · implementation and public destination to establish

LetterPatio

A proposed boundary for physical letters, print-and-post workflows and delivery evidence, with formal digital correspondence connected to its own governed services.

Postal correspondence for your workflows

Who it fits & where to start

For Product builders, platform teams and operators who need explicit channel identity, permissions and delivery evidence.

A useful first step Choose a channel purpose, then define identity, consent, authority and the required delivery evidence.

Explore LetterPatio
PRODUCT DIRECTIONConcept schematic

SocialPatioPublish. Engage. Understand.

Social channel work with explicit identities and platform permissions.

THE PLANNED ENTRY POINTAn authorised social account
PublishPosts, media & schedules
EngageComments & permitted replies
UnderstandListening, signals & measures

Concept schematic · service implementation and provider setup to establish.

Infrastructure product / PatioProduct concept · implementation and public destination to establish

SocialPatio

A proposed service boundary for social accounts, publishing, comments, permission-dependent direct messages and evidence-aware listening. Shared source building blocks exist; the branded service remains to establish.

Social channels with clear permissions

Who it fits & where to start

For Product builders, platform teams and operators who need explicit channel identity, permissions and delivery evidence.

A useful first step Choose a channel purpose, then define identity, consent, authority and the required delivery evidence.

Explore SocialPatio
PRODUCT DIRECTIONConcept schematic

VoicePatioListen. Understand. Speak.

Speech and voice-agent experiences that can work across channels.

THE PLANNED ENTRY POINTA permitted voice interaction
ListenAudio & transcription
ConverseVoice-agent turns & handoffs
SpeakSpeech synthesis & playback

Concept schematic · service implementation and provider setup to establish.

Infrastructure product / PatioProduct concept · implementation and public destination to establish

VoicePatio

A proposed experience for transcription, speech generation and voice-agent conversations, composed from bounded shared voice capabilities rather than a phone-number or carrier service.

Speech and voice interaction for your app

Who it fits & where to start

For Product builders, platform teams and operators who need explicit channel identity, permissions and delivery evidence.

A useful first step Choose a channel purpose, then define identity, consent, authority and the required delivery evidence.

Explore VoicePatio

04 / WITHIN Adaptable software

Billing, finance & usage infrastructure

The contracts, runtime capabilities and integration boundaries beneath financial work.

Explore this group

BillingOS France SME

French SME quote-to-cash operations with VAT compliance, e-invoicing readiness, and approval-gated CompanyOS workflows.

◎ Demo company: Atelier Lumière SARL
SIRET 55208131700015VAT FR12345678901Currency EURTax rate 20%
▤↗

Quote Desk

Create and manage quotes with VAT calculations

3 quotes1 pending2 accepted
▧↗

Invoice Inbox

Invoice lifecycle from draft to issued

5 invoices2 draft3 issued
↔↗

Payments & Reconciliation

Track payments and reconcile with invoices

4 payments3 matched1 pending
◇↗

France Compliance

E-invoicing readiness and PA connector checks

2 ready1 blockedSIRET check
✓↗

CompanyOS Review

Approval workflows and operator inbox

3 items2 approved1 pending

Reusable BillingOS components · synthetic France-SME fixture · no live invoice, payment or compliance qualification

Product / platformExisting source · reusable workspaces and deterministic runtime

BillingOS

Quotes, invoices, payments, usage and review decisions need to agree without losing their history.

A reviewable quote-to-cash lifecycle with pricing, usage evidence and explicit FinanceOS handoffs.

Who it fits & where to start

For Business owners, billing operators and product teams managing quote-to-cash workflows.

A useful first step A reviewable quote-to-cash lifecycle with pricing, usage evidence and explicit FinanceOS handoffs.

Explore BillingOS
FINANCE OPS AI WORKFLOWS · SOURCE TEMPLATE

Cash aging

draft ready

Review the synthetic aging snapshot, its owner and supporting evidence.

Total exposure€65,000
Overdue€56,000
Disputed€24,000
Snapshot28 Apr 2026

Aging priorities

INV-1001Atelier Demo · Sales lead€18,500
INV-1002Northwind Sample · Finance manager€24,000
INV-1003Lagoon Demo · Account owner€7,500
INV-1004Cobalt Test · Admin€1,200
INV-1005Blue Sample · Shared mailbox€4,800
INV-1006Recent Demo · Sales€9,000

Actual Finance Ops template components · source synthetic fixture · local selection and review only

Product / platformExisting contracts & runtime · workflow example available

FinanceOS

Budgets, commitments and economic evidence must stay attributable across companies and decisions.

Exact-money financial projections, reviewable plans and governed ledger handoffs.

Who it fits & where to start

For Finance operators, founders and holding or multi-company teams.

A useful first step Exact-money financial projections, reviewable plans and governed ledger handoffs.

Explore FinanceOS
EXACT SOURCE EXCERPT

Metered usage, with its evidence

Exact quantities, allocation dimensions, idempotency and superseding corrections belong to the usage record.

export interface MeteredUsageRecordV1 {
	id: string;
	kind: 'metered_usage_record_v1';
	metricKey: string;
	quantity: EconomicQuantity;
	dimensions: EconomicAllocationDimensionsV1;
	observedAt: string;
	recordedAt: string;
	idempotencyKey: string;
	supersedesRecordId?: string;
	correctionReason?: string;
	evidenceRefIds: string[];
}
Inspect the original source ↗

Related company metrics

The separate read-only adapter layer returns scoped aggregates and evidence from PostHog, Stripe, named PostgreSQL queries, GitHub, Linear, Vercel, Search Console and approved MCP/HTTP/Runtime Node sources.

These business and product aggregates remain distinct from the billable usage ledger.

Inspect company-metrics adapters ↗

Source contract and adapter documentation · no fabricated analytics dashboard or live metrics

Shared capabilityExisting shared capability · metering and read adapters

Usage & metering

Usage records, costs and business metrics should be traceable without treating every analytics event as a billable fact.

Attributable usage records, deterministic aggregation and separately scoped business metrics.

Who it fits & where to start

For Product, finance and platform teams attributing usage and evaluating product or business outcomes.

A useful first step Attributable usage records, deterministic aggregation and separately scoped business metrics.

Explore Usage & metering

Follow a related question.

AN ADJACENT AREABusiness operationsAN ADJACENT AREAWork & careerAN ADJACENT AREAFounder decisions & capacity
Explore the full portfolio

CONNECTED WAYS IN

Continue through Adaptable software.

Follow the work, the person or the product interface. These connections use the same portfolio entries as this area.

Your view

Make room for your context.

Shape the presentation around this moment. You can change it whenever you need.

Your context

The different parts of you

Choose a starting point

A useful mix of context, visuals and gentle guidance.

Tune each dimension
Each dimension can change independently. Product permissions and available actions stay unchanged.

Support the way you begin and return

Tune your support

Reading comfort

Choose your language

Interface language changes text only. Markets, prices and workflows keep their own settings.

Translation coverage

Original source

Navigation151
Graph616
Categories378
Portfolio833
Examples2,035
Source preview1,542

More translations will be added as content is reviewed.

This preference is saved on this browser.

Search the website

Useful starting points

No results. Try a shorter phrase, an operation name or another search area.

A LITTLE ROOM TO EXPLORE

Find something to explore.

Open a closer look on this page, try a different perspective, or follow the detail into its own page.

How previews and controls work
01

Look before you leave

Hover a link or focus it with Tab to see a preview. Clicking the original link or pressing Enter always opens its destination.

02

Stay with the context

Move into the preview to explore its sections. Use Alt + ↓ from a focused link to enter it with the keyboard. Escape closes it.

03

Open the possibilities

Disclosure rows, perspective choices and highlighted controls reveal more. Your view changes reading comfort and the context you explore.

A separate button for a closer look

Show small preview buttons beside links where there is room. Tap the eye to inspect, or tap the link to go straight there. This choice stays in this tab.

No browsing history is collected. Reduced motion follows your device and Your view.