Tahiyya · prototype · synthetic dataالعربية
TahiyyaتحيةFeature map

Everything in the spec, and where it stands

Each line is one feature from the spec. Tap a feature to open its live screen or its sample screen.

Live287built and working in this prototype (of which partly built: 25)Sample3clickable mock screen; built during the pilotComing soon25on the roadmap; "Coming soon" mock screen
VOICE

AI Voice Agent

Live 23Sample 0Coming soon 2
GUEST

Guest Channels (room phone · TV · QR on the guest's own phone)

Live 23Sample 0Coming soon 5
REQ

Requests & Tickets Engine

Live 13Sample 0Coming soon 0
HK

Housekeeping Operations

Live 16Sample 0Coming soon 1
FO

Front Office & FO Manager Toolkit

Live 21Sample 0Coming soon 1
XC

Cross-department Operations

Live 9Sample 0Coming soon 0
HR

Human Resources & Workforce

Live 28Sample 0Coming soon 2
PTYPE

Hotel-type Editions

Live 8Sample 0Coming soon 1
DASH

Dashboards & Reporting

Live 9Sample 0Coming soon 0
AI

The AI Layer (AI throughout the system)

Live 19Sample 0Coming soon 0
RM

Revenue Support (beside the brand RMS, never replacing it)

Live 5Sample 0Coming soon 3
INT

Integrations (Integration Ladder)

Live 5Sample 1Coming soon 4
ADMIN

Administration

Live 9Sample 0Coming soon 0
PLAT

Platform Foundations

Live 20Sample 1Coming soon 0
ESG

ESG

Live 0Sample 0Coming soon 1
IT

IT

Live 0Sample 0Coming soon 1
MKT

Sales & Marketing (proposed 2026-10-04)

Live 4Sample 1Coming soon 0
GTM

Website, sign-up, plans & free trial (owner 2026-10-06)

Live 17Sample 0Coming soon 0
DOCS

Manuals and training material (owner 2026-10-10)

Live 5Sample 0Coming soon 0
  • DOCS-01Master user manual for hotel clients (AR/EN) with screenshots of every feature; later cut per hotel type and package · cloud 2026-10-12/16: ten chapters written and reviewed against the code for waves 1–3 (EN/AR, docs/06-manuals/user-manual/, ch. 10 HR and recruitment new), served per role by DOCS-04; to do: the screenshots (docs/06-manuals/SCREENSHOTS_NEEDED.md, on the laptop)MVPLive
  • DOCS-02Owner's manual and installation guide (AR/EN) with pictures, including the hardware side (QR cards, tablets, room-phone line, PBX) · cloud 2026-10-12/16: five chapters written and reviewed for waves 1–3 (EN/AR, docs/06-manuals/owners-guide/, new 4.10 reports centre and 5.8 IT notes); to do: the screenshots (on the laptop)MVPLive
  • DOCS-03How-to videos: one per feature group for staff and managers, and an owner's guide video, from the film pipeline (marketing/video) · cloud 2026-10-13: ten scene-by-scene scripts with EN/AR narration in docs/06-manuals/how-to-videos/; to do: filming (on the laptop film pipeline)P2Live
  • DOCS-04Client manual pack per plan, feature and role: the user manual a hotel receives follows its plan, chosen features and hardware; in the app each person sees only the chapters for their role and department; PDF and print copies for the hotel, marked with the client name, "Confidential: licensed to <hotel>" and the date; no internal know-how (prompts, rule sources beyond the published "Why this default", installation playbook)MVPPartly built
  • DOCS-05Tahiyya team onboarding and installation playbook + client intake form (internal, confidential, never given to clients): per client what to set up and customise according to the plan, features and hardware chosen (QR cards, tablets, room-phone line / PBX, TV, Wi-Fi, kiosks, printers), installation steps and checklists, and an intake form the client fills in (Markdown + Word) that drives the configuration and the client manual pack (DOCS-04); IP and trade-secret protectionMVPLive
TEST

TEST

Live 2Sample 0Coming soon 0
  • TEST-01Test mode: testers, role sets and notes on the real screens. In the owner console a co-owner opens a test round (name, demo hotel, optional script UAT-1/2/3) and adds testers, each with a short code or link and a role set: for example tester 1 = GM, front-office manager, housekeeping supervisor; tester 2 = room attendant, runner, technician, kitchen; tester 3 = the guests of rooms 412, 318 and 515. A tester opens the link on any phone, tablet or laptop, picks a role from a bar at the bottom of every screen ("Testing as Noura, HK supervisor ▾") and switches roles without PINs; guest roles open the room's guest page. A floating Note button on every screen opens a short form: kind (bug, confusing, wording, looks wrong, idea, works well), text, optional pin on the screen (tap where it is wrong) and an automatic snapshot of the screen; the app attaches the context itself (address, role, device and viewport, language, app version and commit, the last requests with their status codes, console errors, the script step if one is selected). Notes are stored per round (synthetic demo hotels only) and listed in the owner console with filters and a status (new, fixed in <commit>, by design, cannot reproduce) that testers see too. Export for Claude: pnpm --filter @qsh/api test:export <round> writes qa/uat/rounds/<date>-<round>.md plus the snapshots, in the shape of the Claude run reports, so the next session reads it firstPartly built
  • TEST-02Script steps in the app. The UAT scripts (qa/uat/scripts/UAT-*.md, EN and AR) are read into the round so each tester sees only the steps for their roles, in their language, with the expected result; one tap marks ✅ / ⚠ / ❌ and opens the note form with the step attached; the round's table (the same columns as the Word scripts) is built from the marks, which replaces the printed sign-off table; the co-owner signs the round off in the app (rule 8: owner UAT)Live