House of Legends — Specification Index
Status: Canonical — this index is the entry point for all specs Last Updated: 2026-05-11 Codebase: Reflects current implementation state
How to Use These Specs
This folder contains authoritative documentation of House of Legends platform. Each spec covers:
| Spec | Content | Audience |
|---|---|---|
| tech-stack | Current technology choices | All developers |
| data-model | Convex schema, all tables | Backend, frontend |
| booking-flow | 4-step booking SPA | Frontend, product |
| public-pages | Landing pages, shows, experiences | Frontend |
| admin-dashboard | Admin panel features | Admin users |
| staff-pos | POS, kitchen, reception | Staff |
| inquiry-forms | Contact, venue rental, workshops | Marketing |
| gamification | Photo wall, challenges, profiles | Product |
| payments | OnePay, payment flow | Backend, finance |
| notifications | Email, WhatsApp, CRM | Backend |
| user-stories | All user actors and journeys | Product, QA |
Quick Links
Getting Started
- Tech Stack — Start here to understand the technology choices
- Data Model — Understand the database schema
Core Features
- Booking Flow — How guests book tickets
- Payments — OnePay integration
- Public Pages — Landing and show pages
Operations
- Admin Dashboard — Admin panel
- Staff POS — Point of sale system
- Notifications — Email, WhatsApp, CRM
Guest Experience
- Inquiry Forms — Contact and quote forms
- Gamification — Photo wall, challenges, reactions
Planning
- User Stories — All actors and use cases
Related Specs Map
tech-stack
├── data-model (schema.ts is the source)
├── booking-flow
├── public-pages
└── admin-dashboard
data-model
├── booking-flow (uses experiences, events, reservations)
├── payments (uses reservations, payments)
├── notifications (uses reservations, notifications)
├── staff-pos (uses tables, orders, menuItems)
├── gamification (uses guestProfiles, challenges)
└── inquiry-forms (uses formSessions)
booking-flow
├── payments (payment integration)
├── notifications (confirmation emails)
├── public-pages (shows are entry points)
└── user-stories (US-B* stories)
public-pages
├── booking-flow (shows link to booking)
├── inquiry-forms (inquiry pages)
└── gamification (wall page)
admin-dashboard
├── staff-pos
├── data-model
├── booking-flow
├── payments (view payment status)
└── notifications
staff-pos
├── data-model (tables, orders, menuItems)
├── gamification (challenges at table)
└── notifications (order alerts)
inquiry-forms
├── notifications (admin alerts)
└── admin-dashboard (kanban view)
gamification
├── data-model (guestProfiles, challenges)
├── staff-pos (challenges at table)
└── public-pages (wall page)
payments
├── data-model (reservations, payments)
├── booking-flow
└── notifications (confirmation)
notifications
├── payments (triggers)
├── booking-flow (confirmation)
└── admin-dashboard (notification center)Deprecation Notice
The following files are deprecated and should not be referenced:
01-foundation.md→ data-model.md02-guest-journey.md→ public-pages.md + booking-flow.md03-admin-backoffice.md→ admin-dashboard.md04-staff-operations.md→ staff-pos.md05-guest-profiles.md→ gamification.md- And all other legacy numbered specs (06-photo-wall.md through 18-booking-flow.md)
Reason: These files describe planned features that have since been implemented with different designs.