This document outlines the user interface logic and state flow for the Vedic Astro React Application. For astrological interpretation rules, please see APP_CONTEXT.md (which maps to Vedic- How to_Original.md).
| Screen | Focus Area | User Input / Action | Generated Output |
|---|---|---|---|
| Screen 1 | Natal Initialization | User inputs primary birth data (Rasi, Dasas). | Prepares context for Step 1 & 2 interpretations. |
| Screen 2 | Technical Distillation | User triggers technical calculations (Step 0). | Produces Step 1 and Step 2 technical outputs. Provides "Copy Prompt & Data" buttons for 4 sub-steps of Step 2. |
| Screen 3 | Divisional Charts (Vargas) | User selects up to 3 specific D-charts (D2, D3, D4, etc.) via checkboxes. D1, D9, D10 pre-loaded. | Context parameters for Step 3 calculation. Opens input spaces for selected Vargas. |
| Screen 4 | Varga Analysis | User clicks "Calculate Vedic aspect". | Technical data output for each selected Varga (not step-based). Provides navigation to return to Screen 3 or proceed to Screen 5. |
| Screen 5 | Timing & Transits | User inputs Vim/Rasi dasas (Step 4.1) and current transit/Ashtakavarga metrics (Step 4.2). | Final Timing and Transit technical output. |
| Component / Workflow | Rule |
|---|---|
| Workspace Data Persistence | All data MUST be stored per-session (Context API). Screen 3 and 4 must link back to Screen 1 & 2 data for contextual processing. |
| Step 3 Prioritization | D1, D2, D9, and D10 have UI priority. Explain 1-2 sentence purpose/Karaka for each D-chart selected. |
| Step 4 Transit Logic | Technical data needs basic natal context (Lagna) included in the copy/paste logic to be interpreted correctly by the AI. |
| GEM Agent Profile | Assigned Screens/Steps | Primary Instructions |
|---|---|---|
| GEM 1: Natal Promise | Steps 1, 2, 3 | Use React App's "Step 0.5 Output" focusing on Parts 1, 2, 3. Yields deep psychological/spiritual interpretation. |
| GEM 2: Event Timing | Step 4 | Receives technical transit data and base natal context (Lagna) to analyze triggers and Event Timing. |