Skip to main content

​
Hotel Org — Space Surface Overview

​
What Hotel Org Is

Hotels, motels, guesthouses, serviced apartments, and any formal commercial space operator can register as a Leja Organisation with a Business RIN (BRN). Hotel Org is NOT the same as Leja Stay (individual short-let hosting). The distinction is critical: 
LEJA STAY (short-let):
  Individual host. Personal RIN is the host identity.
  Single property or room. No staff management.
  Casual hosting, not a registered business.

HOTEL ORG (Space surface):
  Registered business entity. BRN is the organisational identity.
  Multiple rooms, each with its own Room PIN.
  Staff management (MD, front desk, housekeeping, accounts).
  Organisational accountability, not personal hosting.
  Room Showcase as a dedicated branded surface.

​
Room PIN — Per-Room Identity

Every hotel/motel room gets its own Property Identification Number (PIN). This is a sub-identity nested under the Hotel Property PIN. A Room PIN accumulates:
  • Maintenance history per room
  • Inspection outcomes (periodic condition checks)
  • Guest behavior per stay (damage, cleanliness, disputes)
  • Condition rating across stays
  • Cleaning log compliance
  • Review summaries from witnessed reviews
A Room PIN cannot be reset or hidden. A room with a history of guest damage is visible to future guests. This creates a direct incentive for hotels to maintain rooms well — because their Room PINs are their institutional reputation.

​
Room Showcase

Every Hotel Org gets a Room Showcase — a dedicated branded surface within Leja, distinct from generic listing cards. Room Showcase contains:
  • Hotel branding (name, logo, description, verified BRN status)
  • Per-room entries with interior + exterior photos
  • Room specifications (size, bed type, amenities, floor)
  • Pricing bands and availability calendar
  • Room PIN data (condition, maintenance compliance, review summary)
  • Host response time pattern (from Communication surface data)
Guests browse Room Showcases from the Resident surface (Track 3). Every browse, save, and booking = Track 3 TrendEvent on guest RIN.

​
Check-In / Check-Out Witnessing

Both check-in and check-out are witnessed events in Leja. 
CHECK-IN FLOW:
  1. Guest arrives and hotel confirms check-in on dashboard
  2. Booking payment released from escrow (Payment surface)
  3. TrendEvent created: SHORT_LET_CHECKIN
     → Guest RIN: Track 1 + Track 3 event
     → Room PIN: occupancy event
     → Hotel BRN: hosting event

  Hotel no-show = TrendEvent: HOST_NO_SHOW
  Late check-in = TrendEvent: HOST_LATE_CHECKIN

CHECK-OUT FLOW:
  1. Both parties confirm check-out through their respective surfaces
  2. Hotel submits condition assessment (any damage? deductions?)
  3. Condition assessment logged to Room PIN permanently
  4. Security hold released if no damage claim
  5. Damage claim → hold retained, dispute resolution triggered
  6. TrendEvent created: SHORT_LET_CHECKOUT
     → Guest condition behavior feeds Trust Fingerprint
     → Room condition logged to Room PIN

  Guest damage = TrendEvent: GUEST_DAMAGE_CLAIMED
  Clean exit = TrendEvent: GUEST_CLEAN_EXIT (strong positive signal)

​
Trust Fingerprint Tier Gate

Hotel Org can set a minimum Trust Fingerprint tier for bookings.
  • Hotel sets: “minimum Gold tier for standard rooms”
  • Hotel sets: “minimum Silver tier for budget rooms (accept new users)”
  • AI Dimension G surfaces compatible guests first — not a barrier, an intelligent filter
  • Bronze-tier guests matched with hotels that accept new users
  • Gold/Platinum guests prioritized for premium rooms
This creates a two-sided trust dynamic. The guest’s Trust Fingerprint determines where they can book. The hotel’s Room PIN scores determine which guests want to book there.

​
Hotel Organisation Dashboard

Managing Director sees:
  • Occupancy rate (current, 7-day, 30-day trend)
  • Room PIN scores by floor / room type
  • Guest Trust Fingerprint tier distribution (what tier are our guests?)
  • Revenue tracking (per room, per period)
  • Staff activity log (who checked in whom, when)
  • Anomaly detection (AI Dim D hotel variant):
    • Room with 3+ consecutive damage claims → flagged
    • Guest pattern with frequent disputes → surfaced before acceptance
    • Staff inactivity anomalies

​
Transitional Stay (7+ nights) — Milestone Wave 4

Hotel Org can designate specific rooms for extended stays (7+ nights). Extended stays (7+ nights) generate stronger Trust Graph events — closer to tenancy weight than short-let weight (0.5x per week vs 0.1x per night for short stays). This means:
  • A Resident staying 3 weeks while between tenancies builds Track 1 residential identity data during that stay
  • Bridges the gap between short-let and full tenancy
  • Creates incentive for hotels to offer quality extended stay options

​
Relation Nodes

BRN ↔ Hotel Property PIN
Hotel Property PIN ↔ Room PINs (one per room)
Room PIN ↔ Guest RIN (one relationship per stay)
Hotel BRN ↔ Staff personal RINs (duration of employment)
Room Showcase ↔ Resident surface Track 3
Room PIN ↔ Maintenance Log
Check-in / Check-out ↔ Both Trust Graphs
Hotel BRN ↔ Payment Escrow (booking hold)
Guest Trust Fingerprint → booking acceptance gate (tier check)
Room Showcase ↔ AI Dimension C (advocate matching)
Room PIN ↔ Cleaning log
Hotel Org ↔ AI Dimension D (hotel variant)
Transitional stay ↔ Track 1 TrendEvents
Hotel BRN ↔ Communication surface (guest ↔ hotel thread)

​
Revenue Model

Booking transaction fee: 5% of booking amount
Security hold processing: ₦500 flat per booking
Extended stay fee: 3% of total (lower rate for higher value)
Room Showcase premium listing (Milestone Wave 4): ₦5,000/month per hotel
AI matching premium (Milestone Wave 4): included in Resident Pro

​
Spec Requirements Before Build

The following must be specced before Milestone Wave 3 Hotel Org build begins:
  1. Room PIN creation flow and data model
  2. Room Showcase UI — photo management, availability calendar API
  3. Hotel org dashboard design (separate from standard org dashboard)
  4. Guest trust tier gate implementation in booking flow
  5. Check-in / check-out witnessing atomic DB transaction spec
  6. Hotel-specific TrendEvent types added to TrendEvent enum
  7. Hotel BRN verification requirements (hospitality license per state)
  8. Damage claim and escrow dispute resolution flow
  9. Communication surface thread model for guest ↔ hotel

​
Milestone Wave

Milestone Wave 3 minimum for core Hotel Org. Milestone Wave 4 for transitional stays and full Room Showcase analytics.