Service Relationships

While each service has its own scope, the villa operations modules still overlap in important ways. The key distinction is that M1 / OBV owns the onboarding and villa context, M2/M3/M4 consume operational context, and M7 is currently documented as standalone.

Service Dependency Map

graph LR
    M1OBV["M1 / OBV"]
    M2["M2"]
    M3["M3"]
    M4["M4"]
    M7["M7"]
    Hostify["Hostify"]
    SharePoint["SharePoint"]

    M1OBV -->|"uploads"| SharePoint
    M1OBV -->|"villa / owner context"| M2
    M1OBV -->|"property context"| M3
    M1OBV -->|"listing context"| M4
    M2 <-->|"parts / stock context"| M3
    M4 --> Hostify
    M7 -. "no documented runtime dependency" .- M1OBV

Integration Points

M1 / OBV -> Platform Context

Data	Direction	Purpose
Villa profile inputs	M1 / OBV -> platform	Create or complete the villa record
Owner details	M1 / OBV -> platform	Populate owner data
Documents and photos	M1 / OBV -> SharePoint	Preserve onboarding assets and references

M1 / OBV -> M2 (Villa to Maintenance)

Data	Direction	Purpose
Villa ID	M1 / OBV -> M2	Property reference
Villa Name	M1 / OBV -> M2	Display purposes
Villa Address	M1 / OBV -> M2	Location info
Staff	M1 / OBV -> M2	Technician assignment

M1 / OBV -> M3 (Villa to Inventory)

Data	Direction	Purpose
Villa ID	M1 / OBV -> M3	Property reference
Facilities	M1 / OBV -> M3	Initial inventory
Locations	M1 / OBV -> M3	Storage locations

M2 <-> M3 (Maintenance and Inventory)

Data	Direction	Purpose
Parts Request	M2 -> M3	Stock check
Stock Level	M3 -> M2	Availability
Part Usage	M2 -> M3	Stock deduction
Reorder Alert	M3 -> M2	Low stock notification

M1 / OBV -> M4 (Villa to Reporting)

Data	Direction	Purpose
Villa ID	M1 / OBV -> M4	Property matching
Villa Details	M1 / OBV -> M4	Report context

M4 <- Hostify (External)

Data	Direction	Purpose
Listings	Hostify -> M4	Property data
Reservations	Hostify -> M4	Booking data
Revenue	Hostify -> M4	Financial data
Guests	Hostify -> M4	Guest info

M7 (Internal Hardware)

• No runtime dependency on M1 / OBV, M2, M3, or M4 is documented in the recovered content.
• The module currently behaves as its own internal asset system with its own users, assets, and reports.

Shared Reference Data

Property / Villa ID

The main business key across the villa stack is still the property/villa reference:

M1 / OBV villa record -> M2 property context -> M3 property context -> M4 listing/report context

Source of Truth

Data Type	Source
Villa / onboarding data	M1 / OBV
Work orders and maintenance ops	M2
Inventory and stock state	M3
Reporting snapshots and booking analytics	M4
Hardware assets and employee assignments	M7