Mesos Lab

Mesos Fabric / The shared foundation

One foundation for connected commerce.

Mesos Fabric coordinates identities, permissions, workflows and service connections across Commerce, Agent and Capital—carrying context from a request to its recorded outcome.

Mesos

commerce

Mesos

agent

Mesos

capital

Shared foundation

Mesos Fabric

Identity · Permissions · Workflow · Connections · Records

↕ supported connections

Merchant toolsExternal
Service providersExternal
Banks & payment providersExternal
Conceptual architecture · solid = Mesos, dashed = external systems

Architecture

Shared capabilities. Connected products.

What it does

Represent people, businesses and institutions, and define permitted access and actions.

Example

A customer allows the partner app's assistant to reserve tables up to an agreed deposit amount.

Reused by

✓ commerce✓ agent✓ capital

Transaction walkthrough · Simulated data

Follow one request across the connected systems.

A reservation at Juniper Room, Fri 2 Oct, 19:00, 4 guests, with a 40,000 ₮ deposit. Booking and payment are separate external operations.

Discover

Retrieve a suitable option and available terms from a connected merchant system.

Sequencing depends on the integration — some providers hold a booking before payment, others authorise payment first.

  1. Customer · partner app
  2. Mesos Agent(active)
  3. Mesos Fabric(active)
  4. Merchant booking systemExternal(active)Not started
  5. Payment providerExternalNot started

Three products

Different experiences. Shared foundations.

Objective

Connect merchant operations with payment records, settlement information and reconciliation.

Fabric capabilities

  • Identity & permissions
  • Service connections
  • Records & visibility

External systems & partners

  • POS and business tools
  • Acquirers and payment providers
  • Merchant's bank

Returned

Orders matched to payment and settlement records

Explore commerce

Shared infrastructure reduces repeated work. Each product still needs its own business rules, integrations and operating arrangements.

Operating model

Clear responsibilities across every connection.

The exact allocation depends on the product and partner agreement. Mesos does not hold funds, act as a custodian or assume partners' compliance obligations by default.

  • Mesos product experience(Mesos)

    Presents information, captures permitted actions, and shows workflow status.

  • Mesos Fabric(Mesos)

    Coordinates supported workflows, permissions, connections and relevant records.

  • Connected providers(external)

    Deliver their services and return the applicable execution results.

  • Banks and payment providers(external)

    Perform their agreed financial-service roles, including applicable payment, account or settlement activities.

  • Business and distribution partners(external)

    Manage their customer relationships and agreed operational responsibilities.

Connecting to Mesos

Start with one useful workflow.

  1. 01

    Define

    Agree the use case, participants, required data and responsibilities.

  2. 02

    Map

    Identify supported interfaces, permissions, provider statuses and exceptions.

  3. 03

    Connect

    Configure the relevant integration and customer experience.

  4. 04

    Validate

    Test approvals, success states, failures and reconciliation.

  5. 05

    Launch & operate

    Activate the agreed scope and monitor outcomes.

Indicative implementation approach — not a promise of existing tooling or a delivery timeline.

Design principles

Designed around permissions, state and traceability.

Permission boundaries

Actions and information access follow the permissions granted.

Explicit state

Proposed, approved, pending, confirmed and failed outcomes remain distinguishable.

Safe recovery

Retries and recovery should account for duplicate requests and uncertain provider outcomes.

Traceable records

Relevant approvals, timestamps, provider references and status changes support review and reconciliation.

Example activity log · fictional data

  1. 18:02:10ProposedDraft reservation · Juniper Room · 4 guests
  2. 18:03:41ApprovedCustomer approved deposit 40,000 ₮
  3. 18:03:43PendingPayment request sent · PAY-7731
  4. 18:03:45ConfirmedPayment approved · PAY-7731
  5. 18:03:46PendingBooking request sent · JR-20417
  6. 18:04:02ConfirmedBooking confirmed · JR-20417

Current status

What is available.

Available to explore

  • — Commerce demo — frontend demonstration with sample data, not a production service
  • — Illustrative walkthroughs on the product pages

Verified integrations

  • — None documented yet

Planned or partner-dependent

  • — Fabric permissions, workflow and records services
  • — MCP tools, API connectors and SDK
  • — Payment, banking, verification and funding services — performed by partners
Open the Commerce demo

Practical questions

Straight answers.

Mesos Fabric

Connect the workflow that matters first.

Explore the merchant experience, or see how the shared foundation supports Agent and Capital.