Skip to content

Aashray — Technical Reference

This is the engineering companion to the Aashray Business Logic docs. Where a business-logic file describes what the rules are, its technical counterpart here describes how those rules are actually implemented — exact API routes, database tables/columns, function-level behavior, admin mechanics, and known code-level defects.

Split rule: business-logic files contain no code identifiers, route paths, table/column names, or function names — just plain factual statements of how the system runs. Anything a business stakeholder wouldn't need (routes, schemas, exact SQL/ENUM quirks, implementation bugs) lives here instead, one file per domain, mirroring the business-logic file it pairs with. Every file here links back to its business-logic pair at the top of the page.

Status: every domain is now split. Files 01–10 and 13 each pair one-to-one with a business-logic file of the same number. Files 11, 12, and 99 have no business-logic pairing at all — they're pure staff/engineering reference (an admin-panel page map, a full API route index, and the master discrepancies log) with nothing a business audience needs.

Domain files (paired with business-logic)

File Pairs with
Architecture & Data Model Business Logic — Architecture & Data Model
Accounts, Identity & Auth Business Logic — Accounts, Identity & Auth
Booking Lifecycle & Engine Business Logic — Booking Lifecycle & Engine
Stay — Rooms & Flats Business Logic — Stay: Rooms & Flats
Food Business Logic — Food
Travel Business Logic — Travel
Adhyayan & Utsav Business Logic — Adhyayan & Utsav
Payments, Credits & Reconciliation Business Logic — Payments, Credits & Reconciliation
Services — WiFi, Maintenance, Support, Gate Business Logic — Services
Notifications, Short-links & Config Business Logic — Notifications, Short-links & Config
Status Vocabulary & Scheduled Jobs Business Logic — Status Vocabulary & Automatic Checks

Cross-cutting technical files (no business-logic pairing)

File Covers
Admin Panel Map Every admin module, every page, the backend routes it calls, its RBAC role gate, and its effect on member-side state — the staff-side product, spanning every domain
API Reference Every HTTP route the backend exposes — client, admin, and WiFi — ~250 endpoints, tabled with auth realm and purpose
Discrepancies & Open Questions The master, severity-sorted log of every verified code-level defect found across the audit, aggregating each domain file's own Discrepancies section

How to navigate this set

  • Coming from a business-logic file? Its "For implementation detail…" link at the top always lands you on the matching file here.
  • Looking for a specific route, table, or admin page? Start at API Reference or Admin Panel Map rather than guessing which domain file has it — both are cross-cutting indexes.
  • Triaging bugs? Discrepancies & Open Questions is the rolled-up, severity-ranked view; each domain file's own "Discrepancies" section has the fuller write-up for items specific to that domain.