Life & work Across the website family · Useful context · Change it whenever you need.
Find a useful starting point ↗ Change your view Undo
LSSM / Areas / Adaptable software / GROUP / Adaptable software
Communication channels & infrastructure Communication workflows, email models and proposed phone, postal and social channel products, with messaging, notifications and live-conversation roles.
View Products & projects Capabilities Architecture Full graph Layout Network Layers Clusters Find an entry in this view Fit view Display & filters Arrange
11 entries · 48 recorded relationships
Neighborhood depth 1 2 Close context × Return to this page
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 & channels 6 Data & intelligence 1 Product & software delivery 2 Shared platforms & governance 2 Patio — 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. Patio Communication channels & infrastructure — Communication workflows, email models and proposed phone, postal and social channel products, with messaging, notifications and live-conversation roles. Communication channels & infrastructure CommunicationOS — 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. C CommunicationOS MailPatio — 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. M MailPatio PhonePatio — Bring calls and carrier messages into the right workflow. PhonePatio is a proposed service for dedicated numbers, application access and accountable routing. PhonePatio LetterPatio — Connect document preparation, review and postal dispatch in one workflow. LetterPatio is a proposed service for correspondence that needs to leave the screen. LetterPatio SocialPatio — Connect account authority, publishing and conversation to the work behind them. SocialPatio is a proposed infrastructure layer for products that operate across social channels. SocialPatio VoicePatio — Connect transcription, spoken responses and conversation turns to your application. VoicePatio is a proposed service for voice experiences with explicit recording and action permissions. VoicePatio ContractSpec — ContractSpec powers the whole LSSM ecosystem through specifications, contracts and reusable capabilities. Its role applies across product families, brands and areas. ContractSpec LSSM 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 OS BrainOS — 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 − 100% +
Drag to pan · Ctrl/⌘ + scroll to zoom
Move map Work groups ×
Communication channels & infrastructure Communication workflows, email models and proposed phone, postal and social channel products, with messaging, notifications and live-conversation roles.
group:software-communicationA recorded relationship does not grant data access.
Accessible entry list (11) Patio Shared foundations Communication channels & infrastructure Work groups CommunicationOS Products & experiences MailPatio Products & experiences PhonePatio Products & experiences LetterPatio Products & experiences SocialPatio Products & experiences VoicePatio Products & experiences ContractSpec Shared foundations LSSM OS Shared foundations BrainOS Shared foundations Projects & experiences
Ways into this work. CommunicationOS Calm Signal
ACTIVE ROOM
Leadership A persisted message
11 Aug 2026, 08:00 UTC Open conversation CommunicationInbox component · source test fixture · hCircle is a product projection of this platform
Product / platform Inspected standalone app and reusable bundle source; no new live verification
Conversations and channels need one clear workspace with explicit boundaries.
Move between authorized conversations, shared rooms and communication work without losing context.
Business operations Contribution & community Adaptable software 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 ↗
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 Every topic52 Mailboxes & identities 8 3 Data 2 Capabilities 3 Integrations Messages & threads 16 5 Data 6 Capabilities 5 Integrations Attachments & originals 8 3 Data 3 Capabilities 2 Integrations Folders, labels & search 13 5 Data 6 Capabilities 2 Integrations Delivery & synchronization 19 6 Data 7 Capabilities 6 Integrations Access & identity review 5 2 Data 2 Capabilities 1 Integrations All 52 Data 24 Capabilities 20 Integrations 8 Processing layer Every layer Connect Transform Reconcile / merge Link Interconnect Observe MailPatio
Browse all items 52 Sort catalog By category A–Z
Data resource ↗ Attachments & originals Attachment metadata Filename, media type, size and content ID describe an attachment without granting its bytes.
Data resource ↗ Attachments & originals Attachment original Original bytes handed to document custody with their source identity.
Data resource ↗ Messages & threads Canonical email A typed message with participants, headers, bodies and attachments.
Data resource ↗ Delivery & synchronization Delivery events Evidence about a requested send and the outcomes reported afterward.
Data resource ↗ Delivery & synchronization Delivery receipt Observed provider acceptance and subsequent message state.
Data resource ↗ Delivery & synchronization Inbound route A domain-bound rule for forwarding incoming correspondence.
Data resource ↗ Attachments & originals Inline content reference An inline MIME part can be related to HTML through its content ID.
Data resource ↗ Folders, labels & search Labels and categories Native label IDs organize messages and threads without changing their contents.
Data resource ↗ Delivery & synchronization Mailbox checkpoint A continuation that records where mailbox synchronization can resume.
Data resource ↗ Mailboxes & identities Mailbox connection One account, its placement and the capabilities granted to it.
Data resource ↗ Folders, labels & search Mailbox folder A folder bounds Microsoft Graph synchronization and its delta cursor.
Data resource ↗ Folders, labels & search Mailbox search query A provider query, page size and continuation token describe a bounded search.
Data resource ↗ Delivery & synchronization Mailbox wake notification A delivery ID and history reference tell a reader to fetch mailbox changes.
Data resource ↗ Messages & threads Messages and drafts The correspondence and prepared replies attached to a specific workflow.
Data resource ↗ Messages & threads MIME parts Separate text, HTML, inline assets and ordinary attachments.
Data resource ↗ Messages & threads Native draft reference Draft, message and thread IDs preserve the provider's editable draft identity.
Data resource ↗ Access & identity review Outbound authority Revocable authority attached to a principal, room and permitted action.
Data resource ↗ Access & identity review Participant identity proposal A proposed relationship between two participant identities, awaiting review.
See the records change. Choose an incoming case and a recipient permission. Inspect the field mapping, the records kept and the exact handoff.
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 case Attachment case Readable original Same bytes, second account Scanned PDF, no extractor Recipient permission Document review in LetterPatio Current result Original → cited fragment → reviewable draft
3 local records1 immutable originals1 source 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
fileNameinvoice-42.txt
contentInvoice INV-42 · EUR 84.00
Due: 2026-11-15
mediaTypetext/plain; charset=utf-8 All fields & provenance7
sourceAccountmailbox:studio-demo
sourceObjectmessage:m-104/attachment:a-1
contentIdentitydemo-content:c41
tenantstudio-demo
Message context email.message
messageIdm-104
threadIdt-29
fromaccounts@example.invalid All fields & provenance5
subjectInvoice INV-42
receivedAt2026-10-28T09:12:00Z
02 Mapping & decisions What changes, what stays separate
01 Mapped
sourceObject + contentIdentitymessage:m-104/attachment:a-1
→ originalReforiginal:invoice-42
Mapping rule Preserve content once; bind every source separately.
02 Retained
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.
03 Mapped
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.
document.citation → correspondence.draftFrom original:invoice-42 To draft-42:v1 Scope studio-demo · document_review 03 Resulting records What this product keeps
Preserved original knowledge.original-document
originalReforiginal:invoice-42
immutabletrue
sourceRelationships1 All fields & provenance5
contentIdentitydemo-content:c41
readabletrue
Exact source citation knowledge.document-citation
quoteInvoice INV-42 · EUR 84.00
Due: 2026-11-15
locationlines:1-2
originalReforiginal:invoice-42 All fields & provenance4
extractionRefextract:utf8:42
Reply draft communication.reply-draft
subjectRe: Invoice INV-42
bodyThank you. I have received invoice INV-42 for EUR 84.00, due 15 November 2026.
sourceCitationcitation-42 All fields & provenance7
draftIddraft-42:v1
contextRefthread:t-29
reviewedfalse
deliveryStatenot_sent
Typed handoff → document.review-projection.v1Fields received
originalReforiginal:invoice-42
citationRefcitation-42
excerptInvoice INV-42 · EUR 84.00
purposedocument_review Remain outside this handoff emailBodyallAttachmentsaccountCredentialsunrelatedDocuments
Only these selected fields cross into the receiving product.
Sample grant demo-grant:mailpatio:letterpatio:document.review-projection.v16 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.
Infrastructure product / Patio Website published · mailbox service in development
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.
Adaptable software Business operations 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 DIRECTION Concept schematic
PhonePatioNumbers. Calls. Messages. A phone channel for products, teams and agents.
↗ THE PLANNED ENTRY POINT A managed phone identity
↗ Calls Voice & routing
≡ Messages SMS, MMS & future RCS
⌘ Events Application & agent handoffs
Concept schematic · service implementation and provider setup to establish.
Infrastructure product / Patio Product concept · phone service not established
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.
Adaptable software Business operations 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 DIRECTION Concept schematic
LetterPatioDocuments. Addresses. Post. Physical correspondence connected to a digital workflow.
↗ THE PLANNED ENTRY POINT A document and its delivery address
↗ Prepare Documents & address checks
≡ Dispatch Print, envelope & post
⌘ Track Delivery events & evidence
Concept schematic · service implementation and provider setup to establish.
Infrastructure product / Patio Product concept · implementation and public destination to establish
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
Adaptable software Business operations Money, billing & finance 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 DIRECTION Concept schematic
SocialPatioPublish. Engage. Understand. Social channel work with explicit identities and platform permissions.
↗ THE PLANNED ENTRY POINT An authorised social account
↗ Publish Posts, media & schedules
≡ Engage Comments & permitted replies
⌘ Understand Listening, signals & measures
Concept schematic · service implementation and provider setup to establish.
Infrastructure product / Patio Product concept · implementation and public destination to establish
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
Adaptable software Business operations Knowledge & growth 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 DIRECTION Concept schematic
VoicePatioListen. Understand. Speak. Speech and voice-agent experiences that can work across channels.
↗ THE PLANNED ENTRY POINT A permitted voice interaction
↗ Listen Audio & transcription
≡ Converse Voice-agent turns & handoffs
⌘ Speak Speech synthesis & playback
Concept schematic · service implementation and provider setup to establish.
Infrastructure product / Patio Product concept · implementation and public destination to establish
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
Adaptable software Business operations Knowledge & growth 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 ↗
Choose your language × Interface language changes text only. Markets, prices and workflows keep their own settings.
English English Original source Français French Partial translation Deutsch German Partial translation Español Spanish Partial translation Italiano Italian Partial translation Português Portuguese Partial translation Polski Polish Partial translation Nederlands Dutch Partial translation Română Romanian Partial translation Čeština Czech Partial translation Ελληνικά Greek Partial translation Magyar Hungarian Partial translation Svenska Swedish Partial translation Dansk Danish Partial translation Suomi Finnish Partial translation العربية Arabic Partial translation हिन्दी Hindi Partial translation 日本語 Japanese Partial translation 한국어 Korean Partial translation Bahasa Indonesia Indonesian Partial translation Português (Brasil) Portuguese (Brazil) Partial translation Português (Portugal) Portuguese (Portugal) Partial translation Español (México) Spanish (Mexico) Partial translation English (India) English (India) Original source
Translation coverage Original source
Navigation 151
Graph 616
Categories 378
Portfolio 833
Examples 2,035
Source preview 1,542
More translations will be added as content is reviewed.
This preference is saved on this browser.