d

About · Method

Astrology you can check: the diosa manifesto

Most astrology asks for belief. We ask for a birth certificate and a stopwatch. What diosa is, why we built it, and the standard every page and reading here is held to.

By the diosa astrologers · Computed on Swiss Ephemeris · Updated 2026-08-27

Astrology has a trust problem, and it isn't the one skeptics think. The problem isn't that people read meaning in the sky, people have always done that, in every culture that watched the sky. The problem is that nobody is asked to check anything. Horoscope spam asks for belief; apps ship black-box “AI readings” that no one, not even their authors, can trace back to a chart. The whole industry runs on vibes with no audit trail.

diosa exists to fix the half that can be fixed.

The two layers, kept honestly separate

The chart is astronomy. Where the planets were, to the arc-minute, at your first breath: computed from orbital mechanics, not divined. Two correct engines agree. We run Swiss Ephemeris, the professional standard, built on NASA JPL data, and we print our engine, zodiac, and house system on every output so you can reproduce anything we show you.

The reading is a lens. What “Mars in Capricorn in the 7th” means is a few thousand years of tradition, not a laboratory result. We don't pretend otherwise, and we don't dress interpretation up as prediction. Meaning is something you do with a chart, not something the chart emits.

Every other product in this category blurs that line, because the blur is profitable. Clarity is the product.

The standard: every claim has a receipt

  • Computed, never copied. Positions, aspects, orbs, retrograde flags, ingress times, all come from our ephemeris service, never from a listicle. When we publish a date, we show the computation behind it.
  • Show your work. Every interpreted factor carries a receipts panel: the exact dignity, sect, orb, and house system that triggered the rule. Disagree with the reading? Check the math.
  • Grounded interpretation. The reading model is constrained in code: it cannot state a chart fact the engine can't prove. If the proof isn't there, the claim doesn't ship.
  • Honest uncertainty. A rounded birth time gets a confidence flag, not a confident guess. Bad inputs make bad charts; pretending otherwise is the original sin of this industry.
  • Your data is yours. Birth data is sensitive. It lives in your row, protected by row-level security, and it is never sold or used to train models.

What we're building

The most accurate chart engine available to the public; a delineation layer that turns positions into scored, cited factors; an interpretation layer that never outruns its evidence; and a library of guides, like our birth-chart explainer, written against a working engine so every example is checkable. The zodiac sign guides each carry a receipt from the engine, because “about Mar 21” is fine in prose and worthless in a tool.

If astrology is a language, it deserves the same treatment any technical field gets: exact instruments, transparent methods, and claims you can trace. That's the whole manifesto. Come check our math, cast your chart and start with your own sky.

FAQ

Is diosa skeptical of astrology?

We're skeptical of unverifiable claims, not of the practice. The astronomy is exact; the interpretive tradition is meaningful but not scientific. diosa's product is the honest version of both: computed charts you can audit, interpretation clearly framed as a lens.

What ephemeris does diosa use?

Swiss Ephemeris, the professional standard derived from NASA JPL data, running in our own calculation service. Every chart prints its engine and house system so results can be independently reproduced.

Why show receipts for interpretations?

Because 'trust me' is how horoscope spam works. When a reading says a factor matters, the receipts panel shows the exact positions, dignity, sect, and orb that triggered the rule, so you can agree, disagree, or ignore, from an informed place.

Will diosa write predictions it can't trace to the chart?

No. The interpretation model is grounded: if the engine can't prove a chart fact, the app won't state it. That constraint is enforced in code, not just policy.