description: Standardized workflow for ensuring Vedic data integrity during profile imports.

🕉️ Vedic Data Integrity Workflow

To ensure all profiles (native, celebrity, or research) maintain correct house alignments (SAV) across all divisional charts, follow these logic rules:

1. The "4-Section" Data Rule

Every profile .md file in docs/ should ideally contain these four structured sections for full functionality: - 📊 Longitude Table: Used for precise degrees and verifying the D1 Lagna. - ### Rasi (D1): The primary physical chart. Must be in ASCII or Markdown Table format. - ### D9 / D10 / D60: Essential divisional charts. Headers must follow ### [Type] (D[Num]) or ### D[Num]. - ### Vimsottari Dasa: For timing and dasha analysis.

2. Chart Normalization Logic

The system automatically maps various naming conventions to standard keys. Use these aliases in your Markdown headers: - D1: Rasi, D1, D-1 - D9: Navamsha, Navamsa, D9, D-9 - D10: Dashamsha, Dasamsa, D10, D-10

3. Lagna Verification Rule

If a divisional chart (like D9) shows house placements starting from Aries by default (i.e. H1 = Aries), it means the Lagna (As) was not correctly detected. - Check: Ensure the table has a row with **As (Lagna)** in the planets column. - Improved: The asciiParser.ts is now updated to detect: - **As (Lagna)** - As(Sign) (e.g. As(Cp)) - As - Lagna

4. Import Workflow

1. Prepare: Export data from JHora using the ASCII/Grid format or the Markdown table format.
2. Format: Follow the structure in docs/celebrity/nhi-vo.md.
3. Sync: Run npm run sync-user or paste directly into the Step0Input UI.
4. Verify: Use the Chart Ref dropdown in the SAV section. Select D9. Observe if the grid shifts to the correct D9 Lagna sign (e.g., Virgo for Nhi Vo).

5. Metadata Rule

Always include a header in the Markdown:

**User**: [Name]
**DOB**: YYYY-MM-DD
**Time**: HH:MM:SS