Vertical Catalog¶
Status: FROZEN — Foundation v1.0
A vertical is a platform-governed business preset, not a Tenant type and not a codebase boundary.
Each Business Unit has exactly one Primary Vertical Preset. Additional compatible capabilities may be enabled subject to compatibility, entitlement and billing rules.
Primary vertical presets¶
| Primary vertical | Representative capability composition |
|---|---|
| Hotel | Accommodation, room inventory, reservations, rates, policies, F&B/events optional as add-on capabilities |
| Spa | Services, staff/resources, appointments, slots, packages, payments |
| Water Park | Admission/ticketing, session capacity, passes, cabanas/add-ons, memberships |
| Villa / Luxury Estate | Accommodation/rental, date-range availability, concierge/add-ons, enquiry/booking |
| Marina | Berths/slips, resource reservations, services, memberships; yacht/excursion capabilities optional |
| Yacht Charter | Asset catalog, scheduled asset availability, crew/captain, charter pricing, add-ons, request/quote/instant modes |
| Vehicle Rental | Fleet assets, quantity/date availability, pickup/return, insurance, extras |
| Vacation Rental | Accommodation units, nightly/date availability, rates, policies |
| Excursions / Group Travel | Group requirements, participant categories, transport, itinerary, capacity, group/tiered/quote pricing |
| Event Management | Leads, requirements, venues/resources, proposals/quotes, milestones, deposits |
| Destination Weddings | Event workflow, venue/packages, guests, vendors, deposits, planning milestones |
| Golf Course | Tee-time slots, player capacity, carts/equipment, memberships, events |
| Restaurant / Beach Club | Tables/seating, reservations, menus, events, cabanas, minimum-spend/deposit options |
The platform team may add future Primary Vertical Presets without changing Tenant semantics.
Composite onboarding templates¶
Some commercial/business categories are better represented as compositions rather than a single operational Business Unit.
Resort¶
A Resort onboarding template may provision/configure combinations such as:
Tenant / Brand
├── Hotel BU
├── Spa BU
├── Restaurant / Beach Club BU
├── Golf Course BU
├── Marina BU
└── Experiences / Excursions BU
The tenant may present these through one Resort brand/site while retaining operationally meaningful Business Unit boundaries.
This distinction prevents a RESORT mega-unit from becoming a special-case architecture.
Yacht schema baseline¶
Typical attributes include length, beam, capacity, cabins, bathrooms, manufacturer/model/year, departure marina, captain/crew inclusion, fuel policy, overnight eligibility and amenities.
Typical resources include yacht, captain, crew and optional tender/water-sports equipment.
Excursion schema baseline¶
Typical attributes include group type, minimum/maximum participants, departure/return points, itinerary, transport requirements, meals, activities, guide requirements, emergency contact/document requirements and accommodation option.
Participant classes may include student, teacher, chaperone, employee, guest and driver, with configurable complimentary ratios.
Capability expansion and billing¶
A Primary Vertical Preset establishes baseline capabilities for the Business Unit. Enabling additional compatible capabilities may alter subscription billing.
The exact price of each capability/module is not part of Foundation v1.0; the invariant is that capability activation is entitlement- and billing-aware.
Vertical governance¶
Tenants may:
- choose an available Primary Vertical Preset;
- enable entitled compatible capabilities;
- configure supported schemas/workflows;
- add supported custom fields.
Tenants may not:
- create arbitrary executable Vertical Definitions;
- bypass compatibility rules;
- enable billable capabilities without the corresponding effective entitlement.
A Custom-plan engagement may commission a new vertical/capability. Once implemented, it is still a platform-governed definition rather than a tenant-specific backend fork.
Future vertical onboarding¶
A new platform-governed vertical should normally be added by defining:
- baseline capability composition;
- offering/resource schemas;
- supported transaction modes;
- pricing/availability defaults;
- workflow presets;
- search/filter definitions;
- recommended Managed Site components/templates;
- import/export mappings;
- optional channel mappings;
- compatible optional capabilities and entitlement/billing metadata.
A new vertical must not require adding tenant.type = <vertical>.