Architecture

How the 21-app RBS ecosystem fits together.

The three layers

1. Identity & CRM — Camino

The front door for every user session, every partner app, every CRM activity. OAuth2 + PKCE IdP, multi-tenant org primitives, unified customer timeline. See /apps/camino/.

2. Payments & billing — Colectiva

MXN payment rails, subscriptions, wallets, transfers. Webhook delivery hub for payment events. See /apps/colectiva/.

3. Fiscal — Constanza

CFDI 4.0 stamping, contabilidad electrónica, multi-tenant fiscal operations for Mexican legal entities. Stamps invoices generated anywhere in the ecosystem. See /apps/constanza/.

Integration backbone

• Auth: OAuth2 + PKCE via Camino — see /integration/auth
• Events: 101 typed webhook events — see /integration/events and /reference/events
• Webhook transport: HMAC-SHA256 signed, raw-body signatures, 5-min replay window — see /integration/webhooks
• Idempotency: Idempotency-Key on writes, eventId dedupe on webhooks — see /integration/idempotency
• Errors: RFC 7807 Problem Details + correlationId propagation — see /integration/errors

Tier 1 apps (full public API surface)

Camino, Colectiva, Constanza, Agente

Tier 2 apps (narrow surface)

Caracol, Mancha, Agora, Cookie Monster, Patadas

Other apps (internal or future-public)

Baul, Comal, Cosmos Pet, Garita, Goodbay, La Hoja, Madriguera, Plenura, Puppy Love, Rito, Servilleta, Continua

Their surfaces are not yet public. See /apps/ for the current T1/T2 set.

SDK

One TypeScript SDK unifies all cross-app integration: @r-bsoftware/ecosystem-sdk. See /reference/sdk.

Source of truth

• App registry: ecosystem-sdk/packages/mcp-server/src/registry/apps.json (21 canonical apps)
• Event registry: ecosystem-sdk/packages/mcp-server/src/registry/events.json (101 events)
• SDK source: ecosystem-sdk/packages/sdk/src/