hotelsfidato-ai/crs

Purpose and Runtime

Fidato is a Phase 1 internal hospitality CRS/ERP frontend for CRM, reservations, hotel inventory/rates, finance, reports, automation, and administration. It is a Vite-served React 19 TypeScript SPA with no backend or authentication; all interactions use deterministic simulated data that resets on refresh. Primary bootstrap and route entry points are src/main.tsx and src/routes.tsx.

Application Shell and Navigation

The routed application is framed by a shared operational shell: sidebar navigation, top bar, role switcher, command palette, and AI panel. This is the principal cross-feature control boundary, including simulated “Viewing as…” role context rather than login.

• src/components/app/AppShell.tsx

• src/components/app/navigation.ts

• src/components/app/RoleSwitcher.tsx

Routing, Access, and Failure States

src/routes.tsx maps the feature pages into the SPA. Authorization is client-side and driven by role/permission rules; forbidden, missing-route, and route-loading/error fallback states are isolated in the shared feature area. This is presentation-level enforcement only until real authentication arrives.

• src/routes.tsx

• src/lib/permissions.ts

• src/features/shared/Forbidden.tsx

Data Boundary: Repositories and Deterministic Mock State

Feature screens should consume the repository layer rather than directly owning persistence behavior. The current repository implementation is an in-memory mock store populated from fixed seed data, creating repeatable review flows and reset-on-refresh semantics. This is the intended Phase 2 swap boundary for Firestore-backed implementations.

• src/data/repositories/index.ts

• src/data/repositories/mock/store.ts

• src/data/seed/index.ts

Core Domain Feature Areas

The UI is organized by business capability, with route-level pages covering the major operating workflows: CRM entities and imports/merges; reservations, calendar, approvals, and booking details; partner hotel profiles, inventory, and rates; and finance invoices, payments, and commissions.

• src/features/crm/CustomersPage.tsx

• src/features/reservations/ReservationsPage.tsx

• src/features/hotels/InventoryPage.tsx

• src/features/finance/InvoicesPage.tsx

Analytics, Automation, AI, and Administration

Dashboard and reporting pages expose operational reporting, including occupancy, revenue, sales, forecast, and hotel views. Separate areas represent automation workflows/runs, simulated AI interactions, notifications/templates, and administrative users, roles, settings, integrations, and audit logs. These are frontend workflows today, not connected service integrations.

• src/features/reports/ReportShell.tsx

• src/features/automation/WorkflowsPage.tsx

• src/features/ai/AiPage.tsx

• src/features/admin/IntegrationsPage.tsx

Shared UI System and Future Infrastructure

A reusable UI layer supplies form controls, tables, filtering, overlays, status indicators, and feedback states; global styling and design tokens live separately. The material runtime stack includes React Router, TanStack Query, Zustand, Radix UI, react-hook-form/Zod, Recharts, Tailwind v4, and Vite. Planned infrastructure—not present in this build—is Firebase (Firestore, Auth, Functions, Storage), followed by n8n automation wiring.

• src/components/ui/index.ts

• src/styles/theme.css

• docs/data-model.md