Ning's Vedic Astrology Analysis System

What problem it solves

Vedic astrology analysis often breaks down at the data entry and rule execution layers: charts may arrive as PDF files, screenshots, or text; birth time may be uncertain; natal, synastry, and Prashna workflows are easy to mix. nings-vedic-astrology splits these flows into routed submodules and uses structured_data.md as a shared intermediate artifact, so downstream analysis starts from the same validated dataset.

How it works

The root SKILL.md only routes the request. Execution follows the selected module file:

• Reader: extracts and validates chart data from PDF files, screenshots, or text, then produces structured_data.md.
• Calculator: calculates a chart directly from birth date, time, and location using the scripts/ chain, then produces structured_data.md.
• Core: runs P1-P12, house, divisional chart, life-area, and Q&A workflows.
• Rectifier: calibrates uncertain birth time using event-to-house relationships.
• Career / Love: handles career and romantic timing topics separately.
• Synastry: reads both parties' structured_data.md files and performs relationship chart analysis.
• Prashna: handles independent horary or time-specific questions without requiring the natal Core workflow.

The usual path is to identify the input type, enter the matching module stage, and let that module read its required resources, run scripts, or validate outputs. Language follows the client by default; Japanese clients may use resources/ja-*.md localization layers without changing algorithms, thresholds, or artifacts.

Boundaries and cautions

• The selected module file is the execution source of truth. Root routing does not replace module-level calculations, thresholds, stages, or output requirements.
• Natal, synastry, and Prashna are separate workflows. Existing natal data does not automatically trigger Core analysis.
• Conclusions must come from the current module's authorized data and rules. User history must not be used to back-derive chart conclusions.
• When reading SAV house values, follow the Core house mapping instead of recomputing from raw sign values.
• Commercial use is subject to AGPL-3.0, so applicable open-source obligations must be respected.