Life & work Across the website family · Useful context · Change it whenever you need.
Find a useful starting point ↗ Change your view Undo
LSSM / Capabilities / CAPABILITY / Direction to develop
Embedded email & inboxes Dedicated workflow email with explicit read, draft and send access. MailPatio demonstrates the model; its mailbox service is not enabled.
A product direction demonstrated in source; the service itself is not established.
Adaptable software ↗ Business operations ↗
View Products & projects Capabilities Architecture Full graph Layout Network Layers Clusters Find an entry in this view Fit view Display & filters Arrange
6 entries · 14 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 1 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 Embedded email & inboxes — Dedicated workflow email with explicit read, draft and send access. MailPatio demonstrates the model; its mailbox service is not enabled. Embedded email & inboxes 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 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 Capabilities ×
Embedded email & inboxes Dedicated workflow email with explicit read, draft and send access. MailPatio demonstrates the model; its mailbox service is not enabled.
capability:embedded-correspondenceA recorded relationship does not grant data access.
recorded relationships 5 All recorded relationshipsSearch relationships ← BrainOS
Context & intelligence from
Declared architecture Evidence foundation:foundation:brainos>capability:embedded-correspondencefoundation
Direction: foundation:brainos → capability:embedded-correspondence
user-foundations-2026-10-28 ← ContractSpec
Powered by
Declared architecture Evidence foundation:foundation:contractspec>capability:embedded-correspondencefoundation
Direction: foundation:contractspec → capability:embedded-correspondence
user-foundations-2026-10-28 ← LSSM OS
Operating infrastructure from
Declared architecture Evidence foundation:foundation:lssm-os>capability:embedded-correspondencefoundation
Direction: foundation:lssm-os → capability:embedded-correspondence
user-foundations-2026-10-28 → MailPatio
Capability direction
Proposed direction Evidence capability:capability:embedded-correspondence>brand:mailpatiocapability
Direction: capability:embedded-correspondence → brand:mailpatio
preview:mailpatio ← Patio
Shared infrastructure & data from
Declared architecture Evidence foundation:family:patio>capability:embedded-correspondencefoundation
Direction: family:patio → capability:embedded-correspondence
Runtime import not verified
user-patio-holding-remit-2026-10-29 Accessible entry list (6) Patio Shared foundations Embedded email & inboxes Capabilities MailPatio Products & experiences ContractSpec Shared foundations LSSM OS Shared foundations BrainOS Shared foundations EXPERIENCES & COVERAGE
Where this work belongs. The note beside each product identifies the scope of this connection.
Direction to develop The inspected website explains and demonstrates the proposed model. Mailbox service and production intake remain disabled.
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 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.
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 dataMailPatio / 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 Reset exampleCurrent 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 The acquired bytes and account-bound source relationship are separate evidence.
Message context email.message
messageIdm-104
threadIdt-29
fromaccounts@example.invalid All fields & provenance5
subjectInvoice INV-42
receivedAt2026-10-28T09:12:00Z Sender, message identity and time stay tied to this mailbox.
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.
Linked contextdocument.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 Deduplication saves one original; it does not combine account permissions.
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 The quotation points to the original and this extraction run.
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 A cited draft is prepared; sending still requires its own content and recipient approval.
Typed handoff MailPatio→ LetterPatiodocument.review-projection.v1 Selected projection availableFields 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.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 / 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 ↗
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.