Skip to content

Touriffique Platform Architecture

Foundation status: v1.0 FROZEN
Freeze date: 2026-09-21
Technology gate: I1-B1 through I1-B4 ACCEPTED; I1-B5 next

This documentation defines the target architecture for evolving the legacy Laravel application into a configurable, multi-tenant platform for tourism, hospitality, leisure, rentals, experiences, events, and adjacent service businesses.

The target platform is not a file-for-file rewrite of the legacy application's vertical modules. The legacy application is the behavioral migration baseline; Touriffique generalizes those capabilities into reusable engines, Business Units, platform-governed vertical presets and capabilities.

Foundation v1.0

Product/domain semantics are frozen in Foundation Baseline v1.0.

Technology gate

I1-B1 through I1-B4 are accepted. Authentication uses Keycloak 26.x with OIDC Authorization Code + PKCE; Touriffique owns Users, tenant memberships, permissions, scoped authorization, customers and entitlements. MFA is mandatory for every platform/tenant staff account. The next gate is I1-B5 — Cache, queues, events & background processing.

Platform at a glance

flowchart TB
    U[Visitors / Customers] --> MS[Managed Site App]
    U --> CS[Custom Site - Custom Plan only]
    TA[Tenant Users] --> TC[Tenant Admin App]
    PA[Platform Team] --> PC[Platform Admin App]

    MS --> API[Initial API Runtime]
    CS --> API
    TC --> API
    PC --> API

    API --> PE[Platform Engine]
    API --> CE[Capability Engine]
    API --> CO[Commerce Engine]
    API --> SE[Site Engine]
    API --> CRM[CRM Engine]
    API --> ME[Marketing Engine]
    API --> CH[Channel & Advertising Engine]
    API --> FE[Finance Engine]
    API --> IE[Integration Engine]
    API --> OE[Operations Engine]
    API --> I18N[Internationalization Engine]

Frozen product rules

  1. A Tenant is an organization, not a vertical.
  2. Each Business Unit has exactly one Primary Vertical Preset.
  3. Additional compatible capabilities are entitlement- and billing-aware.
  4. Business Units and Locations are many-to-many.
  5. Customer identity is Tenant-wide; staff visibility can be Business-Unit scoped.
  6. Orders may contain lines from multiple Business Units of the same Tenant.
  7. Yacht Charter and Excursions/Group Travel are first-class launch coverage.
  8. Plan names are Starter, Growth, Pro, Custom.
  9. Starter/Growth/Pro use Managed Site delivery only.
  10. Custom may use Managed, Headless, or hybrid delivery according to contract.
  11. Touriffique monetization is subscription + optional paid modules/capabilities + custom work; no default transaction commission.
  12. Tenants connect their own supported payment-gateway accounts.
  13. Tenants connect their own advertising accounts and providers bill media spend directly.
  14. Internationalization is platform-wide; Tenant Admin is localized and Platform Admin is i18n-ready.
  15. Vertical Definitions are platform-governed rather than tenant-authored executable logic.

Accepted I1-B1 topology

  • core repositories: touriffique-bend, touriffique-fend, touriffique-docs;
  • backend: modular monolith, one API runtime initially, separately deployable workers from the same repository;
  • frontend: Tenant Admin, Platform Admin and Managed Site are separate independently deployable applications within the same frontend workspace;
  • Custom/headless tenant-specific sites live outside the core frontend repository;
  • no separate contracts repository initially.

Reading order

Start with Foundation Baseline v1.0 → Technology Baseline → Architecture Overview → ADRs → Engine specifications.

Technology and implementation documents must conform to the frozen foundation, not redefine it.