How hudson-f-lima/hopeos-v1 works
KortexOS is a beauty-business operations system: staff use its web app to manage appointments and checkout, while the backend exposes authenticated and public booking APIs and persists tenant data. The main operational flow is agenda interaction through shared client state and API calls into backend routes, with scheduling engines supporting availability and Supabase-backed persistence. The README also identifies dashboard and connected records as product capabilities. Several route and UI implementations were not sampled, so those subsystems are shown without speculative internal call chains.
Main entry points: src/app.js HTTP application · js/app.js Operations UI · agenda.js Agenda UI · api.js API client
Components 26
Web application
- Operations UI
js/app.js - Agenda UI
js/ui/agenda.js - Schedule blocks
js/ui/agendaBloqueio.js - Appointment service
js/ui/atendimento.js - Checkout UI
js/ui/checkout.js - Recurring series
js/ui/series.js - Dashboard UI
js/ui/dashboard.js - Client state
js/state.js - API client
js/api.js - Auth storage
js/auth-storage.js
Backend API
- HTTP application
backend/src/app.js - Auth middleware
backend/src/middleware/auth.js - Session routes
backend/src/routes/auth.js - Public booking
backend/src/routes/publicBooking.js - Availability API
backend/src/routes/disponibilidade.js - Operational routes
backend/src/routes/index.js
Operations domain
- Appointment handling
backend/src/engines/AtendimentoEngine.js - Availability rules
backend/src/engines/DisponibilidadeEngine.js - Slot suggestions
backend/src/engines/SlotEngine.js - Schedule rules
backend/src/engines/ScheduleEngine.js
Identity and data
- Identity provider
backend/src/auth/provider.js - Identity store
backend/src/auth/identityStore.js - Tenant repository
backend/src/repositories/SupabaseRepository.js - Supabase database
backend/src/db/supabaseClient.js
Other components
- Staff user
- Online customer
Connections 29
- Staff user → Operations UI: uses
README.md - Operations UI → Agenda UI: renders
js/app.js - Operations UI → Checkout UI: renders
js/app.js - Operations UI → Recurring series: renders
js/app.js - Operations UI → Dashboard UI: renders
js/app.js - Agenda UI → API client: requests
js/ui/agenda.js - Agenda UI → Client state: reads and updates
js/ui/agenda.js - Agenda UI → Schedule blocks: uses
js/ui/agenda.js - Agenda UI → Appointment service: uses
js/ui/agenda.js - Checkout UI → API client: requests
js/ui/checkout.js - Recurring series → API client: requests
js/ui/series.js - Client state → API client: loads data
js/state.js - API client → Auth storage: reads session
js/api.js - HTTP application → Public booking: mounts
backend/src/app.js - HTTP application → Session routes: mounts
backend/src/app.js - HTTP application → Auth middleware: requires authentication
backend/src/app.js - HTTP application → Availability API: mounts
backend/src/app.js - HTTP application → Operational routes: mounts
backend/src/app.js - Auth middleware → Identity provider: authenticates with
backend/src/middleware/auth.js - Auth middleware → Identity store: looks up identity
backend/src/middleware/auth.js - Session routes → Auth middleware: uses
backend/src/routes/auth.js - Session routes → Tenant repository: uses
backend/src/routes/auth.js - Availability rules → Schedule rules: uses
backend/src/engines/DisponibilidadeEngine.js - Slot suggestions → Schedule rules: uses
backend/src/engines/SlotEngine.js - Slot suggestions → Availability rules: computes from
backend/src/engines/SlotEngine.js - Appointment handling → Schedule rules: uses
backend/src/engines/AtendimentoEngine.js - Appointment handling → Slot suggestions: uses
backend/src/engines/AtendimentoEngine.js - Tenant repository → Supabase database: queries
backend/src/repositories/SupabaseRepository.js - Online customer → Public booking: books online