FUNCTIONAL ECOSYSTEM / Communication & collaboration
Move from a conversation to coordinated work.
Conversations, communities and coordinated work span email, phone, postal, social, private-messaging, notification and live-conversation roles. Patio makes channel scope visible without claiming shared providers or universal implementation.
CONNECTED ACROSS LSSM
Shared direction. Many connections.
Select an entry to explore its neighbours. Move between ownership, specifications, areas, products, data and infrastructure without leaving 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.
Drag to pan · Ctrl/⌘ + scroll to zoom
Accessible entry list (13)
Families & ecosystems
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 / There is a useful need and people who might choose to contribute to it.
Fairelio
Useful work, clear commitments, room to choose
Fairelio brings people and organisations around useful work: scoped missions, clear commitments, learning and contribution. Make the need, the terms and the next decision concrete.
03 / Conversations and channels need one clear workspace with explicit boundaries.
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.
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
04 / Our product needs the emails for one workflow without access to the user’s whole personal inbox.
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.
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.
05 / A company and candidate need a relevant introduction with clear evidence, shared interest and control over what is disclosed.
Sarla
The right introduction, with shared intent
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.
Sarla brings together startups and people who have good reasons to work together.
Two ambitionsOne meeting point ↙
&
Your next chapter.
Their team’s project.
What comes next takes two.
Sarla · source landing-page composition
06 / Our app needs a reachable phone identity and the calls or messages for one workflow, without taking over a person’s whole phone.
PhonePatio
Phone identity, calls and messages for your app
A proposed channel product for dedicated numbers, inbound and outbound voice, SMS, MMS and RCS. PhonePatio and TelPatio remain alternative names for this one telephony scope; carrier support and service implementation are to establish.
Concept schematic · service implementation and provider setup to establish.
07 / A proposed boundary for physical letters, print-and-post workflows and delivery evidence, with formal digital correspondence connected to its own governed services.
LetterPatio
Postal correspondence for your workflows
A proposed boundary for physical letters, print-and-post workflows and delivery evidence, with formal digital correspondence connected to its own governed services.
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.
08 / 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.
SocialPatio
Social channels with clear permissions
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 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.
09 / 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.
VoicePatio
Speech and voice interaction for your app
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.
This ecosystem groups products around related outcomes. Each product keeps its own audience, interface and implementation. Follow a capability to inspect the scope and evidence for each connection.
An editorial grouping requested by the founder on 29 October 2026. Membership reflects the recorded product scope; it does not establish common product lineage, legal ownership, a live integration or shared customer data.
Membership groups products by the work they address. Product pages and capability coverage record the inspected implementations, proposed connections and availability separately.
hCircle