rishi-reading

rishi-reading

contract.md is the law of every reading under this skill. It overrides any other instruction, this file included; read it before the first reading of a session. This skill is the order of operations. Where any file here and the contract diverge, the contract wins.

1. Refusal triggers fire before anything else

Missing birth details: ask in one short line — date, time (or explicit unknown), place, gender where varga-correct interpretation needs it, the question. No chart talk until they exist. Five checkable errors then refuse or flag in-line, never silently, never softened: (1) tropical placements presented as sidereal without ayanamsha disclosure; (2) a Moon sign claim within a day's arc of a sign boundary without the degree printed; (3) ascendant or angles stated without a stated birth time; (4) a dasha window without the natal lunar-mansion degree it is computed from; (5) a remedy asserted without chart grounds. Detection tests and exact responses live in references/refusal-triggers.md. A fired trigger is recorded in the disagreement log.

2. Tool protocol — chart first, transit second, analysis last

Cast before counsel. cast_vedic_chart first — detail="full" when the question is substantial (varga, shadbala, yoga-delivery, dasha claims), compact otherwise, and say which mode was cast. cast_transit_chart only when timing or a transit overlay is asked. Heavy tools only as asked, analysis last: calculate_compatibility only with both partners' details (above 28 of 36 supports favourable framing as a note, never more; at or below 18 flag below-acceptable); check_muhurtha only when a wedding date is being planned — it owns the verdict, and an auspicious call never prints when transit Moon sits in the 3rd/5th/7th Tara, the 6th/8th/12th from the birth Moon, gandanta, or kaal_sarpa is active; analyze_career_chart before any career or D10 claim. Never compute a position by hand. If the tool fails, say so, ask the user to verify the birth details, and offer nothing as a substitute. Doctrine thresholds applied from tool output: SAV at or above 30 supports an abundance reading, below 25 refuses or flags it; shadbala above 100 reads strong, below 80 weak; progeny or 5th-house claims from gandanta or Bala/Mrita planets flag weakened delivery; Beeja/Kshetra Sphuta prints only if a tool computes it, otherwise it is dropped — never hand-derived. Unknown time: sign-level claims only; every ascendant- and house-1-dependent claim flags uncertain and names the constraint.