THE TECHNICAL PORTFOLIO

Platforms with
a clear job to do.

Find the application kit, reusable workspace or shared capability that fits the work. Inspect each product through its own components and follow its source.

Communication & connected work

A reusable platform with a standalone application and a public-facing hCircle experience.

Product platform · app & reusable bundle

CommunicationOS

Conversations with clear context and boundaries

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.

StandaloneWeb and PWA application

EmbeddedReusable application kit and contextual slots

Product experiencehCircle 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

EXPLORE THE PRODUCT

CommunicationOSCalm Signal

AUTHORIZED SIGNAL

Communication inbox

Return to the active conversation or move deliberately between rooms.

1 room

ACTIVE ROOM

Leadership

A persisted message

11 Aug 2026, 08:00 UTC

Open conversation

LEADERSHIP · SOURCE FIXTURE

A persisted message

11 Aug 2026, 08:00 UTC

Display-only conversation excerpt. No message is sent.

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

Billing & finance

Commercial quote-to-cash and financial acceptance have distinct responsibilities. Follow their workspaces, contracts and handoff.

Product platform · reusable workspaces

BillingOS

Keep quote-to-cash connected and reviewable

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.

Quote-to-cash lifecycle
Quotes, invoices & payment workspaces
Usage rating & corrections
FinanceOS posting handoffs

Existing source · reusable workspaces and deterministic runtime

Source & current scope

BillingOS has country-neutral core contracts, deterministic runtime and real reusable web UI. The displayed France-SME workspace uses the inspected example fixture. It is not a claim of PA accreditation, connected payment execution or production invoice submission.

Inspect the pinned component source ↗Component provenance & replacement targets ↗

Original billing workspace components · sample content

EXPLORE THE PRODUCT

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 platform · contracts & runtime

FinanceOS

Financial evidence across companies and decisions

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.

Multi-entity planning & consolidation
Exact-money projections & balanced postings
Budgets, commitments & review gates
Cash aging, reporting & adoption template

Existing contracts & runtime · workflow example available

Source & current scope

FinanceOS core is a contract/runtime surface. Consequential banking, tax, payroll and ledger effects remain host-owned governed handoffs. The Finance Ops app-looking preview is explicitly the existing deterministic workflow template with synthetic data; it does not establish a launched FinanceOS application.

Inspect the pinned component source ↗Component provenance & replacement targets ↗

Existing Finance Ops workflow example and source contracts

EXPLORE THE PRODUCT

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

SELECTED DETAIL

INV-1001

ClientAtelier Demo

Amount€18,500

OwnerSales lead

DisputeNo dispute flagged in the synthetic aging row.

Fixture noteHigh amount overdue more than 30 days.

EvidenceConfirm invoice, owner note, due date and client promise before sending anything.

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

EXACT SOURCE EXCERPT

FinanceOS · multi-entity contract

The core is a contract/runtime surface. This is the original synthetic holding-and-companies fixture, not an app screenshot.

export const financeOsFixture = {
	id: 'finance-os-example',
	version: '1.0.0',
	canonicalGoalRefs: [ref('goal:durable-growth', 'lssm_goal')],
	entities: [
		{
			id: 'holding',
			kind: 'holding',
			name: 'Example Holding',
			functionalCurrency: 'EUR',
			jurisdictionRefs: [],
		},
		{
			id: 'company-a',
			kind: 'company',
			name: 'Company A',
			parentEntityRef: ref('holding', 'holding'),
			functionalCurrency: 'EUR',
			jurisdictionRefs: [],
		},
		{
			id: 'company-b',
			kind: 'company',
			name: 'Company B',
			parentEntityRef: ref('holding', 'holding'),
			functionalCurrency: 'EUR',
			jurisdictionRefs: [],
		},
	],
	consolidationScopes: [

Inspect the original source ↗

Exact source excerpt; the continued file defines consolidation, ledgers, budgets, evidence and governed handoffs.

Acquisition & intelligence

Inspect the OSINT operator console and the shared provider layer for web search, extraction, crawling and browser access.

Product platform · console & service hosts

OSINT

External intelligence with traceable evidence

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.

Search & research
Source health & evidence
Job freshness & curation
Acquisition recovery & replay

Existing source · console, API, CLI, MCP and worker

Source & current scope

The requested branch contains deployable OSINT hosts and a reusable operator console. These establish source scope, not a currently launched commercial service. The portfolio display ports the real console styles and master/detail components with local fixtures; no provider calls or live acquisition run here.

Inspect the pinned component source ↗Component provenance & replacement targets ↗

Original operator console components · sample content

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

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

Shared capability · provider support matrix

Web acquisition & scraping

Search, scrape and browse through one layer

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.

Eleven provider adapter families
REST, SDK, MCP, browser & proxy surfaces
Stagehand browser actions & extraction
Explicit support and qualification evidence

Existing shared capability · provider qualification required

Source & current scope

This is a shared capability evidenced by provider-web-access, not an invented standalone company. The visual is an excerpt of its actual support matrix. Provider binding, account access and full live qualification remain distinct from the existence of adapters.

Inspect the pinned component source ↗Component provenance & replacement targets ↗

Actual provider support documentation

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
Provider	REST	TypeScript SDK	Native MCP	Proxy
Bright Data	Yes	@brightdata/sdk	Hosted and local	HTTP, HTTPS, SOCKS
Massive	Yes	Not advertised	Not advertised	Residential HTTP, HTTPS, SOCKS
Browserbase	Yes	@browserbasehq/sdk + Stagehand v4	Hosted and local	Session-managed or custom
Serper	Yes · ten result categories	Not advertised	Not advertised	Not advertised
Linkup	Yes · including x402	linkup-sdk	Hosted and local	Not advertised
Tavily	Yes	@tavily/core	Hosted and local	Not advertised
Direct fetch	Yes	No	ContractSpec projection only	No
Reworkd	Yes	No public client bound	ContractSpec projection only	No
Firecrawl	Yes	REST preferred	Documented, not bound	No
Apify	Yes	REST preferred	Documented, not bound	No
Oxylabs	Yes	No	Local server, not bound	HTTP, HTTPS, SOCKS5/SOCKS5H

Full support and qualification matrix ↗

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

Usage & measurement

Metered usage supplies billing evidence. Product and company metric adapters supply related aggregates. Their boundaries remain explicit.

Shared capability · metering & metrics adapters

Usage & metering

Usage evidence that adds up

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.

Append-only usage ledger
Exact aggregation & superseding corrections
PostHog metering adapters
Read-only company metric aggregates

Existing shared capability · metering and read adapters

Source & current scope

Usage & metering is a shared capability rather than an approved new company. The visual shows its actual TypeScript record interface and source adapter scope, not a fabricated analytics dashboard. Billing evidence and business/product aggregates are kept distinct.

Inspect the pinned component source ↗Component provenance & replacement targets ↗

Actual metering contract and adapter scope

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

Embedded correspondence

Dedicated workflow addresses and explicit application access. The website demonstrates the proposed model; its mailbox service is still in development.

Product direction · website & fictional model

MailPatio

Email inboxes for your app

Embedded email infrastructure for dedicated addresses, workflow-linked messages and explicit application access. Its public website explains the proposed model with a fictional interactive example; live mailbox service and production intake remain disabled.

Dedicated workflow addresses
Read, draft and send permissions
Revocable app access
Interactive correspondence model

Website published · mailbox service in development

Source & current scope

Source main@fcb3ed1dd5485a4e18e7d6db2db28df23e9158f4 records a published public website at www.mailpatio.com. README and release config explicitly keep all mailbox capabilities and production intake disabled. Website UI and fictional demonstration are inspected; no live mailbox service, SDK or product integration is asserted.

Inspect the pinned component source ↗Component provenance & replacement targets ↗

Original website and its fictional correspondence model

EXPLORE THE PRODUCT

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.

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.

Try a different caseAttachment case

Recipient permissionDocument review in LetterPatio

Current resultOriginal → cited fragment → reviewable draft

3local records1immutable originals1source relationships

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.

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.

Linked context

document.citation → correspondence.draft

From: original:invoice-42
To: draft-42:v1
Scope: studio-demo · document_review

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 grant

demo-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.

Gmail message and MIME normalization Immutable document custody and per-source provenance UTF-8 extraction and explicit PDF/OCR ports Original documents, fragments and citations Typed conversation-to-object references Field-scoped authorization before projection

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

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.

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.

Try a different caseAttachment case

Recipient permissionDocument review in LetterPatio

Current resultOriginal → cited fragment → reviewable draft

3local records1immutable originals1source relationships

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.

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.

Linked context

document.citation → correspondence.draft

From: original:invoice-42
To: draft-42:v1
Scope: studio-demo · document_review

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 grant

demo-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.

Composed personal applications

PersonalOS brings planning, agency and wellbeing into a composed application. Its personal experiences retain their own scope.

Composed application · personal workspace

PersonalOS

One calm place for what matters today

The composed personal workspace for Today, goals, wellbeing, household support, review and privacy, with explicit consent, human control and recovery.

Today and personal goals
Wellbeing and household summaries
Weekly review and recovery
Consent and coach controls

Inspected web/mobile/desktop/API composition; local qualification described by source with live-provider and production gates separate

Source & current scope

Inspected web/mobile/desktop/API composition; local qualification described by source with live-provider and production gates separate. 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 PersonalOS shell and Today summary

PersonalOS

One calm place for what matters today.

TODAY

Your day, at a humane pace

Choose one meaningful next action, then adjust without losing progress.

Today plan

Nothing recorded yet.

Habits

PersonalOS source component excerpt · source test fixture · no personal account connected

THE ECOSYSTEM ARCHITECTURE

Distinct roles. Brought together.

BrainOS provides context and intelligence. ContractSpec defines and builds. Patio supplies shared infrastructure and data. LSSM OS composes these layers and operates the environments that use them.

LSSM One owning ecosystem · distinct responsibilities

Context & intelligence

BrainOS

Knowledge, memory and intelligence, available within the right context.

Contracts & build

ContractSpec

Define behaviour, build reusable capabilities and verify the work.

Specialized domain & platform specs

Shared infrastructure & data

Patio

LSSM’s specialized holding for infrastructure, data, transmission and streams. Shared roles across every area.

Infrastructure & data scope

BROUGHT TOGETHER BY

LSSM OS

Composes contracts, intelligence, infrastructure and data. Runs and operates the environments that bring them into use.

RUNTIME & OPERATIONS

Target ecosystem architecture. ContractSpec specializes into domain and platform contracts. The foundation roles come together through LSSM OS; each technical relationship carries its own evidence.

Patio: the specialized infrastructure and data holding within LSSM, with focused product brands. Implementation and availability are recorded per service. Inspect the scope ↗ · Explore the products ↗

CommunicationOS

Leadership

A place for the relationships that make a life.

BillingOS

Quote Desk

Invoice Inbox

Payments & Reconciliation

France Compliance

CompanyOS Review

Quote Desk

Quote · Atelier Lumière

FinanceOS

Aging priorities

INV-1001

INV-1002

INV-1003

INV-1004

INV-1005

INV-1006

FinanceOS · multi-entity contract

OSINT

Intelligence

Acquisition

Governance

Recovery

Self-improvement

Dead letters

France ATS ingestion

Provider health

Evidence

Web acquisition & scraping

Web access provider matrix

Usage & metering

Metered usage, with its evidence

Related company metrics

MailPatio

Inside MailPatio.

Explore by topic

Browse all items 52

See the records change.

Turn an invoice email into a cited reply

Source records

Invoice attachment

Message context

Mapping & decisions

Retain one immutable original

Cite before drafting

Resulting records

Preserved original

Exact source citation

Reply draft

MailPatio→LetterPatio

Fields received

Remain outside this handoff

Inside MailPatio.

Explore by topic

Browse all items 52

See the records change.

Turn an invoice email into a cited reply

Source records

Invoice attachment

Message context

Mapping & decisions

Retain one immutable original

Cite before drafting

Resulting records

Preserved original

Exact source citation

Reply draft

MailPatio→LetterPatio

Fields received

Remain outside this handoff

PersonalOS

Today plan

Habits

BrainOS ↗

ContractSpec ↗

Patio ↗

LSSM OS ↗

MailPatioLetterPatio

MailPatioLetterPatio

BrainOS

ContractSpec

Patio

LSSM OS