Library
Vedic Astrology Wiki

Vedic Astrology Transits: A Guide to Gochara

Learn how Vedic transits compare a target-time sky with a natal reference. Choose guides for gochara, Sade Sati, settings and dasha differences.

Names and related terms
Vedic transits · Gochara

Editorially reviewed: · Reviewed by OpenFate · Editorial Methodology

Overview

A Vedic transit compares a planet’s position at a specified target time with a separately identified natal reference. Start by separating the sky calculation from the traditional interpretation. This guide directs you to the method, Sade Sati and the product’s actual timing boundaries.

At a glance

Moving layer
Planetary positions at the target instant
Fixed reference
Named natal Moon, lagna or other reference
Required settings
Zodiac, ayanamsa, time and coordinate convention
Different technique
A dasha is a natal-input period schedule

Explore concepts

What should I learn before reading a transit?

Use the gochara page to practise relative sign counting. Use Sade Sati for the particular Saturn-to-natal-Moon convention, and dasha-versus-transit to distinguish a period ruler from a moving planet. The settings page explains what makes a comparison reproducible.

A transit interpretation needs both a moving layer and a fixed reference. “Saturn is in the twelfth” is incomplete unless the reader knows twelfth from what, in which zodiac and at which time. A current-looking headline is not a calculation record.

Two readers can have different relative positions

Suppose a hypothetical target-time Saturn is in Pisces. For a natal Moon in Aries, Pisces is the twelfth sign from the Moon; for a natal Moon in Aquarius it is the second. The target sky is the same while the natal reference differs.

This example verifies counting, not either reader’s experience. It does not mean that everyone with a Moon in Aries has the same circumstances, or that changing the reference physically moves Saturn. Keep the two birth records and their uncertainty separate.

What can this guide and the app actually establish?

The locally reviewed OpenFate forecast contract walks frozen Vimshottari intervals and explicitly excludes invented transits. A future-dated dasha card therefore cannot be relabelled as a transit report. This source-code review is not a claim to have checked every currently deployed screen.

The following pages are educational, not live ephemerides or guaranteed event forecasts. If a natal reference is uncertain, retain the alternative counts. Use actual evidence for health, work, resources and relationships instead of treating a transit label as proof.

Sources and editorial basis

  1. P. V. R. Narasimha Rao: Vedic Astrology — An Integrated Approach
    §§25.1–25.2, printed p. 314: natal and target-time positions and natal-Moon reference. The roadmap and hypothetical two-person sign counts are editorial teaching examples, not the chapter’s outcome predictions.A named practitioner’s introduction to Jyotish. Used for terminology and a stated method, not universal school agreement or scientific validation. The added March 18, 2010 note describes changed views; it does not establish a fully revised 2010 edition.
  2. OpenFate Editorial Methodology
    OpenFate Editorial Methodology, stable sections #editorial-principles, #editorial-workflow, #editorial-ai, and #editorial-context. Used for the calculation/interpretation and evidence-boundary policy.OpenFate separates deterministic chart calculation, traditional interpretation, and modern editorial explanation.
  3. Swiss Ephemeris Programmer’s Manual: Time, Sidereal Modes and Houses
    Swiss Ephemeris Programmer’s Manual, §12.1 swe_set_sid_mode (including Lahiri modes) and §12.2 ayanamsa functions; §15 house calculation. The page’s rounded arithmetic examples are original teaching inputs, not ephemeris outputs.Primary software documentation for numerical time and position calculations. Sidereal modes, including named Lahiri variants, are explicit settings. The manual does not validate astrological interpretations.
  4. OpenFate Vedic implementation: local source review, 2026-09-08
    Read-only local source review: app/modules/vedic/interpretation/forecastFacts.ts module contract and prompt/chat/en.ts §11 prohibit invented transits and use frozen Vimshottari intervals; logic/types.ts records unavailable transit factors; logic/policy.ts lists D1/D2/D6/D9/D10/D24, not D4 or D20. This does not verify deployed screens or demonstrate Panchanga, Muhurta or Sade Sati outputs.An editorial review of local policy and calculation source files, not an independently accessible publication or proof of the deployed version. Implementation limitations and discrepancies remain separate from traditional arithmetic.

Search the Wiki