Traditional transit use
Use a transiting planet’s own BAV as one context layer, not as a standalone event forecast.
A common traditional use is to inspect how many bindus a planet has in the sign through which that same planet is transiting.
The bindu count describes the Ashtakavarga support assigned to that sign in the natal grid; it does not specify which event must happen.
A full transit reading still needs the natal house/sign being crossed, natal planets contacted, lordship, Dasha and the rest of the chart.
Ashtakavarga is a point-distribution system. The fixed BAV checksum belongs to the rule system; the useful chart-specific information is how those points distribute across the twelve signs.
Read the audit grid before reading the total. Each bindu comes from a contributor and a counted position, so the learner should be able to reproduce why a cell is 0 or 1. SAV is then the sign-wise sum of the seven planetary BAV rows.
How to read it
- Choose the target BAV planet.
- Choose one sign column.
- Audit all eight contributor decisions.
- Verify the planet’s fixed row checksum.
- Use SAV/BAV as context, not as a standalone event prediction.
Key points
- BAV row totals are fixed checksums.
- Distribution across signs is chart-specific.
- SAV = sum of seven planetary BAV rows, not a separate mysterious score.
Do not call a high raw SAV number a guaranteed positive event without the rest of the transit/natal context.
Apply this lesson to a chart
- Open Ashtakavarga Lab.
- Choose one planet and one sign.
- Explain at least two contributor bindu decisions from the audit table.