Inspect the instrument · 19 October 2026
How the calculation
is checked.
Starry Bodies uses Swiss Ephemeris for astronomical positions. We check the implementation against stored reference calculations, exercise uncertain and invalid inputs, and keep the limits of each check explicit.
These are software checks. Agreement with an astronomical calculation does not establish that an astrological interpretation predicts an outcome.
Reproducible reference checks.
| Check | Observed result | What it covers |
|---|---|---|
| Native calculation bridge | 28 reference chart cases passed | Four sidereal references across seven house systems; reference longitudes, angles, cusps and time scales; equatorial coordinate invariance. |
| Moon bridge | 35 cases passed | Five zodiac frames; UTC and terrestrial-time conversion, illuminated fraction and strict-next quarter-phase roots. |
| Invalid and unavailable inputs | Rejection checks passed | Unsupported settings, invalid coordinates, unavailable polar house calculations and missing precise ephemeris data. |
Both commands were run successfully on 19 October 2026 in the source build environment. The native bridge is compiled from the actual application C bridge and compared with independently generated Swiss Ephemeris reference fixtures. The implementation and fixtures share the Swiss Ephemeris model; this is not an independent comparison against another astronomical model.
Run the same checks.
Download the application source, follow its setup instructions, and run these commands from the project directory. The checks require Python and a C compiler.
python scripts/check-native-bridge.py
python scripts/check-native-moon.pyDownload source, fixtures and third-party notices ↓
What these results do not establish.
The bridge checks run on Linux. They do not compile Swift, link an iOS binary, test WidgetKit or StoreKit, or exercise the interface on an iPhone. Browser, account, map, timing and payment handlers have separate checks in the source. No single check certifies the entire product.
A recorded birth time may be rounded, its historical time zone may require investigation, and city coordinates are representative points. Those input limits remain even when the numerical implementation agrees with its reference. Read the selected methods alongside the result.
What to compare between tools.
Match the UTC instant, location, zodiac reference, house system, node type and displayed bodies before comparing numerical results. For maps, also match the physical coordinate and angularity model. A different method can produce a different answer without either tool having made an arithmetic error.
Methods, models and data sources ↗
This dated report describes the checks observed above. Future changes need their own appropriate verification.