GeminiAPI.comTHE GLOSSARY
A little less jargon.
A lot more clarity.
Twenty-five terms to help you navigate the guides. These definitions describe the conventions and design language used on this site; they do not turn symbolic interpretations into personal facts.
API
An application programming interface: a defined way for software components to exchange information. On this site, API examples are proposed structures and local fixtures, not available hosted services.
Explore the topic ↗Ephemeris
A set of modeled or tabulated positions of astronomical objects over time. Ephemeris data and the symbolic interpretation attached to that data are separate layers in the architecture discussed here.
Explore the topic ↗Natal chart
A chart constructed for a specified birth record under selected conventions. The usefulness of its details depends on the supplied information and the assumptions used to normalize and calculate it.
Explore the topic ↗Birth-time precision
A description of how specifically a birth time is known. Recorded, approximate, and unknown inputs should not silently become equally certain values in a chart pipeline.
Explore the topic ↗Time-zone identifier
A geographic identifier used to resolve civil time with the relevant rules. Keep it distinct from a current fixed offset when documenting a historical input.
Explore the topic ↗UTC
Coordinated Universal Time, a time reference commonly used in normalized timestamps. An application should still document any other time scales required by its calculation engine.
Explore the topic ↗Zodiac
In the introductory astrological model used in these guides, a cycle of twelve equal sectors under a chosen convention. Do not confuse a sign label with an astronomical constellation region.
Explore the topic ↗Tropical zodiac
A conventional zodiac referenced to the March equinox. A response should name the convention instead of leaving readers to infer it from a displayed sign.
Explore the topic ↗Sidereal zodiac
A zodiac using a specified stellar-reference convention. Document the selected offset model and implementation rather than treating the word sidereal as a complete calculation setting.
Explore the topic ↗Ayanamsha
The offset convention used when relating a sidereal zodiac to a tropical reference. A sidereal implementation should identify the model it uses so comparisons are interpretable.
Explore the topic ↗Ecliptic longitude
An angular coordinate around the ecliptic reference used by the selected calculation. Preserve the reference settings and units, and do not confuse it with a location’s geographic longitude.
Explore the topic ↗Ascendant
An astrological chart point associated with the ecliptic and the local eastern horizon. Do not invent it when the inputs required by the selected calculation are missing.
Explore the topic ↗House system
A chosen method for dividing a chart into houses. Treat the method as a setting, disclose it beside the result, and explain unavailable or fallback calculations.
Explore the topic ↗Whole-sign houses
A house convention organized by complete zodiac signs. In the local JSON example, the setting is illustrative; it does not indicate that any houses have been calculated.
Explore the topic ↗Aspect
A selected angular relationship between chart objects. The geometry, the configured target, and the editorial meaning attached to it should remain distinguishable.
Explore the topic ↗Orb
A configured angular tolerance used when selecting aspects or event windows. It is a selection rule, not a measured probability of a personal outcome.
Explore the topic ↗Transit
In these guides, a time-dependent comparison involving modeled positions and a defined reference. A transit event record should remain separate from a reflective passage about it.
Explore the topic ↗Exact contact
A modeled instant that satisfies a specified event criterion. Do not label the nearest coarse sample as exact unless the method actually resolves the contact.
Explore the topic ↗Retrograde motion
Apparent reversal of motion against a chosen sky reference. In a timeline implementation, document the reference and preserve repeated contacts rather than collapsing distinct events.
Explore the topic ↗Synastry
A comparison of selected features from two natal charts under documented conventions. It is not, by itself, a validated measurement of relationship quality or another person’s character.
Explore the topic ↗Composite chart
A derived chart using a specified method of combining two inputs. It should not be labeled as the same object as a direct comparison of two independent charts.
Explore the topic ↗Lunar node
A chart point related to the Moon’s orbital intersection with the ecliptic. The mean-node or true-node choice is computational metadata; a karmic story is a separate interpretation.
Explore the topic ↗Interpretation layer
Reviewed text that supplies symbolic context or reflection. Give it its own identifiers and revisions so a wording change is not confused with recalculating astronomical data.
Explore the topic ↗Medical astrology
Historical and cultural material linking astrological symbols with health concepts. This site does not treat those associations as diagnosis, treatment guidance, or a personal health assessment.
Explore the topic ↗Text alternative
A written explanation that communicates the information in a visual. Complex chart diagrams may need a nearby table or extended description in addition to a short image alt attribute.
Explore the topic ↗The next step is yours
Make space for a new idea.
Explore a topic. Understand the inputs. Build with perspective.