System Architecture

The current docs describe a multi-service platform rather than a single monolith. The villa operations modules share business context, the reporting layer consumes external data, and M7 currently sits apart as an internal hardware service.

Architecture Diagram

graph TD
    M1OBV["M1 / OBV\nVilla Onboarding"]
    M2["M2\nMaintenance"]
    M3["M3\nInventory"]
    M4["M4\nReporting"]
    M7["M7\nHardware"]
    SharePoint["SharePoint"]
    Hostify["Hostify"]

    M1OBV -->|"villa context"| M2
    M1OBV -->|"property context"| M3
    M1OBV -->|"listing context"| M4
    M1OBV -->|"documents + photos"| SharePoint
    M2 <-->|"parts / stock context"| M3
    M4 -->|"booking + reservation data"| Hostify
    M7 -. "currently isolated from the villa stack" .- M1OBV

Service Details

M1 - OBV - Villa Onboarding

Purpose: Guided onboarding experience for new villas.

• Focuses on the 11-step onboarding wizard and related admin oversight.
• Collects structured data that becomes the core villa record set used by the wider platform.

M2 - Maintenance

Purpose: Operational maintenance and work order management.

• Tracks work orders, vendors, requests, purchase orders, emergencies, and PMPs.
• Consumes villa and asset context from the broader operations stack.

M3 - Inventory

Purpose: Inventory, consumables, and location tracking.

• Organizes inventory around properties, locations, categories, and stock visibility.
• Closely related to M2 where maintenance work consumes or requests stock.

M4 - Reporting

Purpose: Analytics and reservation reporting.

• Pulls reporting data together for dashboards, tables, and exports.
• Depends on external booking data as well as internal property context.

M7 - Hardware

Purpose: Internal hardware lifecycle management for company equipment.

• Tracks devices, assignments, employees, reports, and audit history.
• Current docs indicate it does not yet integrate with the rest of the villa operations stack.

Architectural Notes

• Each module is documented as its own application surface, with its own operational concerns and data model.
• Cross-service coupling is mostly at the workflow and identifier level rather than by sharing the same tables.
• The documentation set is broader than the originally exposed sidebar structure; M7 and the expanded technical pages are now surfaced alongside the operational docs.

For auth-specific details, continue to Authentication Flow. For the exact integration map, use Service Relationships.