Prototype disclosure
What works, what is imported, and what is simulated
This is an independent RailSaanjh demonstration, not an IRCTC or Railway service. It never creates a journey that is valid for travel.
Back to train searchImplemented prototype behaviour
What you can genuinely try here
Find a route and compare choices [1]
Station search, direction-safe route matching, intermediate boarding, overnight timing, class comparison, and quota selection run against the imported catalogue. General and Premium Tatkal begin directly; Tatkal is the protected route.
Use fair access during a Tatkal surge [3]
A signed anonymous session can create one protected intent, join a deterministic simulated cohort, survive refresh or a short offline interval, receive a time-limited offer, and claim a session-bound booking permit. Repeated polling does not improve priority.
Complete a synthetic booking flow [4]
Select or save synthetic passengers, request an exact demo fare, affirm consent, choose a credential-free mock payment method, and receive a scenario-driven result. Confirmed outcomes use fake-PRS segment-aware allocation.
Retrieve demo outcomes [4]
My Trips and PNR-like lookup work within the anonymous browser session. The documented fixture DMO260001 is synthetic, and every generated ticket says it is not valid for travel.
Imported, but not live
What the catalogue contributes
1,707 services and 3,724 stations are imported from the Datameet Indian Railways catalogue under CC0-1.0. The app uses station names/codes, stops, service names, declared classes, and historical timetable metadata to find a valid route. [1]
That data is marked validity unknown and shown as an illustrative daily schedule. It does not establish that a train runs on the selected date, nor does it supply live availability, fare, quota, berth, booking, or PNR information.
Synthetic data and disconnected services
What must not be treated as real
Railway operations
Availability states and counts, fare estimates and exact totals, quota rules, coach capacity, berth inventory, allocation, waitlist/RAC results, Premium Tatkal pricing, and cancellation/refund outcomes are deterministic simulations—not authoritative Railway or PRS data. [1] [2]
People and identity
The traveller profile, eligibility/risk signals, saved passengers, and all passenger details are synthetic fixtures. The prototype does not verify identity and does not accept Aadhaar, OTP, contact, or real passenger information. [2] [4]
Payments and tickets
Demo UPI, card, and net-banking choices collect no credentials. Payment success, decline, unknown, and refund-pending results come from a versioned test scenario. Tickets and PNR-like references are synthetic and cannot be used for travel. [4]
Demand and operations
People ahead in the waiting room, movement, slowdown, admission throughput, and video fast-forward are a deterministic server-side cohort for demonstration. No real Tatkal demand, queue position, notification, or support channel is connected. [3]
Citation register
Evidence behind this page
- [1] Imported timetable catalogueDownload railway-catalogue.json
Records the DataMeet source, CC0-1.0 licence, unknown timetable validity, illustrative-daily assumption, route matching, and the synthetic commercial-data boundary.
- [2] Prototype boundary and policy decisionsDownload IMPLEMENTATION_DECISIONS.md
Defines the no-live-integration boundary, deterministic queue behaviour, fixture-only passenger data, mock payments, PNR-like references, and persistence requirements.
- [3] Queue implementationDownload V2_PHASE_B_EVIDENCE.md
Implements signed anonymous sessions, idempotency, deterministic cohort progression, reconnectable queue status, admission limits, and scoped permits.
- [4] Booking and retrieval implementationDownload V2_PHASE_C_EVIDENCE.md
Implements synthetic passenger fixtures, fare consent, scenario-driven payment outcomes, fake-PRS allocation, ticket results, My Trips, and PNR-like lookup.
- [5] Hosted-production evidence still outstandingDownload V2_PHASE_B_EVIDENCE.mdDownload V2_PHASE_C_EVIDENCE.mdDownload V2_PHASE_D_EVIDENCE.md
Records that public deployment, hosted Redis restart recovery, multi-instance testing, and manual assistive-technology review are not yet evidenced.
“Implemented” means present and locally verified in this repository. It does not mean publicly deployed, integrated with an external provider, or approved for production use. [5]