Who’s behind the readings
House Call is one practitioner, working directly across all three traditions. There’s no team of tradition consultants sourcing separate reference corpora, and no hand-off to a model that drafts on its own. The practitioner has configured a Claude instance with reference material and methodology specific to each tradition (Vronsky Western, BaZi, Vedic) and directs it per chart, per tradition, throughout the process, cross-referencing the instrument’s output against the chart math as they go.
The practitioner directs and ships every reading, the document you receive. That means: work the chart through the instrument tradition by tradition, cross-check every named transit against the chart math in real time, cut passages that drift into generic Sun-sign prose, rewrite the synthesis where the three traditions strain against each other, write the “short answer” callouts where the chart deserves one. The instrument is fast; the practitioner’s judgment is the reason a House Call reading is specific to your chart instead of generically plausible.
The detailed AI disclosure (what the model can and can’t see, where it fails, how the practitioner watches for it) lives at /how-we-use-ai.
The synthesis method
Three independent traditions compute their views of the same birth chart, and the practitioner weaves them into a single document, directing the AI instrument through each tradition in turn. Three lenses, one chart, with the practitioner doing the interpretive work of saying where they agree and where they honestly disagree.
- Western (Vronsky-school): classical natal chart math: planets in signs, planets in houses, aspects between them, the chart ruler.
- Chinese BaZi (Four Pillars): day-pillar day master + the five elements as expressed across year, month, day, hour pillars. Older system; reads structure, not story.
- Vedic Jyotish: sidereal positions with Lahiri ayanamsa, plus Vimshottari Dasha timing. Reads trajectory in 16 to 20 year arcs.
Where all three agree, the reading speaks at high confidence. Where they diverge, it stays honest about the uncertainty rather than picking a winner.
What the model does (and what it doesn’t)
A Claude instance, configured with the Vronsky / BaZi / Vedic reference material, is what the practitioner directs throughout the drafting process. It works from the chart math and the curated reference passages keyed to your configuration as the practitioner works through each section with it, not on its own beforehand. The practitioner cross-checks and rewrites as it goes, and ships the result.
What the model specifically does not do: run the chart math (Swiss-Ephemeris-equivalent positions do that deterministically); decide what’s true (the practitioner does that, cross-checked against the chart math); produce a reading independent of the practitioner’s direction (a hard rule, the DB schema enforces it). No reading has ever gone out without the practitioner’s hands-on involvement.
If you’re here because Reddit pointed you at us with the question “isn’t this just AI slop?” The honest answer is: a generic ChatGPT spitting out Sun-sign prose is slop. A single accountable practitioner directing a purpose-built instrument through a curated multi-tradition corpus, cross-checking every word against the chart math, is what makes three-tradition synthesis economically possible at this depth. The speed comes from the instrument; the specificity comes from the practitioner’s direction and judgment.
How a reading is actually built
For each commissioned reading the workflow is:
- Intake. The practitioner collects birth data + context questions from the buyer.
- Chart math. Tropical positions, Lahiri- ayanamsa sidereal positions, and BaZi four-pillar resolution are computed deterministically from the birth data.
- Directed synthesis (practitioner + instrument). The chart math plus the curated reference passages keyed to this chart’s configuration go into the AI instrument. The practitioner works through each tradition section with it, in turn, plus a synthesis pass and the short-answer callouts.
- Cross-check and rewrite. The practitioner checks every line against the chart math as they go. Catches false transit claims, cuts generic Sun-sign prose, rewrites passages where the synthesis strains the source tradition, checks that the three traditions actually converge where the text says they do, validates that named predictions are falsifiable-by-date. Where the chart genuinely doesn’t support a claim, the claim gets cut, not softened.
- Voice + format pass. Final pass for voice consistency, structural rhythm, and short-answer callout placement. Then it ships.
- Customer follow-up. The practitioner runs the customer-facing question + feedback loop, directing the same instrument against the same reference material and shipping the result.
Each reading takes 5 to 14 days end-to-end depending on depth tier, and most of that time is the practitioner actively working the chart. The instrument is fast; the days are the practitioner directing it through every tradition, cross-checking against the chart math, and rewriting whatever didn’t hold up. A fast machine response is cheap; the practitioner’s time is what the price covers.
What we got wrong in the first five readings
Beta means we’ve been wrong about things. The honest list:
- Saturn-return timing was off by ~14 months in one reading because the model anchored to the tropical return without weighting the Vedic sidereal lag enough. The practitioner has since formalised a cross-system timing rule that catches this before it ships.
- BaZi was under-served in the first two readings: the day master got named but its element interactions didn’t. We added a requirement that the synthesis section anchor on a BaZi paragraph before it’s allowed to ship.
- The “short answer” callout at the top of each section was added after a reader said the long-form prose was beautiful but they couldn’t tell what the chart was actually saying. They were right.
- One reading was too long: 18,000 words where 12,000 would have hit harder. Now the tier word counts are ceilings, not targets.
- Predictions weren’t falsifiable enough in the first cohort. We now stamp each prediction with a check-by date and an outcome chip (true / false / mixed) so the practice gets feedback on its own accuracy over time.
Where we’re still stuck
- Resolving Western Mercury-retrograde claims against the same period in Vedic dasha terms, the systems sometimes describe the same months in language that looks contradictory but is actually pointing at the same underlying texture. The practitioner is still finding the vocabulary for this and the instrument still produces awkward seams.
- Working a sparse natal (born outside major aspect windows, weak BaZi element interplay), the same framework that sings on a busy chart can feel forced on a quieter one. Working on a “quiet-chart” voice that doesn’t over-claim.
- The follow-up question rate-limit (3/week) is honest about capacity but feels stingy. Considering a per-cohort pool instead.
What this is not
- One reading, not a daily horoscope generator.
- Not medical, legal, financial, or psychiatric advice.
- Not deterministic predictions about specific events.
- A one-off reading at three depths, not a subscription.
- Intake is limited and every application gets a personal review, so spots are finite rather than first come, first served.
- The practitioner directs a purpose-built AI instrument through every reading, tradition by tradition, cross-checking against the chart math and shipping each section by hand. This happens every time; no reading skips it.
If you want to try the practice
Three soft entry points, easiest first:
- Free Sun-snapshot: 10 seconds, no signup. Tells you the strongest aspect today’s sky is making to your Sun.
- Sample reading: three real reading sections, anonymised. The depth + voice you’d get if you booked.
- Book the full reading: pricing opens soon. Refundable until delivered. Founders’ cohort pricing locks in for the first 25 readers.
Questions about how the practice works (or where you think we’ve got it wrong) are welcome. Reply to any email from us, or write to hello@housecallastro.com (The practitioner runs the customer-facing channel personally).