# Docs - [Trips Enjoy Documentation](/ar/docs): Business requirements, software requirements, data model and user flows for the Trips Enjoy platform. - Business (BRD) - [Business Requirements](/ar/docs/brd): Context, scope, stakeholders and commercial model of the Trips Enjoy platform. - [Business Requirements & Rules](/ar/docs/brd/requirements): BR-requirements by module and the platform business rules (BRL). - [Compliance, Risks & Decisions](/ar/docs/brd/compliance): Compliance and safety, assumptions, risks, open decisions and approval. - Software (SRS) - [Software Requirements](/ar/docs/srs): Introduction, overall description and external interfaces of the SRS. - Requirements - [AUTH — Accounts, identity and access](/ar/docs/srs/requirements/auth): Functional requirements for Accounts, identity and access (AUTH). - [ONB — Applications and approvals](/ar/docs/srs/requirements/onb): Functional requirements for Applications and approvals (ONB). - [ORG — Organization tenancy and settings](/ar/docs/srs/requirements/org): Functional requirements for Organization tenancy and settings (ORG). - [EMP — Employees and permissions](/ar/docs/srs/requirements/emp): Functional requirements for Employees and permissions (EMP). - [TRIP — Trips](/ar/docs/srs/requirements/trip): Functional requirements for Trips (TRIP). - [PRG — Programs](/ar/docs/srs/requirements/prg): Functional requirements for Programs (PRG). - [FLT — Fleet and vehicle types](/ar/docs/srs/requirements/flt): Functional requirements for Fleet and vehicle types (FLT). - [STF — Staffing](/ar/docs/srs/requirements/stf): Functional requirements for Staffing (STF). - [NEG — Deal negotiation](/ar/docs/srs/requirements/neg): Functional requirements for Deal negotiation (NEG). - [SEAT — Seats](/ar/docs/srs/requirements/seat): Functional requirements for Seats (SEAT). - [BKG — Booking and checkout](/ar/docs/srs/requirements/bkg): Functional requirements for Booking and checkout (BKG). - [PAY — Payments and refunds](/ar/docs/srs/requirements/pay): Functional requirements for Payments and refunds (PAY). - [CPN — Coupons](/ar/docs/srs/requirements/cpn): Functional requirements for Coupons (CPN). - [SUB — Plans and subscriptions](/ar/docs/srs/requirements/sub): Functional requirements for Plans and subscriptions (SUB). - [CHK — Check-in and check-out](/ar/docs/srs/requirements/chk): Functional requirements for Check-in and check-out (CHK). - [MOD — Moderator app](/ar/docs/srs/requirements/mod): Functional requirements for Moderator app (MOD). - [TRK — Live tracking](/ar/docs/srs/requirements/trk): Functional requirements for Live tracking (TRK). - [PAR — Parent tracker](/ar/docs/srs/requirements/par): Functional requirements for Parent tracker (PAR). - [MED — Media and albums](/ar/docs/srs/requirements/med): Functional requirements for Media and albums (MED). - [PHO — Photographer studio](/ar/docs/srs/requirements/pho): Functional requirements for Photographer studio (PHO). - [DRV — Driver app and lab tests](/ar/docs/srs/requirements/drv): Functional requirements for Driver app and lab tests (DRV). - [ADM — Admin console](/ar/docs/srs/requirements/adm): Functional requirements for Admin console (ADM). - [ACC — Accounting and settlements](/ar/docs/srs/requirements/acc): Functional requirements for Accounting and settlements (ACC). - [NTF — Notifications](/ar/docs/srs/requirements/ntf): Functional requirements for Notifications (NTF). - [TRV — Traveler profile and history](/ar/docs/srs/requirements/trv): Functional requirements for Traveler profile and history (TRV). - [MKT — Markets](/ar/docs/srs/requirements/mkt): Functional requirements for Markets (MKT). - [ANL — Analytics](/ar/docs/srs/requirements/anl): Functional requirements for Analytics (ANL). - [API — Public API](/ar/docs/srs/requirements/api): Functional requirements for Public API (API). - [Data Requirements](/ar/docs/srs/data): Core entities, isolation, soft delete and retention. - [State Machines](/ar/docs/srs/state-machines): Trip, booking, seat and deal lifecycles as event/guard transition tables. - [Quality & Interface Requirements](/ar/docs/srs/quality): Non-functional requirements and interface/API requirements. - [Traceability & Open Items](/ar/docs/srs/traceability): BRD→SRS traceability matrix, open items and conflict resolutions. - Data Model (ERD) - [Data Model](/ar/docs/erd): Conventions, domain map and entry points into the entity-relationship design. - Domains - [Lookups and markets](/ar/docs/erd/domains/lookups-and-markets): Tables and relationships for the lookups and markets domain. - [Identity and access](/ar/docs/erd/domains/identity-and-access): Tables and relationships for the identity and access domain. - [Applications](/ar/docs/erd/domains/applications): Tables and relationships for the applications domain. - [Organizations](/ar/docs/erd/domains/organizations): Tables and relationships for the organizations domain. - [Suppliers](/ar/docs/erd/domains/suppliers): Tables and relationships for the suppliers domain. - [Fleet and trips](/ar/docs/erd/domains/fleet-and-trips): Tables and relationships for the fleet and trips domain. - [Deals](/ar/docs/erd/domains/deals): Tables and relationships for the deals domain. - [Booking and payment](/ar/docs/erd/domains/booking-and-payment): Tables and relationships for the booking and payment domain. - [Coupons](/ar/docs/erd/domains/coupons): Tables and relationships for the coupons domain. - [Plans and subscriptions](/ar/docs/erd/domains/plans-and-subscriptions): Tables and relationships for the plans and subscriptions domain. - [Operations](/ar/docs/erd/domains/operations): Tables and relationships for the operations domain. - [Media](/ar/docs/erd/domains/media): Tables and relationships for the media domain. - [Finance](/ar/docs/erd/domains/finance): Tables and relationships for the finance domain. - [Platform](/ar/docs/erd/domains/platform): Tables and relationships for the platform domain. - [Lookup Catalog & Access Paths](/ar/docs/erd/reference): Lookup type catalog, row-level security paths and SRS traceability. - User Flows - [User Flows](/ar/docs/user-flows): How every role registers, gets approved and uses the platform, with rule traces. - [Traveler App](/ar/docs/user-flows/traveler): End-to-end flows for the traveler app (UF IDs, steps, rules). - [Organization Dashboard](/ar/docs/user-flows/organization): End-to-end flows for the organization dashboard (UF IDs, steps, rules). - [Admin Console](/ar/docs/user-flows/admin): End-to-end flows for the admin console (UF IDs, steps, rules). - [Driver App](/ar/docs/user-flows/driver): End-to-end flows for the driver app (UF IDs, steps, rules). - [Photographer Studio](/ar/docs/user-flows/photographer): End-to-end flows for the photographer studio (UF IDs, steps, rules). - [Moderator App](/ar/docs/user-flows/moderator): End-to-end flows for the moderator app (UF IDs, steps, rules). - [Parent Tracker](/ar/docs/user-flows/parent): End-to-end flows for the parent tracker (UF IDs, steps, rules). - [Shared Flows](/ar/docs/user-flows/shared): End-to-end flows for the shared flows (UF IDs, steps, rules). - System Workflows - [System Workflows](/ar/docs/workflows): The engine-executed processes — states, timers, retries and jobs — that run the platform between and during human actions. - [Applications](/ar/docs/workflows/applications): The application workflow — submission, review, changes, appeals and re-application — with its working-day SLAs and closure job. - [Booking & Payment](/ar/docs/workflows/booking-payment): The booking pipeline — seat holds, attempt caps, Fawry vouchers, gateway polling and escalation — from cart to confirmed. - [Refunds](/ar/docs/workflows/refunds): The refund pipeline — policy windows, coupon reversal, gateway retries, finance review and the post-cut-off path. - [Trip Lifecycle](/ar/docs/workflows/trip-lifecycle): The trip state machine — publishing, start-time transitions, remedy windows, change notices and archival. - [Trip Day](/ar/docs/workflows/trip-day): Check-in within 60 seconds, offline queues that retry every 30 seconds, GPS batching, and moderator access that expires with the trip. - [Money](/ar/docs/workflows/money): The settlement pipeline — double-entry ledger, weekly Monday payouts, invoice retries, daily reconciliation and the finance digest. - [Subscriptions](/ar/docs/workflows/subscriptions): The subscription engine — trials, dunning on days 1-3-5-7, the 7-day grace window, scheduled downgrades and monthly counter resets. - [Notifications](/ar/docs/workflows/notifications): The notification pipeline — quiet hours, deferred sends at 07:00, three retries with backoff, event-key dedup and the hourly reminder job. - [Media](/ar/docs/workflows/media): The album pipeline — a 14-day upload window after the trip, resumable batches, four processed variants and archival 30 days later. - [Job Catalog](/ar/docs/workflows/scheduled-jobs): Every timer, queue and scheduled job on the platform, with cadence and rule traces — the operations reference. - [Requirement Coverage](/ar/docs/workflows/coverage): Which user flows and workflows cover each functional requirement — generated, refresh with bun scripts/coverage-matrix.ts. - Delivery Plan - [Delivery Plan](/ar/docs/plan): The end-to-end plan from foundation to scale — phases, generated tasks, milestones and the test strategy, every task traced to a requirement. - [P1 — Foundation](/ar/docs/plan/p1): Delivery tasks for P1: accounts, organization applications and approval, tenancy, generated from the requirement trace. - [P2 — Single-vehicle pilot (Egypt)](/ar/docs/plan/p2): Delivery tasks for P2: trip creation, traveler booking, payment in EGP, admin basics, generated from the requirement trace. - [P3 — Operational depth](/ar/docs/plan/p3): Delivery tasks for P3: multi-vehicle trips, programs, seat modes, moderator app, check-in, generated from the requirement trace. - [P4 — Marketplace supply](/ar/docs/plan/p4): Delivery tasks for P4: platform drivers and photographers, lab tests, negotiation, media, generated from the requirement trace. - [P5 — Monetization and Gulf launch](/ar/docs/plan/p5): Delivery tasks for P5: plans for all roles, feature gates, coupons, full accounting, invoices; Saudi Arabia (SAR) and UAE (AED), generated from the requirement trace. - [P6 — Family and scale](/ar/docs/plan/p6): Delivery tasks for P6: live tracking, parent tracker, analytics, public API, generated from the requirement trace. - [Milestones](/ar/docs/plan/milestones): The phase ladder from foundation to scale — tasks per phase, definitions of done and the open decisions that gate each phase. - [Test Strategy](/ar/docs/plan/testing): How the specification's acceptance criteria, flows and workflows become the test pyramid — from API tests per requirement to time-travel tests for timers. - [For AI Agents](/ar/docs/ai): Machine-readable access: llms.txt, per-page Markdown, search API and an MCP server. # Docs - [Trips Enjoy Documentation](/en/docs): Business requirements, software requirements, data model and user flows for the Trips Enjoy platform. - Business (BRD) - [Business Requirements](/en/docs/brd): Context, scope, stakeholders and commercial model of the Trips Enjoy platform. - [Business Requirements & Rules](/en/docs/brd/requirements): BR-requirements by module and the platform business rules (BRL). - [Compliance, Risks & Decisions](/en/docs/brd/compliance): Compliance and safety, assumptions, risks, open decisions and approval. - Software (SRS) - [Software Requirements](/en/docs/srs): Introduction, overall description and external interfaces of the SRS. - Requirements - [AUTH — Accounts, identity and access](/en/docs/srs/requirements/auth): Functional requirements for Accounts, identity and access (AUTH). - [ONB — Applications and approvals](/en/docs/srs/requirements/onb): Functional requirements for Applications and approvals (ONB). - [ORG — Organization tenancy and settings](/en/docs/srs/requirements/org): Functional requirements for Organization tenancy and settings (ORG). - [EMP — Employees and permissions](/en/docs/srs/requirements/emp): Functional requirements for Employees and permissions (EMP). - [TRIP — Trips](/en/docs/srs/requirements/trip): Functional requirements for Trips (TRIP). - [PRG — Programs](/en/docs/srs/requirements/prg): Functional requirements for Programs (PRG). - [FLT — Fleet and vehicle types](/en/docs/srs/requirements/flt): Functional requirements for Fleet and vehicle types (FLT). - [STF — Staffing](/en/docs/srs/requirements/stf): Functional requirements for Staffing (STF). - [NEG — Deal negotiation](/en/docs/srs/requirements/neg): Functional requirements for Deal negotiation (NEG). - [SEAT — Seats](/en/docs/srs/requirements/seat): Functional requirements for Seats (SEAT). - [BKG — Booking and checkout](/en/docs/srs/requirements/bkg): Functional requirements for Booking and checkout (BKG). - [PAY — Payments and refunds](/en/docs/srs/requirements/pay): Functional requirements for Payments and refunds (PAY). - [CPN — Coupons](/en/docs/srs/requirements/cpn): Functional requirements for Coupons (CPN). - [SUB — Plans and subscriptions](/en/docs/srs/requirements/sub): Functional requirements for Plans and subscriptions (SUB). - [CHK — Check-in and check-out](/en/docs/srs/requirements/chk): Functional requirements for Check-in and check-out (CHK). - [MOD — Moderator app](/en/docs/srs/requirements/mod): Functional requirements for Moderator app (MOD). - [TRK — Live tracking](/en/docs/srs/requirements/trk): Functional requirements for Live tracking (TRK). - [PAR — Parent tracker](/en/docs/srs/requirements/par): Functional requirements for Parent tracker (PAR). - [MED — Media and albums](/en/docs/srs/requirements/med): Functional requirements for Media and albums (MED). - [PHO — Photographer studio](/en/docs/srs/requirements/pho): Functional requirements for Photographer studio (PHO). - [DRV — Driver app and lab tests](/en/docs/srs/requirements/drv): Functional requirements for Driver app and lab tests (DRV). - [ADM — Admin console](/en/docs/srs/requirements/adm): Functional requirements for Admin console (ADM). - [ACC — Accounting and settlements](/en/docs/srs/requirements/acc): Functional requirements for Accounting and settlements (ACC). - [NTF — Notifications](/en/docs/srs/requirements/ntf): Functional requirements for Notifications (NTF). - [TRV — Traveler profile and history](/en/docs/srs/requirements/trv): Functional requirements for Traveler profile and history (TRV). - [MKT — Markets](/en/docs/srs/requirements/mkt): Functional requirements for Markets (MKT). - [ANL — Analytics](/en/docs/srs/requirements/anl): Functional requirements for Analytics (ANL). - [API — Public API](/en/docs/srs/requirements/api): Functional requirements for Public API (API). - [Data Requirements](/en/docs/srs/data): Core entities, isolation, soft delete and retention. - [State Machines](/en/docs/srs/state-machines): Trip, booking, seat and deal lifecycles as event/guard transition tables. - [Quality & Interface Requirements](/en/docs/srs/quality): Non-functional requirements and interface/API requirements. - [Traceability & Open Items](/en/docs/srs/traceability): BRD→SRS traceability matrix, open items and conflict resolutions. - Data Model (ERD) - [Data Model](/en/docs/erd): Conventions, domain map and entry points into the entity-relationship design. - Domains - [Lookups and markets](/en/docs/erd/domains/lookups-and-markets): Tables and relationships for the lookups and markets domain. - [Identity and access](/en/docs/erd/domains/identity-and-access): Tables and relationships for the identity and access domain. - [Applications](/en/docs/erd/domains/applications): Tables and relationships for the applications domain. - [Organizations](/en/docs/erd/domains/organizations): Tables and relationships for the organizations domain. - [Suppliers](/en/docs/erd/domains/suppliers): Tables and relationships for the suppliers domain. - [Fleet and trips](/en/docs/erd/domains/fleet-and-trips): Tables and relationships for the fleet and trips domain. - [Deals](/en/docs/erd/domains/deals): Tables and relationships for the deals domain. - [Booking and payment](/en/docs/erd/domains/booking-and-payment): Tables and relationships for the booking and payment domain. - [Coupons](/en/docs/erd/domains/coupons): Tables and relationships for the coupons domain. - [Plans and subscriptions](/en/docs/erd/domains/plans-and-subscriptions): Tables and relationships for the plans and subscriptions domain. - [Operations](/en/docs/erd/domains/operations): Tables and relationships for the operations domain. - [Media](/en/docs/erd/domains/media): Tables and relationships for the media domain. - [Finance](/en/docs/erd/domains/finance): Tables and relationships for the finance domain. - [Platform](/en/docs/erd/domains/platform): Tables and relationships for the platform domain. - [Lookup Catalog & Access Paths](/en/docs/erd/reference): Lookup type catalog, row-level security paths and SRS traceability. - User Flows - [User Flows](/en/docs/user-flows): How every role registers, gets approved and uses the platform, with rule traces. - [Traveler App](/en/docs/user-flows/traveler): End-to-end flows for the traveler app (UF IDs, steps, rules). - [Organization Dashboard](/en/docs/user-flows/organization): End-to-end flows for the organization dashboard (UF IDs, steps, rules). - [Admin Console](/en/docs/user-flows/admin): End-to-end flows for the admin console (UF IDs, steps, rules). - [Driver App](/en/docs/user-flows/driver): End-to-end flows for the driver app (UF IDs, steps, rules). - [Photographer Studio](/en/docs/user-flows/photographer): End-to-end flows for the photographer studio (UF IDs, steps, rules). - [Moderator App](/en/docs/user-flows/moderator): End-to-end flows for the moderator app (UF IDs, steps, rules). - [Parent Tracker](/en/docs/user-flows/parent): End-to-end flows for the parent tracker (UF IDs, steps, rules). - [Shared Flows](/en/docs/user-flows/shared): End-to-end flows for the shared flows (UF IDs, steps, rules). - System Workflows - [System Workflows](/en/docs/workflows): The engine-executed processes — states, timers, retries and jobs — that run the platform between and during human actions. - [Applications](/en/docs/workflows/applications): The application workflow — submission, review, changes, appeals and re-application — with its working-day SLAs and closure job. - [Booking & Payment](/en/docs/workflows/booking-payment): The booking pipeline — seat holds, attempt caps, Fawry vouchers, gateway polling and escalation — from cart to confirmed. - [Refunds](/en/docs/workflows/refunds): The refund pipeline — policy windows, coupon reversal, gateway retries, finance review and the post-cut-off path. - [Trip Lifecycle](/en/docs/workflows/trip-lifecycle): The trip state machine — publishing, start-time transitions, remedy windows, change notices and archival. - [Trip Day](/en/docs/workflows/trip-day): Check-in within 60 seconds, offline queues that retry every 30 seconds, GPS batching, and moderator access that expires with the trip. - [Money](/en/docs/workflows/money): The settlement pipeline — double-entry ledger, weekly Monday payouts, invoice retries, daily reconciliation and the finance digest. - [Subscriptions](/en/docs/workflows/subscriptions): The subscription engine — trials, dunning on days 1-3-5-7, the 7-day grace window, scheduled downgrades and monthly counter resets. - [Notifications](/en/docs/workflows/notifications): The notification pipeline — quiet hours, deferred sends at 07:00, three retries with backoff, event-key dedup and the hourly reminder job. - [Media](/en/docs/workflows/media): The album pipeline — a 14-day upload window after the trip, resumable batches, four processed variants and archival 30 days later. - [Job Catalog](/en/docs/workflows/scheduled-jobs): Every timer, queue and scheduled job on the platform, with cadence and rule traces — the operations reference. - [Requirement Coverage](/en/docs/workflows/coverage): Which user flows and workflows cover each functional requirement — generated, refresh with bun scripts/coverage-matrix.ts. - Delivery Plan - [Delivery Plan](/en/docs/plan): The end-to-end plan from foundation to scale — phases, generated tasks, milestones and the test strategy, every task traced to a requirement. - [P1 — Foundation](/en/docs/plan/p1): Delivery tasks for P1: accounts, organization applications and approval, tenancy, generated from the requirement trace. - [P2 — Single-vehicle pilot (Egypt)](/en/docs/plan/p2): Delivery tasks for P2: trip creation, traveler booking, payment in EGP, admin basics, generated from the requirement trace. - [P3 — Operational depth](/en/docs/plan/p3): Delivery tasks for P3: multi-vehicle trips, programs, seat modes, moderator app, check-in, generated from the requirement trace. - [P4 — Marketplace supply](/en/docs/plan/p4): Delivery tasks for P4: platform drivers and photographers, lab tests, negotiation, media, generated from the requirement trace. - [P5 — Monetization and Gulf launch](/en/docs/plan/p5): Delivery tasks for P5: plans for all roles, feature gates, coupons, full accounting, invoices; Saudi Arabia (SAR) and UAE (AED), generated from the requirement trace. - [P6 — Family and scale](/en/docs/plan/p6): Delivery tasks for P6: live tracking, parent tracker, analytics, public API, generated from the requirement trace. - [Milestones](/en/docs/plan/milestones): The phase ladder from foundation to scale — tasks per phase, definitions of done and the open decisions that gate each phase. - [Test Strategy](/en/docs/plan/testing): How the specification's acceptance criteria, flows and workflows become the test pyramid — from API tests per requirement to time-travel tests for timers. - [For AI Agents](/en/docs/ai): Machine-readable access: llms.txt, per-page Markdown, search API and an MCP server.