Life & work Across the website family · Useful context · Change it whenever you need.
Find a useful starting point ↗ Change your view Undo
LSSM / Portfolio / Infrastructure product / Patio
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.
WHO IT IS FOR Builders of products and agents needing purpose-specific correspondence for job searches, creator collaborations or supplier workflows.
Starting situation Our product needs the emails for one workflow without access to the user’s whole personal inbox. 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.
A WAY INTO THE PRODUCT
Explore the project in practice. A dedicated correspondence boundary with explicit read, draft and send permissions.
EXPLORE THE PRODUCT Landing page Product view
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.
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.
These views use local sample content. Enable JavaScript to switch between product views.
01 MailPatio A dedicated correspondence boundary with explicit read, draft and send permissions.
THE PRODUCT WORKFLOW Capabilities in the inspected project. Each item links to the implementation or source definition that supports its stated scope.
LSSM ACCOUNT / ACROSS PATIO Your account. Patio’s infrastructure and data holding includes focused brands with a shared account direction. Choose the personal or work context that belongs in this experience.
Explore your LSSM account ↗ 01 / WHAT MAY TRAVEL Bring what helps. Your language, reading preferences and chosen work context can make correspondence feel familiar.
See personal & work spaces ↗ 02 / WHAT STAYS SCOPED Keep permissions explicit. Each mailbox keeps its own connection and access rules. Carrying a preference should not expose message history.
See the account boundaries ↗ Account continuity is a design direction. This review connects no account or product data.
View Products & projects Capabilities Architecture Full graph Layout Network Layers Clusters Find an entry in this view Fit view Display & filters Arrange
14 entries · 77 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.
Work & careers 2 Company operations 1 Marketing & creators 1 Communication & channels 6 Data & intelligence 1 Product & software delivery 1 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 Tafio — Tafio is a product in its own right as well as the foundation for a family of focused career experiences. Start with the general career agent, or choose a more specific way into the same work. T Tafio CompanyOS — A general company workspace and adaptable business foundation. Documents, conversations and prepared work come together around the team’s responsibilities, with sources and review visible. C CompanyOS Taketide — Taketide is the UGC platform for creators and brands: a clear brief, a suitable collaboration and content worth sharing. Its marketing and app experiences support creator discovery, campaign work and review. T Taketide 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 Sarla — Sarla connects candidates and employers through relevant, human-reviewed introductions. Its candidate, employer and operator workspaces bring role clarification, career context, evidence-aware matching and explicit approval before anything is shared. S Sarla 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 Products & experiences ×
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.
brand:mailpatioA recorded relationship does not grant data access.
recorded relationships 14 Search relationships ← BrainOS
Context & intelligence from
Declared architecture Evidence foundation:foundation:brainos>brand:mailpatiofoundation
Direction: foundation:brainos → brand:mailpatio
user-foundations-2026-10-28 ← CommunicationOS
Related experience to explore
Editorial relationship Evidence adjacent:brand:communicationos>brand:mailpatioadjacent
Direction: brand:communicationos → brand:mailpatio
portfolio-v20 ← CompanyOS
Related experience to explore
Editorial relationship Evidence adjacent:brand:companyos>brand:mailpatioadjacent
Direction: brand:companyos → brand:mailpatio
portfolio-v20 ← ContractSpec
Powered by
Declared architecture Evidence foundation:foundation:contractspec>brand:mailpatiofoundation
Direction: foundation:contractspec → brand:mailpatio
user-foundations-2026-10-28 ← LetterPatio
Related experience to explore
Proposed direction Evidence adjacent:brand:letterpatio>brand:mailpatioadjacent
Direction: brand:letterpatio → brand:mailpatio
user-patio-scope-2026-10-29 ← LSSM OS
Operating infrastructure from
Declared architecture Evidence foundation:foundation:lssm-os>brand:mailpatiofoundation
Direction: foundation:lssm-os → brand:mailpatio
user-foundations-2026-10-28 ← Patio
Provides services within Patio
Proposed direction Evidence patio-service-provider:family:patio>brand:mailpatiopatio-service-provider
Direction: family:patio → brand:mailpatio
Runtime import not verified
user-patio-holding-remit-2026-10-29 service-source:mailpatio ← Patio
Related to Patio service scope
Proposed direction Evidence patio-service-related:family:patio>brand:mailpatiopatio-service-related
Direction: family:patio → brand:mailpatio
Runtime import not verified
user-patio-holding-remit-2026-10-29 user-phonepatio-2026-10-29 user-patio-scope-2026-10-29 → PhonePatio
Related experience to explore
Proposed direction Evidence adjacent:brand:mailpatio>brand:phonepatioadjacent
Direction: brand:mailpatio → brand:phonepatio
user-phonepatio-2026-10-29 user-patio-scope-2026-10-29 ← Sarla
Related experience to explore
Editorial relationship Evidence adjacent:brand:career-agent>brand:mailpatioadjacent
Direction: brand:career-agent → brand:mailpatio
portfolio-v20 → SocialPatio
Related experience to explore
Proposed direction Evidence adjacent:brand:mailpatio>brand:socialpatioadjacent
Direction: brand:mailpatio → brand:socialpatio
user-patio-scope-2026-10-29 → Tafio
Related experience to explore
Editorial relationship Evidence adjacent:brand:mailpatio>brand:tafioadjacent
Direction: brand:mailpatio → brand:tafio
portfolio-v20 ← Taketide
Related experience to explore
Editorial relationship Evidence adjacent:brand:creator-platform>brand:mailpatioadjacent
Direction: brand:creator-platform → brand:mailpatio
portfolio-v20 → VoicePatio
Related experience to explore
Proposed direction Evidence adjacent:brand:mailpatio>brand:voicepatioadjacent
Direction: brand:mailpatio → brand:voicepatio
user-patio-scope-2026-10-29 Accessible entry list (14) Patio Shared foundations Tafio Products & experiences CompanyOS Products & experiences Taketide Products & experiences CommunicationOS Products & experiences MailPatio Products & experiences Sarla Products & experiences PhonePatio Products & experiences LetterPatio Products & experiences SocialPatio Products & experiences VoicePatio Products & experiences ContractSpec Shared foundations LSSM OS Shared foundations BrainOS Shared foundations HOW IT CONNECTS
Its own purpose. This entry has a distinct purpose within the ecosystem. Its related products and capabilities offer other ways to approach the work.
Explore the problem area ↗ A connection is a route to explore. It does not grant another product access to personal or company information.
Follow MailPatio in the atlas ↗ Brand, domain & source notes 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.
Visuals on this review site reproduce inspected landing-page and app components, with local sample data where needed. Source paths and replacement imports are documented in code comments. A preferred domain or accepted name does not establish a public launch.
Previous source direction: MailPatio / inspected source.
Groups this experience belongs to Capability coverage Each label describes this project’s connection to the capability.
Families and ecosystems Lineage identifies a product foundation; functional ecosystems identify related work.
Shared infrastructure & data This product is a focused experience within the shared infrastructure and data foundation, with its own scope and interface.
Follow the connections ↗ See the product interfaces ↗ Inspect the component source ↗ THE ECOSYSTEM ARCHITECTURE
The architecture around MailPatio. Contracts, intelligence and shared infrastructure and data come together in LSSM OS. Product experiences keep their own purpose and identity.
LSSM ↗ One owning ecosystem · distinct responsibilities 01 / SHARED LANGUAGE ContractSpec Core contracts & behaviour → 02 / SPECIALIZED CONTRACTS Specialized specs Domain & platform responsibilities → 03 / IMPLEMENTATION Platforms & services OS, Patio and product environments Context & intelligence
Personal
↔ Company
Context you choose to connect
Knowledge, memory and intelligence, available within the right context.
Contracts & build
INPUT { email }
→ OPERATION contract
→ RESULT { outcome }
Shared meaning · reusable behavior
Define behaviour, build reusable capabilities and verify the work.
Specialized domain & platform specs ↗ Shared infrastructure & data
Channels Records Signals History Exchange Shared infrastructure & data
LSSM’s specialized holding for infrastructure, data, transmission and streams. Shared roles across every area.
Infrastructure & data scope ↗
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 ↗
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.