Domain Vocabulary¶
Status: FROZEN — Foundation v1.0
| Term | Definition |
|---|---|
| Tenant | The subscribing organization and primary isolation/billing boundary. It is not a business vertical. |
| Brand | A customer-facing brand owned/operated by a tenant. A brand is explicit when present; absence of a Brand record does not create an implicit domain object. |
| Location | A physical or operational location associated with tenant business activity. Locations and Business Units have a many-to-many relationship. |
| Business Unit | An operational subdivision such as a hotel, spa, restaurant, yacht-charter operation, golf course, or excursions operation. Each business unit has exactly one Primary Vertical Preset. |
| Primary Vertical Preset | The one platform-governed vertical preset that establishes the baseline capability/schema/workflow composition of a Business Unit. |
| Vertical Definition | A platform-maintained definition describing recommended capabilities, schemas, workflows and site components for a class of business. Tenants cannot create arbitrary executable Vertical Definitions. |
| Composite Onboarding Template | A platform-maintained onboarding composition that may create/configure multiple Business Units, capabilities, sites or defaults. Resort is a canonical example; it is not required to be one giant operational Business Unit. |
| Capability | A reusable unit of business functionality such as appointments, accommodation inventory, ticketing, quotes, resource scheduling or rentals. |
| Additional Capability | A compatible capability enabled in addition to a Business Unit's primary vertical composition. Enablement is subject to entitlement, compatibility and billing rules. |
| Capability Pack | A curated group of capabilities installed/enabled together. |
| Offering Type | A schema-backed definition of something that can be presented/sold/reserved, such as Room, Yacht Charter, Massage, Tee Time Package or Excursion. |
| Offering | A concrete tenant-owned sellable/reservable item or service. |
| Resource Type | Definition of a schedulable/allocatable resource such as Therapist, Vehicle, Yacht, Treatment Room, Table, Berth, Bus or Guide. |
| Resource | A concrete instance or pool of a resource type. |
| Availability Model | Rules for determining when an offering/resource can be used or booked. |
| Inventory Model | Rules for representing quantity/capacity over a period or slot. |
| Pricing Model | Rules used to construct a price quote. |
| Transaction Mode | High-level customer conversion model: INSTANT_BOOK, REQUEST_TO_BOOK, ENQUIRY_ONLY, QUOTE_REQUIRED, EXTERNAL_BOOKING. |
| Workflow Definition | Allowed states and transitions for a business process. |
| Site | A public digital property owned by a tenant, optionally associated with a brand and one or more business units. |
| Managed Site | Platform-rendered website built using approved site/page components and variants. |
| Custom Site | Separately contracted public frontend under the Custom plan. It may use Managed, Headless, or a hybrid delivery model according to contract. |
| Theme | Site-wide design tokens and visual defaults. |
| Site-level Component | Global/shell component or default used across a site: header, footer, navigation, listing defaults, global search, etc. |
| Page | Routable content/application surface belonging to a site. |
| Section | Ordered page-level composition unit such as hero, slider, gallery, CTA, listing, testimonials or map. |
| Functional Component | Data/action-aware component such as booking, availability, search, tee-time picker or appointment picker. |
| Component Variant | A versioned presentation implementation selectable for a component/section definition. |
| Plan | Commercial product tier: Starter, Growth, Pro, or Custom. |
| Entitlement | Machine-evaluable permission/limit derived from plan, paid modules/capabilities, contract terms and permitted overrides. |
| Paid Module / Capability Add-on | Optional commercial entitlement that extends a subscription. Enabling an additional capability may create this billing effect. |
| Locale | Normalized BCP 47 language/region identifier such as es-DO or en-US. |
| Tenant Locale Set | Locales enabled for a tenant, bounded by plan/contract entitlements. |
| Site Locale Set | Locales enabled for a specific site; must be a subset of tenant-enabled locales. |
| Resolved Locale | Locale selected for a concrete request, communication or rendering operation after deterministic resolution/fallback. |
| Translation | Locale-specific representation of translatable fields attached to a canonical entity or stable system key. |
| Preferred Locale | Explicit customer/user preference used for localized communications and experiences where applicable. |
| Subscription | Tenant's commercial enrollment in a Plan plus its effective paid modules/capabilities and approved contract overrides. |
| Customer | A tenant-wide end-customer identity/profile. The same customer may interact with multiple Business Units of that tenant; staff visibility may be restricted by Business Unit permissions. A person interacting with different tenants has distinct tenant customer records unless a future explicitly designed cross-tenant identity feature says otherwise. |
| Lead | A tenant-scoped customer/prospect interaction that may precede a quote, order or booking. |
| Reservation | A time/capacity/resource allocation or hold. A Reservation represents allocation state and may exist before or after commercial confirmation according to workflow. |
| Booking | The commercial service/reservation commitment for one or more offerings under a defined workflow. A Booking may reference one or more Reservations. |
| Quote | A versioned priced proposal that may be accepted before Booking/Order creation or confirmation. |
| Order | A tenant-scoped commercial aggregate containing one or more Order Lines. Lines may belong to different Business Units of the same Tenant. Orders never span tenants. |
| Payment Account | Tenant-owned/configured account with a supported payment gateway used to process that tenant's customer payments. |
| Advertising Account | Tenant-owned/connected account with a supported advertising provider such as Meta or Google. Provider media spend is billed by that provider to the tenant. |
Organization and commerce relationships¶
Tenant
├── Brand(s)
├── Location(s) ─────────────┐
├── Business Unit(s) │ many-to-many
│ ├── exactly 1 Primary Vertical Preset
│ ├── 0..N Additional Compatible Capabilities
│ ├── Offering(s)
│ └── Resource(s)
├── Site(s)
├── Customer(s) [tenant-wide]
└── Order(s)
└── Order Line(s) -> Business Unit(s)
A business unit may participate in multiple sites. A site may present multiple business units. A business unit may operate at multiple locations, and a location may host multiple business units.