- affliction_evidence / career_semantic_profile / career_analysis (functional roles, affliction signals, user-industry gate) - sade_sati.build_saturn_cycle_timeline with bisected ingress moments (FLG_SIDEREAL frame, BUG-1275) - Chesta profile candidates and PL9 AV cell profile as sidecars (shadbala.py / ashtakavarga.py stay frozen, ERR-110) - Raman Sahams in the annual pack; book rule packets + admission gate - consultation_native_layers: affliction_evidence, career_analysis, sade_sati_timeline, shadbala_chesta_profiles, book_rules, annual_tajika.raman_sahams Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DbBXoyn7Hj3LCW3BUs5bZ8
869 lines
91 KiB
JSON
869 lines
91 KiB
JSON
{
|
||
"schema_version": 1,
|
||
"copyright_boundary": "non_verbatim_rule_summaries_and_locators_only",
|
||
"packets": [
|
||
{"rule_id":"sripati_vii_ruler_recenter_geometry","source_id":"web:sripati_paddhati_scan","admission_state":"reference_only","assertion_boundary":"Named geometric realization of ruler longitude as Ascendant; supplied astronomy, not independently verified historical chart reconstruction","page_locator":"VII printed132 recenter instruction;137-138 Mars-centered diagram; Swiss houses_armc API","source_url":"https://www.ebharatisampat.in/pdfs/ebharati-pdf-1621321809Sripatipadhati.pdf","supporting_source_urls":["https://www.astro.com/swisseph/swephprg.htm"],"non_verbatim_rule_summary":"Rebuild the Bhava chart with the period ruler's longitude as Ascendant, then place unchanged natal positions in it. Explicit spherical rising-point inversion supplies ARMC/MC; existing quadrant trisection provides centers for midpoint assignment.","implementation_targets":["scripts/aayu_sripati_periods.py","tests/test_sripati_recenter.py"],"validation":{"status":"fixture_passed","test_path":"tests/test_sripati_recenter.py","validation_kind":"fixture_numeric","validated_assertions":["Forward/inverse astronomical geometry across latitudes and quadrants","Cardinal case, polar blockers, native period integration for both profiles, portable CLI"],"not_validated_reason":"No printed chart/date reproduction or automatic birth/strength composition; obliquity/ayanamsa remain explicit inputs"}},
|
||
{"rule_id":"sripati_vii_diwakara_all_occupants","source_id":"web:sripati_paddhati_scan","admission_state":"reference_only","assertion_boundary":"Named supplied-Bhava reading of Diwakara child selection/order, not a complete autonomous birth-to-period doctrine","page_locator":"VII15 commentary printed135-136; VII16-17 printed137; PDF indices148-150 visually checked","source_url":"https://www.ebharatisampat.in/pdfs/ebharati-pdf-1621321809Sripatipadhati.pdf","non_verbatim_rule_summary":"Diwakara retains eligible occupants rather than only the strongest and follows Dasakrama instead of the textual order of relationship groups. Apply per-participant relation fractions, normalize over selected bodies and recurse for Vidasa.","implementation_targets":["scripts/aayu_sripati_periods.py","tests/test_aayu_diwakara.py"],"validation":{"status":"fixture_passed","test_path":"tests/test_aayu_diwakara.py","validation_kind":"fixture_numeric","validated_assertions":["Distinct all-participant order/weights, exact parent partitions, query and CLI","Bhattotpala original profile retained; missing inputs and ties remain blocked"],"not_validated_reason":"Synthetic/derived rule tests, not independent Diwakara numerical case; supplied Bhava interpretation explicit, recentering/year and source strength exceptions unresolved"}},
|
||
{"rule_id":"web_rath_saptarishi_mundane_year_table","source_id":"web:rath_saptarishi_mundane","admission_state":"reference_only","assertion_boundary":"Published mundane year-table lookup only; not natal doctrine or historical verification","page_locator":"Present Period; year-table notes; Antardasha table","source_url":"https://srath.com/jyoti%E1%B9%A3a/nak%E1%B9%A3atra/saptar%E1%B9%A3i-nak%E1%B9%A3atra/","non_verbatim_rule_summary":"Published reverse27-star sequence has960-year major periods. The1699..2659 parent contains nine century children and a final60-year child. Preserve astronomical year numbering and unknown transition days.","implementation_targets":["scripts/saptarishi_mundane.py","tests/test_saptarishi_mundane.py"],"validation":{"status":"fixture_passed","test_path":"tests/test_saptarishi_mundane.py","validation_kind":"fixture_numeric","validated_assertions":["Published MD anchors and complete child table","Year boundaries, unsupported ranges, strict inputs and portable report CLI"],"not_validated_reason":"No complete PD rule, precise civil boundary, independent historical validation or natal source admission"}},
|
||
{"rule_id":"web_jhora_360_tithi_pravesha_composition","source_id":"web:pvr_jhora_year_options","admission_state":"reference_only","assertion_boundary":"Software year option and separately attributed annual families; composition remains explicit, not universal author prescription","page_locator":"JHora features Dasas first bullet; PVR2004 Yoga and Nakshatra annual sections","source_url":"https://www.vedicastrologer.org/jh/features.htm","supporting_source_urls":["https://www.indiadivine.org/content/topic/1223159-research-panchanga-pravesha-charts-and-dasas/"],"non_verbatim_rule_summary":"360-Tithi year uses actual relative Moon-Sun motion. Explicitly combine this4320-degree clock with existing Yoga or Nakshatra annual period producers, preserving their distinct seeds and cycles; do not relabel its endpoint as a successor return.","implementation_targets":["scripts/pravesha_return_year.py","scripts/annual_pravesha.py","tests/test_pravesha_tithi_year.py"],"validation":{"status":"fixture_passed","test_path":"tests/test_pravesha_tithi_year.py","validation_kind":"fixture_numeric","validated_assertions":["Actual4320-degree span, full-parent MDADPD and half-open query","Main report current alternatives retain separate family timelines without successor search"],"not_validated_reason":"No independent full dates, universal annual prescription, intercalary selector or predictive case admission"}},
|
||
{"rule_id":"web_pvr_karana_360_tithi_year","source_id":"web:pvr_jhora_year_options","admission_state":"reference_only","assertion_boundary":"Explicit astronomical year option with one published numerical MD case; not universal calendar or event admission","page_locator":"JHora features:360-Tithi years; PVR2004 Karana section full1995 MD table","source_url":"https://www.vedicastrologer.org/jh/features.htm","supporting_source_urls":["https://www.indiadivine.org/content/topic/1223159-research-panchanga-pravesha-charts-and-dasas/"],"non_verbatim_rule_summary":"Use actual unwrapped Sun-Moon relative motion for a360-Tithi year. Each of seven equal nominal MD shares spans4320/7 degrees; invert astronomical motion for civil boundaries while preserving Karana angular balance.","implementation_targets":["scripts/karana_annual_dasha.py","scripts/pravesha_return_year.py","tests/test_karana_tithi_year.py"],"validation":{"status":"fixture_passed","test_path":"tests/test_karana_tithi_year.py","validation_kind":"fixture_numeric","validated_assertions":["All nine published1995 boundaries within60seconds without fitted epoch or year","Actual angular shares, annual clipping, query boundaries and portable CLI"],"not_validated_reason":"AD/PD, automatic intercalary selection, Tribhagi and predictive cases remain open"}},
|
||
{"rule_id":"web_pvr2002_karana_quadrant_lords","source_id":"web:pvr_panchanga_lords_2002","admission_state":"reference_only","assertion_boundary":"Complete seed mapping, not full annual timing admission","page_locator":"PVR signed2002-10-20 reply, item1;2004 research1993/1995 chart seeds","source_url":"https://www.indiadivine.org/content/topic/1212615-importance-of-weekday-and-panchanga/","supporting_source_urls":["https://www.indiadivine.org/content/topic/1212964-karana-panchanga-examples-my-first-emails-to-sri-kn-rao-and-pt/","https://www.indiadivine.org/content/topic/1223159-research-panchanga-pravesha-charts-and-dasas/"],"non_verbatim_rule_summary":"Movable Karana lords follow weekday order. Fixed Karana lords follow current-chart quadrants1,4,7,10; a printed Venus seed is chart-dependent, not a universal Kimstughna rule.","implementation_targets":["scripts/karana_annual_dasha.py","tests/test_karana_pvr_seed.py"],"validation":{"status":"fixture_passed","test_path":"tests/test_karana_pvr_seed.py","validation_kind":"fixture_numeric","validated_assertions":["Sixty slots across twelve ascendants; missing ascendant preserves angles and blocks fixed periods","Native source epochs reproduce77.27% Kimstughna and71.98% Vishti; native Leo gives tenth lord Venus","Annual MD/report/CLI and standalone seed work"],"not_validated_reason":"No complete author year convention, AD/PD or independent full-period dates"}},
|
||
{"rule_id":"web_samiti_karana_lords","source_id":"web:veda_samskruti_samiti_karana","admission_state":"reference_only","assertion_boundary":"Panchanga lord mapping only; annual Dasha combination is an explicit experiment, not source doctrine","page_locator":"Karna: karana-adhi devata-ruling planet/graha table","source_url":"https://vedasamskrutisamiti.org.in/karna/","non_verbatim_rule_summary":"A complete eleven-Karana planetary table differs from Julene for several movable and all fixed entries. Preserve the full named alternative rather than patching node rows.","implementation_targets":["scripts/karana_annual_dasha.py","tests/test_karana_samiti_seed.py"],"validation":{"status":"fixture_passed","test_path":"tests/test_karana_samiti_seed.py","validation_kind":"fixture_numeric","validated_assertions":["All60 slots and four fixed-seed annual branches; source conflict retained"],"not_validated_reason":"No source endorsement of composition, independent period-date verification or AD/PD"}},
|
||
{"rule_id":"web_pvr2002_tithi_balance_discrimination","source_id":"web:pvr_tithi_ashtottari_2002","admission_state":"reference_only","assertion_boundary":"Published seed-fraction numeric comparison only; elapsed-time is an explicit alternative, not a claimed author rule","page_locator":"First Dasa Remainder; Example1 natal and2002 return; Example2 1994 return","source_url":"https://www.indiadivine.org/content/topic/1187969-tithi-ashtottari-dasa-tutorial/","non_verbatim_rule_summary":"The initial duration uses remaining Tithi fraction. Native angular and actual-duration fractions differ; compare both against printed percentages without changing the named MD/AD algorithm.","implementation_targets":["scripts/tithi_ashtottari.py","tests/test_tithi_elapsed_balance.py"],"validation":{"status":"fixture_passed","test_path":"tests/test_tithi_elapsed_balance.py","validation_kind":"fixture_numeric","validated_assertions":["Three source epochs support angular fraction at printed precision under explicit Lahiri true-position settings","Actual Tithi boundary crossings, wrap, annual/natal MDAD and CLI"],"not_validated_reason":"No complete author settings, independent fine-date or event calibration; no PD or Tribhagi"}},
|
||
{"rule_id":"web_mhora_yoga_clock_distinction","source_id":"web:mhora_0_2","admission_state":"reference_only","assertion_boundary":"Software source inspection and native astronomical diagnostic only; no external execution or adopted annual rule","page_locator":"256fb4b8 Dasas.cs ToDate.AddYears; DasaControl.cs compressToYogaPraveshaYearYoga","source_url":"https://github.com/sureshdr/mhora/blob/256fb4b873b6a76316260fbe11101952353fe90c/DasaControl.cs#L1150","non_verbatim_rule_summary":"The software exposes a Yoga-sum year clock distinct from elongation. Compare unwrapped sum and difference motion without treating either name as proof of the author's annual scale.","implementation_targets":["scripts/pravesha_year_basis_diagnostic.py","tests/test_pravesha_year_basis_diagnostic.py"],"validation":{"status":"fixture_passed","test_path":"tests/test_pravesha_year_basis_diagnostic.py","validation_kind":"fixture_numeric","validated_assertions":["Unwrapped sum equals lunar plus solar motion","Published NP intervals distinguish equal elongation from unequal Yoga-sum motion"],"not_validated_reason":"External C#/WinForms runtime unavailable; no external MD/AD/PD replay or traditional year adoption"}},
|
||
{"rule_id":"web_pyjhora_saptarishi_named_anchors","source_id":"web:pyjhora_saptarishi","admission_state":"reference_only","assertion_boundary":"External software options only; independent traditional applicability unresolved","page_locator":"48e57d29 get_dhasa_bhukthi and _dhasa_progression, dhasa_starting_planet parameter","source_url":"https://github.com/naturalstupid/PyJHora/blob/48e57d29b47a3143519910a24866758116467485/src/jhora/horoscope/dhasa/graha/saptharishi_nakshathra.py","non_verbatim_rule_summary":"Named Moon, Sun or Lagna anchor is passed to the external D1 producer; preserve selected longitude, returned nakshatra periods and actual runtime parameters separately.","implementation_targets":["scripts/specialized_dasha_external_replay.py","tests/test_saptarishi_external.py"],"validation":{"status":"fixture_passed","test_path":"tests/test_saptarishi_external.py","validation_kind":"fixture_numeric","validated_assertions":["Three anchors actually execute at depths1/2/3","Synthetic fixture produces three distinct first stars","Default Moon timeline unchanged; named report/query retained"],"not_validated_reason":"No independent classical anchor doctrine, real case or customer admission; installed runtime not pinned to source link"}},
|
||
{"rule_id":"web_pvr2004_yoga_natal_explicit_year","source_id":"web:pvr2004_yoga_letter","admission_state":"reference_only","assertion_boundary":"Source natal seed/MD years; fixed-day dates and child recursion remain explicit conventions","page_locator":"Signed Narasimha letter 2004-08-13, computation(2), Siddhi40-percent example","source_url":"https://www.indiadivine.org/content/topic/1221098-yoga-pravesha-and-yoga-vimsottari-dasa-tithi-pravesh/","non_verbatim_rule_summary":"Yoga ruler supplies first period and remaining fraction supplies balance. Continue regular Vimshottari years. Annual compression is a separate use, not a requirement for the natal cycle.","implementation_targets":["scripts/yoga_annual_dasha.py","scripts/jyotish_engine.py","tests/test_yoga_natal_periods.py"],"validation":{"status":"fixture_passed","test_path":"tests/test_yoga_natal_periods.py","validation_kind":"fixture_numeric","validated_assertions":["Siddhi40percent yields Mars2.8 years, then Rahu18 and Jupiter16","Explicit fixed-year birth clipping, child coverage and half-open query"],"not_validated_reason":"No independent author year constant, PD example, real case or customer admission"}},
|
||
{"rule_id":"sripati_vii14_uniform_common_reading","source_id":"web:sripati_paddhati_vii","admission_state":"reference_only","assertion_boundary":"Explicit textual-reading candidate, not sole traditional algorithm or complete printed-number parity","page_locator":"VII14 commentary pp127/131-132","source_url":"https://www.ebharatisampat.in/pdfs/ebharati-pdf-1621321809Sripatipadhati.pdf","non_verbatim_rule_summary":"Opt-in interpretation: exact common positive values across distinct bodies are subtracted once per distinct value uniformly within each comparison group. This preserves ordering; negative adjusted groups are blocked. Printed Saturn balance remains discrepant.","implementation_targets":["scripts/aayu_sripati_periods.py","tests/test_sripati_vargabala.py"],"validation":{"status":"fixture_passed","test_path":"tests/test_sripati_vargabala.py","validation_kind":"fixture_numeric","validated_assertions":["source Kendra and full MD order under explicit candidate reading","common occurrence trace, no near-value rounding, default unchanged","negative adjusted group blocked and raw matrix retained"],"not_validated":["independent traditional corroboration of once-per-value rule","source Saturn31.401; exact26.783674 differs","universal applicability or cases"]}},
|
||
{"rule_id":"sripati_vii12_14_vargabala_matrix","source_id":"web:sripati_paddhati_vii","admission_state":"reference_only","assertion_boundary":"Raw exact matrix only, not final Samyavargabala ranking","page_locator":"VII12-14 pp127-131; original pp128/129/131 visually inspected","source_url":"https://www.ebharatisampat.in/pdfs/ebharati-pdf-1621321809Sripatipadhati.pdf","non_verbatim_rule_summary":"Allocate one quarter of the body strength to D1 and one eighth to each other Saptavarga, then multiply by the corresponding lord strength. Retain all56 products and raw totals; do not invent unresolved mutual cancellation.","implementation_targets":["scripts/aayu_sripati_periods.py","tests/test_sripati_vargabala.py"],"validation":{"status":"fixture_passed","test_path":"tests/test_sripati_vargabala.py","validation_kind":"fixture_numeric","validated_assertions":["56 source products within0.006Rupa while preserving exact arithmetic and printed rounding differences","raw totals never replace rectified ranking strengths","standalone CLI, report and optional period evidence"],"not_validated":["Samyavargabala mutual cancellation and printed Saturn balance","birth-derived Shadbala and divisional lords","independent dates or outcomes"]}},
|
||
{"rule_id":"sripati_vii_bhattotpala_periods","source_id":"web:sripati_paddhati_vii","admission_state":"reference_only","assertion_boundary":"Supplied-input chronology, not independently verified birth dates or outcomes","page_locator":"VII8-17 printed121-138; pp132-133 original images inspected","source_url":"https://www.ebharatisampat.in/pdfs/ebharati-pdf-1621321809Sripatipadhati.pdf","non_verbatim_rule_summary":"Rank MD by seed and angular/succedent/cadent groups. Select Bhattotpala strongest-per-group children and normalize1,1/2,1/3,1/7,1/4 shares recursively. Lagna-first strength uses triangular Bhavaphala times Shadbala; other seed rules remain distinct.","implementation_targets":["scripts/aayu_sripati_periods.py","tests/test_aayu_sripati_periods.py"],"validation":{"status":"fixture_passed","test_path":"tests/test_aayu_sripati_periods.py","validation_kind":"fixture_numeric","validated_assertions":["published MD order and exact supplied-year accumulation","Sun child shares28:14:4:7 and Mars recursion6:3:2","native source Sun Bhavaphala geometry","partial input retention, query boundaries and decision-relevant ties","native exact supplied-center Bhava assignments; unequal sandhi, ruler anchor and cross-chart input consistency"],"not_validated":["automatic ruler recentering or Sun/Moon Varga strength","Diwakara child ordering","independent calendar dates, real cases or customer routing"]}},
|
||
{"rule_id":"sripati_v_nisargayu_diwakara_table","source_id":"web:sripati_paddhati_v","admission_state":"reference_only","assertion_boundary":"Native named-profile arithmetic; full printed-table parity and Dasha dates unclosed","page_locator":"V13-28 printed86-98, Diwakara note p93; PDF100-112; original pp87/97/98 visually inspected","source_url":"https://www.ebharatisampat.in/pdfs/ebharati-pdf-1621321809Sripatipadhati.pdf","non_verbatim_rule_summary":"Natural quotas use exaltation-distance interpolation, continuous visible-half deduction, maximum enemy/combustion loss, and within-sign rising reduction. Select Diwakara single Lagna and the table's Lagna reduction explicitly.","implementation_targets":["scripts/nisargayu_sripati.py","tests/test_nisargayu_sripati_native.py"],"validation":{"status":"fixture_passed","test_path":"tests/test_nisargayu_sripati_native.py","validation_kind":"fixture_numeric","validated_assertions":["source angular differences and continuous deduction fractions","no Mars enemy exemption, maximum not sequential deduction","explicit horizon/strongest/rising-aspect controls","portable CLI and retained partial results"],"not_validated":["printed74.2756 total vs exact-input74.23278857; Jupiter row divergence","Devala averaged divisor or strong-Lagna doubled variant","native MD/AD/PD chronology or outcomes"]}},
|
||
{"rule_id":"raman_aiyar_pindayu_contributions","source_id":"raman_horoscope_v2","admission_state":"reference_only","assertion_boundary":"Named composite contribution arithmetic, not Dasha dates or outcome","page_locator":"Raman Vol2 printed97-104 / PDF104-111; Aiyar Brihat Jataka VII notes4,7","source_url":"https://chestofbooks.com/new-age/astrology/Brihat-Jataka/On-Ayurdayaor-The-Determination-Of-The-Length-Of-Life-Part-2.html","non_verbatim_rule_summary":"Raman exaltation-distance base and sequential deductions; Aiyar total-sum full-ecliptic Krurodaya convention, nearest occupant and benefic-aspect relief; Raman within-sign Navamsa Lagna contribution added last.","implementation_targets":["scripts/pindayu_raman.py","scripts/raman_aayu_rules.py","tests/test_pindayu_raman_native.py"],"validation":{"status":"fixture_passed","test_path":"tests/test_pindayu_raman_native.py","validation_kind":"fixture_numeric","validated_assertions":["Raman Chart33 supplied deductions and Lagna contribution","Aiyar independent98.5 subtotal and5/6 deduction gives16years5months","extrema/symmetric base arcs, exemptions, missing-strength/aspect and tie boundaries"],"not_validated":["automatic chart conditions or strengths","BPHS occupant-only or alternate Lagna rule","Nisargayu adjustment","Dasha chronology or outcomes"]}},
|
||
{"rule_id":"raman_v2_amsayu_sequential_adjustments", "source_id":"raman_horoscope_v2", "admission_state":"reference_only", "assertion_boundary":"Source-bounded arithmetic on supplied chart conditions, not chronology or life outcome", "page_locator":"Vol2 printed99-100,105-108 / PDF106-107,112-115", "non_verbatim_rule_summary":"Amsayu base uses longitude in Navamsa units modulo12. Apply the greatest eligible increase once, then visible-house, enemy-sign and combustion deductions sequentially with stated exceptions; no Krurodaya. Only the strongest occupant of a crowded visible house suffers that house deduction.", "implementation_targets":["scripts/amsayu_raman.py","scripts/pindayurdaya.py","tests/test_amsayu_raman_native.py"], "validation":{"status":"fixture_passed","test_path":"tests/test_amsayu_raman_native.py","validation_kind":"fixture_numeric","validated_assertions":["Raman p99 table visually checked against original PDF","Chart34 supplied conditions reproduce named fractions without fitting printed rounded days","maximum increase once, sequential reductions and exemptions","missing strength preserves unaffected contributions"],"not_validated":["automatic chart conditions or strength","printed day-level discrepancy resolution","Dasha chronology and event reliability"]}},
|
||
{"rule_id":"web_rath_padanadhamsa_narayana_cycles","source_id":"web:rath_narayana_dasa","admission_state":"reference_only","assertion_boundary":"Named-source native cycle arithmetic; not calendar or predictive validation","page_locator":"Padanadhamsa pp191-192; Table53 pp193-194; second-cycle rule p44 and zero complement example p45; AD pp49-51","source_url":"https://scienceoflight.net/wp-content/uploads/extra/Narayana%20Dasa%20by%20Sanjay%20Rath.pdf","non_verbatim_rule_summary":"The Padanadhamsa section directs use of standard Navamsa Narayana rules. Reuse the complement cycle and source-profiled child rules, preserving zero spans and unresolved exceptions.","implementation_targets":["scripts/padanadhamsa.py","scripts/padanadhamsa_calendar.py","tests/test_padanadhamsa_two_cycle.py"],"validation":{"status":"fixture_passed","test_path":"tests/test_padanadhamsa_two_cycle.py","validation_kind":"fixture_numeric","validated_assertions":["Table53 first nine MD spans retained","complement cycle uses existing native rule","repeated parent identity and zero-complement exclusion","calendar engine and portable CLI preserve both cycles"],"not_validated":["independent second-cycle date oracle","birth balance and PD","event reliability"]}},
|
||
{"rule_id":"web_raman_numeric_strength_trikona_md_ad","source_id":"web:raman_studies_jaimini","admission_state":"reference_only","assertion_boundary":"Source sign/rank arithmetic, not independent ephemeris, dates, events or universal Jaimini doctrine","page_locator":"Sections62-72 pp36-44,79-86 pp47-50,92-94 pp58-62; Examples16/18/23/24","source_url":"https://www.scribd.com/doc/127930441/Studies-in-Jaimini-Astrology-by-b-v-Raman","non_verbatim_rule_summary":"Raman numerical sign-strength adaptation selects the trinal seed. Apply his sign-group order and dual-lord duration rules, retaining unresolved exceptions and explicit conventions.","implementation_targets":["scripts/trikona_raman.py","tests/test_trikona_raman_native.py"],"validation":{"status":"fixture_passed","test_path":"tests/test_trikona_raman_native.py","validation_kind":"fixture_numeric","validated_assertions":["seven planetary and twelve Rasi totals","automatic Virgo seed","all twelve published MD spans","144 AD with same-profile parent boundaries"],"not_validated":["ambiguous Druk duplicate roles","node dignity and extreme-debility exception","birth chronology and dates","PD and predictive accuracy"]}},
|
||
{"rule_id":"local_raman_manual_dignity_trikona","source_id":"local:raman_manual_hindu_astrology","admission_state":"reference_only","assertion_boundary":"Raman-specific MT degree ranges and natural relationships; exaltation precedence remains explicit profile","page_locator":"A Manual of Hindu Astrology sections25-30,printedpp11-13; local transcription pages102/104/106","non_verbatim_rule_summary":"Use the author's own degree ranges and permanent relationships, retaining their differences from the repository Shadbala constants.","implementation_targets":["scripts/trikona_raman.py","tests/test_trikona_raman_native.py"],"validation":{"status":"fixture_passed","test_path":"tests/test_trikona_raman_native.py","validation_kind":"fixture_numeric","validated_assertions":["Mars18 Jupiter13 Venus10 MT endpoints","exaltation-first explicit convention"],"not_validated":["node dignity","universal cross-tradition MT boundaries"]}},
|
||
{"rule_id":"web_raman_trikona_94_ad","source_id":"web:raman_studies_jaimini","admission_state":"reference_only","assertion_boundary":"Confirmed-full-parent AD sequence and nominal duration only; no birth chronology or date calibration","page_locator":"Section94 pp61-62; section155 p127","source_url":"https://www.scribd.com/doc/127930441/Studies-in-Jaimini-Astrology-by-b-v-Raman","non_verbatim_rule_summary":"Equal child durations and parent-dependent trinal traversal; use the author's sign groups, separately from parity-based variants.","implementation_targets":["scripts/trikona_dasha.py","tests/test_trikona_raman_antardasa.py"],"validation":{"status":"fixture_passed","test_path":"tests/test_trikona_raman_antardasa.py","validation_kind":"fixture_numeric","validated_assertions":["Sagittarius and Capricorn published AD sequences","equal nominal child durations"],"not_validated":["birth seed and full MD anchor","calendar oracle","PD","event reliability"]}},
|
||
{"rule_id":"web_pvr26_sarvatobhadra_vedha","source_id":"web:pvr_textbook_ch26_8","admission_state":"reference_only","assertion_boundary":"Native supplied-star Vedha geometry and target matches,not predictive validation","page_locator":"Chapter26.8,Figure3 pp357-362;Example114 ray contents and Example116 target pairs;special phonetic principles p359","source_url":"https://vedicastrologer.org/articles/vedic_astro_textbook.pdf","non_verbatim_rule_summary":"Trace source-defined paths from each supplied transit star and match typed natal or thematic references. Keep corner/phonetic additions and alternative motion selection explicit; preserve source discrepancies.","implementation_targets":["scripts/sarvatobhadra_chakra.py","tests/test_sarvatobhadra_native.py"],"validation":{"status":"fixture_passed","test_path":"tests/test_sarvatobhadra_native.py","validation_kind":"fixture_numeric","validated_assertions":["Example114 complete ray contents","Example116 five named target groups and source planet pairs","28-star rays,numbering,motion variants,corner/phonetic and missing-input handling"],"not_validated_reason":"Supplied inputs only;no ephemeris-derived independent case,full variant doctrine,event or customer admission"}},
|
||
{"rule_id":"web_kota_modern_guardians_routes","source_id":"web:kota2006_2011_parallel","admission_state":"reference_only","assertion_boundary":"Modern source-named structure and placement predicates only","page_locator":"2006 Kota Cakra signed Swee teaching/Pradeep first section:108-pada table; Vijayalur2011 sections Construction,Terminologies,Example,Rules and author comment;VS alternative guard paragraph;Mindsutra sample printedp10","source_url":"https://vijayalur.com/2011/06/02/kota-chakra/","non_verbatim_rule_summary":"Anchor the modern fort at natal Moon's star; select the guardian by an explicit pada-table or star-lord profile. Track supplied motion on the roads, retain pillar/stationary states and separate the sources' different guardian-location preferences.","implementation_targets":["scripts/kota_chakra.py","tests/test_kota_native.py"],"validation":{"status":"fixture_passed","test_path":"tests/test_kota_native.py","validation_kind":"fixture_numeric","validated_assertions":["Rohini full partition,Magha3 and Ashlesha4 guardians","Vendor Hasta2 example Mercury/Rahu and nine transit layers,including Abhijit","108padas,variant differences,retrograde/stationary/pillar behavior and external partition comparison"],"not_validated_reason":"Supplied star fixtures,not birth-derived ephemeris or event validation;classical plan,Vedha,functional judgment and customer routing open"}},
|
||
{"rule_id":"web_cole2004_kalachakra_diagram","source_id":"web:cole_kalachakra2004","admission_state":"reference_only","assertion_boundary":"Named layout, Moon seed and traditional structural labels; no predictive admission","page_locator":"Movement of Prana in the Kalachakra, SJC2004: numbered direction diagram, public example and Direction section; JHora feature list for separate Sun/annual-Lagna seeds","source_url":"https://shrifreedom.org/vedic-astrology/kalachakra/","non_verbatim_rule_summary":"Start the numbered28-star diagram at the Moon's star in this lineage. Preserve square layers, fortress and cardinal/diagonal flow labels. Alternate documented seeds remain separate compositions.","implementation_targets":["scripts/kalachakra_layout.py","tests/test_kalachakra_native_layout.py"],"validation":{"status":"fixture_passed","test_path":"tests/test_kalachakra_native_layout.py","validation_kind":"fixture_numeric","validated_assertions":["All nine planets match author example from supplied star table","All28 anchor rotations;27/28 star conventions and explicit annual input checks"],"not_validated_reason":"No birth-derived ephemeris, annual example, activation or predictive validation; Abhijit longitude endpoints inconsistent in source"}},
|
||
{"rule_id":"patel_nadi_ch1_ch2_named_nonuniform","source_id":"local:patel_nadi_astrology_2002","admission_state":"reference_only","assertion_boundary":"Named nonuniform interval lookup and separate uniform comparison; no predictive admission","page_locator":"Chapters I-II; local transcription PDF11-18; Vasudha/Sukhada and A-E examples","source_url":"https://sanjayprabhakaran.blogspot.com/2005/03/nadyamsa-from-parasaras-shodasa-vargas.html?m=1","non_verbatim_rule_summary":"Combine classical division boundaries into150 unequal intervals; assign name numbers by sign modality. Retain the uniform convention separately and expose angular uncertainty instead of forcing one identity.","implementation_targets":["scripts/chandra_kala_nadi.py","tests/test_chandra_kala_nadi.py"],"validation":{"status":"fixture_passed","test_path":"tests/test_chandra_kala_nadi.py","validation_kind":"fixture_numeric","validated_assertions":["Chapter II named intervals across movable/fixed/dual signs;100..1800arcsecond widths","Exact rational endpoints, circular uncertainty candidates and separate uniform result"],"not_validated_reason":"No manuscript spelling validation, external JHora parity, predictive case or customer admission"}},
|
||
{"rule_id":"web_bphs43_46_aayu_family_identity","source_id":"web:bphs43_46_aayu","admission_state":"reference_only","assertion_boundary":"Family identity and ordering context only; no admission of external harana or outcome formulas","page_locator":"BPHS43.4-22,30-32;46.201-202; compare Raman Vol2 PDF105-113/printed98-106","source_url":"https://jyotishvidya.com/ch43.htm","non_verbatim_rule_summary":"Keep three contribution systems and their reference-strength choices distinct. The Dasha family includes Lagna and seven classical planets. Reduction and increase combinations differ among texts; external software choices must retain their own profiles.","implementation_targets":["scripts/aayu_dasha_report.py","scripts/specialized_dasha_external_replay.py","scripts/pindayurdaya.py","scripts/amsayu.py","tests/test_aayu_external_report.py"],"validation":{"status":"fixture_passed","test_path":"tests/test_aayu_external_report.py","validation_kind":"external_runtime_observation","validated_assertions":["Three explicit runtime branches execute MD/AD/PD with Lagna and seven planets","Harana switch changes actual observed periods; named paths preserve raw output"],"not_validated_reason":"Synthetic software checks only; no independent traditional formula/date or event validation, no customer admission"}},
|
||
{"rule_id":"web_pvr_tithi_ashtottari_2002_md_ad","source_id":"web:pvr_tithi_ashtottari_2002","admission_state":"reference_only","assertion_boundary":"Annual supplied-seed and explicit-year natal MD/AD; angular adapter and reverse alternative separately qualified","page_locator":"2002-12-13 tutorial: First Dasa, Remainder, Compression, Antardasas, Examples1-2;2002-12-19 clarification quotes book pp179/187","source_url":"https://www.indiadivine.org/content/topic/1187969-tithi-ashtottari-dasa-tutorial/","non_verbatim_rule_summary":"Select the named Tithi ruler, scale initial remaining fraction, compress108 units to the actual selected annual span. Subdivide full parents proportionally from the next ruler forward before clipping. Preserve the reported preceding-reverse alternative separately.","implementation_targets":["scripts/tithi_ashtottari.py","scripts/jyotish_engine.py","tests/test_tithi_ashtottari_native.py","tests/test_tithi_ashtottari_natal.py"],"validation":{"status":"fixture_passed","test_path":"tests/test_tithi_ashtottari_native.py","validation_kind":"fixture_numeric","validated_assertions":["All30 rulers; K12 quarter and324-day compression; full annual coverage and child clipping","Example1 rounded lengths and dates within one day; Example2 calculated209.96days retained with printed November8 discrepancy"],"not_validated_reason":"No precise source ephemeris or event validation; reverse source is a book quotation; angular/time balance,PD,author-specific natal calendar/Tribhagi and customer admission remain open"}},
|
||
{
|
||
"rule_id": "web_rath_tara_lesson4_grouped_md",
|
||
"source_id": "web:rath_vimsottari_lesson4",
|
||
"admission_state": "reference_only",
|
||
"assertion_boundary": "Named grouped MD rule with supplied strength ranks; not automatic seed, source calendar or child periods",
|
||
"page_locator": "Vimsottari Dasa, Lesson4 and Example2 Steps1-2; related Crux printed pp6-7/local transcription Page17-18",
|
||
"source_url": "https://srath.com/jyoti%E1%B9%A3a/dasa/vimsottari-dasa/",
|
||
"non_verbatim_rule_summary": "Use the lesson's Lagna quadrant eligibility and strongest-first ordering within Kendra, Panapara and Apoklima groups. Preserve ordinary planetary Vimshottari durations. The book's reference-selection discussion is a separate variant.",
|
||
"implementation_targets": ["scripts/tara_dasha.py", "scripts/jyotish_engine.py", "tests/test_tara_native.py", "tests/test_tara_birth_adapter.py"],
|
||
"validation": {"status":"fixture_passed", "test_path":"tests/test_tara_native.py", "validation_kind":"fixture_numeric", "validated_assertions":["Published nine-lord order from supplied within-group ranks and source group membership; durations total120", "Synthetic fixed-year dates, birth clipping and applicability boundaries"], "not_validated_reason":"No automatic strength or source-balance validation; Example2 AM/PM contradicts itself; AD/PD, dated cases and customer admission remain open"}
|
||
},
|
||
{"rule_id":"web_pvr_sudarsana_ch31_solar","source_id":"web:pvr_vedic_astro_textbook","admission_state":"reference_only","assertion_boundary":"Named native solar algorithm only; no predictive or customer admission","page_locator":"Ch27.1/27.3/27.4 solar units; Ch31.3 printed pp409-411","source_url":"https://www.vedicastrologer.easyhoma.org/articles/vedic_astro_textbook.pdf","non_verbatim_rule_summary":"Advance each natal reference one zodiacal sign per birth year. Each child begins at its parent sign. Solar arcs are 360,30,2.5 degrees for MD,AD,PD, not equal elapsed-day partitions.","implementation_targets":["scripts/sudarsana_dasha.py","scripts/jyotish_engine.py","tests/test_sudarsana_native.py"],"validation":{"status":"fixture_passed","test_path":"tests/test_sudarsana_native.py","validation_kind":"fixture_numeric","validated_assertions":["Textbook year45 three-reference example; exact child coverage and solar boundaries"],"not_validated_reason":"Author astronomical settings not fully specified; no event-outcome validation, global closure or customer admission"}},
|
||
{"rule_id":"web_pvr_sudarsana_2004_owner_seed","source_id":"web:pvr_sudarsana_2004","admission_state":"reference_only","assertion_boundary":"Named native solar algorithm only; no predictive or customer admission","page_locator":"Signed PVR letter 2004-12-17; public D10 MD1994/AD2000/PD2000 tables","source_url":"https://www.indiadivine.org/content/topic/1224052-fwd-sudarsa-chakra-dasa-time-based-predictions-using-rasi/","non_verbatim_rule_summary":"Retain annual solar progression but start children at the natal sign occupied by the classical ruler of each parent sign; then advance zodiacally. Keep this research revision separate from the textbook.","implementation_targets":["scripts/sudarsana_dasha.py","scripts/jyotish_engine.py","tests/test_sudarsana_native.py"],"validation":{"status":"fixture_passed","test_path":"tests/test_sudarsana_native.py","validation_kind":"fixture_numeric","validated_assertions":["Native birth-derived chronology:12 MD,12 AD,12 PD rows;72 edge comparisons within120seconds; source fixed -04 offset"],"not_validated_reason":"Author astronomical settings not fully specified; no event-outcome validation, global closure or customer admission"}},
|
||
{
|
||
"rule_id": "web_julene_2017_karana_lord_table",
|
||
"source_id": "web:julene_louis_karana_2017",
|
||
"admission_state": "reference_only",
|
||
"assertion_boundary": "Named Karana identity/lord table and angular seed only; annual composition remains parameter-sensitive",
|
||
"page_locator": "Karana – Half Lunar Day, 2017-10-09, Meaning and Shukla/Krishna Paksha tables",
|
||
"source_url": "https://julenelouis.com/2017/10/09/karana-half-lunar-day/",
|
||
"non_verbatim_rule_summary": "Sixty half-tithi slots use seven repeating planetary rulers and four fixed node-ruled slots. Keep these node identities rather than silently substituting a seven-planet period lord. Angular remainder and time remainder are separate inputs.",
|
||
"implementation_targets": ["scripts/karana_annual_dasha.py", "tests/test_karana_native_seed.py"],
|
||
"validation": {"status": "fixture_passed", "test_path": "tests/test_karana_native_seed.py", "validation_kind": "fixture_numeric", "validated_assertions": ["All60 slot lords, wrap and exact6-degree boundary", "PVR Vishti example angular remainder rounds to printed71.98% under explicit true-position profile"], "not_validated_reason": "Different authors' rules explicitly composed; fixed node to Dasha substitution, variable-year dates and child rules unresolved; no customer admission"}
|
||
},
|
||
{
|
||
"rule_id": "web_pvr_sjvc15_sudasa_md_ad_2001",
|
||
"source_id": "web:pvr_sjvc_lesson15_2001",
|
||
"admission_state": "reference_only",
|
||
"assertion_boundary": "Native MD/AD rule and one confirmed-parent dated AD table; no verified birth calendar or predictive/customer admission",
|
||
"page_locator": "Lesson15 sections1.2,3.1-3.3 (pp1-4); section3.4.2 complete Leo MD/AD table (p6)",
|
||
"source_url": "https://argala.ru/pdf-files/sudasa_calculation.pdf",
|
||
"non_verbatim_rule_summary": "Derive Sree Lagna from lunar mansion progress. Keep this lesson's parity and Saturn/Ketu ordering exceptions distinct from older versions. Full parent has twelve equally weighted children; observed calendar days differ. A caller-confirmed parent supports a separately labelled solar-clock reconstruction without solving the birth anchor.",
|
||
"implementation_targets": ["scripts/sudasa.py", "scripts/jyotish_engine.py", "tests/test_sudasa_sjvc15_calendar.py", "tests/test_sudasa_anchored_antardasa.py"],
|
||
"validation": {"status": "fixture_passed", "test_path": "tests/test_sudasa_anchored_antardasa.py", "validation_kind": "fixture_numeric", "validated_assertions": ["Twelve Leo MD antardasas and 24 edge comparisons within120seconds of published table, with source MD start supplied", "Native AD direction and variable-duration solar dates retained"], "not_validated_reason": "Supplied full-MD anchor is not a birth-derived calculation; single source case only; calendar clock inferred, not an explicit textual year definition; customer gate remains reference-only"}
|
||
},
|
||
{
|
||
"rule_id": "web_jss_guru_rajesh_varnada_md_ad_2018",
|
||
"source_id": "web:jss_guru_rajesh_2018",
|
||
"admission_state": "reference_only",
|
||
"assertion_boundary": "Supplied-seed sign/year and AD algorithm only, not source calendar, longevity or customer admission",
|
||
"page_locator": "First Chapter: Chakra definitions, Hora Dasa general year/Antardasa rules, Varnada Dasa and Charts47-49; title/preface identifies K. Guru Rajesh, Vijayadasami2018",
|
||
"source_url": "https://www.scribd.com/document/863539521/Jaimini-Jathaka-Sara-Sangraha",
|
||
"non_verbatim_rule_summary": "Both ascendant parities use their own count origin. Period shifts use the ascendant-to-Varnada distance. Keep node-triggered sequence reversal distinct from duration and child counting; use the translation's general own/opposite exceptions and twelve-part children.",
|
||
"implementation_targets": ["scripts/varnada_dasha.py", "scripts/jyotish_engine.py", "tests/test_varnada_jss.py"],
|
||
"validation": {"status": "fixture_passed", "test_path": "tests/test_varnada_jss.py", "validation_kind": "fixture_numeric", "validated_assertions": ["Classical example ten durations; Charts47/48/49 two/seven/eight MD durations", "Chart47 first three AD signs and quarter-year duration; synthetic calendar partition and node reversal"], "not_validated_reason": "No original astronomical settings, source-calendar replay or predictive success claim; packet remains reference-only for customer gate"}
|
||
},
|
||
{
|
||
"rule_id": "web_shanmukha_jss_savayava_hora_2009",
|
||
"source_id": "web:shanmukha_jss_update_2009",
|
||
"admission_state": "reference_only",
|
||
"assertion_boundary": "Explicit sign-origin solar Hora variant, not BPHS Hora or a complete Varnada doctrine",
|
||
"page_locator": "An Update on Jataka Sara Sangraha, 2009-07-01, Savayava Hora and Problems in this calculation sections",
|
||
"source_url": "https://sutramritam.blogspot.com/2009/07/update-on-jataka-sara-sangraha-om-namah.html",
|
||
"non_verbatim_rule_summary": "Use separate actual daytime/nighttime fractions to advance from the natal sign. Preserve the author's discussion of alternate degree conventions and avoid substituting ordinary solar Hora.",
|
||
"implementation_targets": ["scripts/varnada_dasha.py", "scripts/jyotish_engine.py", "tests/test_varnada_savayava_hora.py"],
|
||
"validation": {"status": "fixture_passed", "test_path": "tests/test_varnada_savayava_hora.py::test_author_example_both_parities_without_rounded_remainder_fit", "validation_kind": "fixture_numeric", "validated_assertions": ["Published input clock gives eight completed horas and Gemini/Pisces for the two source ascendants", "Exact remainder computed from input seconds, not fitted to rounded printed degrees"], "not_validated_reason": "Actual solar event flags are an explicit runtime convention, not recovered author astronomical settings; no full date/event or customer admission"}
|
||
},
|
||
{
|
||
"rule_id": "web_mks_varnada_jss_shifted_count",
|
||
"source_id": "web:mks_new_light_jaimini_part2",
|
||
"admission_state": "reference_only",
|
||
"assertion_boundary": "Named candidate with source table residual; not lifespan, event or customer admission",
|
||
"page_locator": "New Light II, Varnada Rasi / Determination of first Dasa and editorial worked Scorpio row; compare New Light III editorial note",
|
||
"source_url": "https://saptarishisshop.com/new-light-on-jaimini-astrology-part-2-by-madhura-krishnamurthi-sastri/",
|
||
"non_verbatim_rule_summary": "Use the source's JSS Savayava Hora, keeping ordinary Hora and BPHS separate. A named shifted-sign count-minus-one reading produces MD candidates; the article's table and later editorial retrospective are not fully consistent.",
|
||
"implementation_targets": ["scripts/varnada_dasha.py", "scripts/jyotish_engine.py", "tests/test_varnada_native.py"],
|
||
"validation": {"status": "fixture_passed", "test_path": "tests/test_varnada_native.py::test_published_first_nine_rows_and_tenth_residual_not_fitted", "validation_kind": "fixture_numeric", "validated_assertions": ["Source SHL and occupied-versus-empty seed", "First nine published lengths; independently computed tenth mismatch retained"], "not_validated_reason": "Cancer5 versus printed8 and count convention unresolved; clock synthetic, no date or event verification"}
|
||
},
|
||
{
|
||
"rule_id":"web_pvr_karana_chaturashiti_2004",
|
||
"source_id":"web:pvr_panchanga_pravesha_2004_archive",
|
||
"admission_state":"reference_only",
|
||
"assertion_boundary":"Explicit-span candidate; does not admit automatic seed mapping or annual date rule",
|
||
"page_locator":"Archived 2004-08-24 research letter, Karana Chaturaseeti Sama Dasa and Warning/Acknowledgement sections",
|
||
"source_url":"https://www.indiadivine.org/content/topic/1223159-research-panchanga-pravesha-charts-and-dasas/",
|
||
"non_verbatim_rule_summary":"Use the Karana ruler for the initial period and carry its remaining fraction into the first balance; subsequent periods follow Chaturashiti order. The author's 1995 return example identifies Vishti/Saturn with 71.98% remaining. Annual clock and complete lord assignments are not specified here.",
|
||
"implementation_targets":["scripts/karana_annual_dasha.py","scripts/jyotish_engine.py","tests/test_karana_annual_native.py"],
|
||
"validation":{"status":"fixture_passed","test_path":"tests/test_karana_annual_native.py::test_source_seed_and_scaled_balance","validation_kind":"fixture_numeric","validated_assertions":["Supplied Saturn seed, .7198 remaining, regular seven-lord sequence","Synthetic 350-day span scales first balance and full parent consistently"],"not_validated_reason":"350 days is synthetic, not source calendar fit; no full mapping, variable-clock or event validation"}
|
||
},
|
||
{
|
||
"rule_id": "web_pvr_kaala_2009_solar_sixths",
|
||
"source_id": "web:pvr_kaala_chakra_2009",
|
||
"admission_state": "reference_only",
|
||
"assertion_boundary": "source-bounded MD formula, not published calendar or event validation",
|
||
"page_locator": "Kaala Dasa and Chakra Dasa, 2009-11-01, PDF pp1-2; Kennedy table discrepancy p5",
|
||
"source_url": "https://www.vedicastrologer.org/articles/kc_dasas.pdf",
|
||
"non_verbatim_rule_summary": "Use sixths of actual day and adjacent nights to locate the birth segment. Its elapsed and remaining fractions divide 120 years into two phases, each distributed by nine planetary ordinal weights totalling 45. Keep the author's hypothesis separate from a universal BPHS interpretation.",
|
||
"implementation_targets": ["scripts/kaala_dasha.py", "scripts/specialized_dasha_router.py", "scripts/jyotish_engine.py", "tests/test_kaala_native.py"],
|
||
"validation": {"status":"fixture_passed","test_path":"tests/test_kaala_native.py::test_published_5pm_example_all_eighteen_lengths","validation_kind":"fixture_numeric","validated_assertions":["Published ideal 5pm seed fraction 1/4 and 30/90-year phases","All eighteen weighted MD lengths"],"not_validated_reason":"Full dated independent cases and author year convention unresolved. Reference-only prevents automatic customer book-packet admission."}
|
||
},
|
||
{
|
||
"rule_id": "web_pvr_varsha_narayana_ch30_4",
|
||
"source_id": "web:pvr_vedic_astro_textbook",
|
||
"admission_state": "reference_only",
|
||
"assertion_boundary": "source-bounded rule calculation; not exact source dates or event verification",
|
||
"page_locator": "PVR Vedic Astrology: An Integrated Approach, ch30.1/30.4, printed pp396,401-402; Chart67 PDF p409",
|
||
"source_url": "https://vedicastrologer.org/articles/vedic_astro_textbook.pdf#page=413",
|
||
"non_verbatim_rule_summary": "Progress natal Lagna one sign per completed year for the annual reference. Apply explicitly selected Narayana rules to annual positions; convert nominal years to three degrees of Sun motion and retain the first 360 degrees. For D-N, use the Nth lord from the progressed reference in annual D1, placed in the annual D-N chart, before sign-strength selection.",
|
||
"implementation_targets": ["scripts/varsha_narayana.py", "scripts/jyotish_engine.py", "tests/test_varsha_narayana_native.py"],
|
||
"validation": {"status":"fixture_passed","test_path":"tests/test_varsha_narayana_native.py::test_published_muntha_seed_saturn_exception_and_first_five_lengths","validation_kind":"fixture_numeric","validated_assertions":["Muntha Capricorn; ninth lord Mercury in annual D9 Scorpio","Scorpio seed and Saturn exception; lengths 7,4,2,3,11"],"not_validated_reason":"Printed Pisces start July20 differs from computed July21; full-date oracle and independent cases open. Reference-only prevents automatic shared/customer book-packet promotion; native research entry is separately callable."}
|
||
},
|
||
{
|
||
"admission_state": "candidate_mapped",
|
||
"assertion_boundary": "does_not_imply_runtime_execution",
|
||
"implementation_targets": [
|
||
"scripts/argala.py",
|
||
"tests/test_argala.py"
|
||
],
|
||
"non_verbatim_rule_summary": "Evaluate Argala from relevant reference points, particularly the ascendant and Arudha ascendant, rather than limiting it to one fixed point.",
|
||
"page_locator": "Volume 1 PDF p. 546; printed p. 195, Principle of Argala",
|
||
"rule_id": "science_of_light_v1_argala_reference_points",
|
||
"source_id": "science_of_light_v1",
|
||
"validation": {
|
||
"status": "not_validated",
|
||
"test_path": "tests/test_argala.py::TestPrimaryArgala::test_argala_output_identifies_science_of_light_reference_packet",
|
||
"validation_kind": "wiring_only",
|
||
"validated_assertions": [
|
||
"source_reference_packets_field_wiring"
|
||
],
|
||
"not_validated_reason": "receipt does not prove the rule formula: only string wiring / boundary text / unrelated legacy structural assertions observed"
|
||
}
|
||
},
|
||
{
|
||
"admission_state": "validated_reference",
|
||
"assertion_boundary": "does_not_imply_runtime_execution",
|
||
"implementation_targets": [
|
||
"scripts/jaimini.py",
|
||
"tests/test_jaimini.py"
|
||
],
|
||
"non_verbatim_rule_summary": "Compute a house Arudha by measuring the inclusive sign distance from the house to its lord, then applying the same inclusive distance from the lord; the ascendant Pada is the principal Pada.",
|
||
"page_locator": "Volume 1 PDF pp. 531-533; printed pp. 187-188, Bhavapada Calculation",
|
||
"rule_id": "science_of_light_v1_arudha_reflection",
|
||
"source_id": "science_of_light_v1",
|
||
"validation": {
|
||
"status": "fixture_passed",
|
||
"test_path": "tests/test_jaimini.py::TestArudhaPada::test_science_of_light_taurus_example_reaches_virgo",
|
||
"validation_kind": "fixture_numeric",
|
||
"validated_assertions": [
|
||
"arudha_lagna_sign_reaches_virgo_for_taurus_asc_venus_in_cancer",
|
||
"inclusive_distance_equals_3",
|
||
"exception_triggered_is_false"
|
||
]
|
||
}
|
||
},
|
||
{
|
||
"admission_state": "candidate_mapped",
|
||
"assertion_boundary": "does_not_imply_runtime_execution",
|
||
"implementation_targets": [
|
||
"mcp_server.py",
|
||
"references/strict-workflow-router.md",
|
||
"tests/test_mcp_strict_workflow_relationship.py"
|
||
],
|
||
"non_verbatim_rule_summary": "For timing, distinguish planetary Dasha as a planetary predominance frame and Rashi Dasha as an activated-life-area frame; cross-check both with current transit rather than reading one timing layer alone.",
|
||
"page_locator": "Volume 1 PDF p. 729; printed p. 288, Calculation of Vimshottari Dasha",
|
||
"rule_id": "science_of_light_v1_dasha_rashi_transit_crosscheck",
|
||
"source_id": "science_of_light_v1",
|
||
"validation": {
|
||
"status": "not_validated",
|
||
"test_path": "tests/test_mcp_strict_workflow_relationship.py::test_relationship_strict_contract_exposes_adjudication_stages_and_multi_reference_summary",
|
||
"validation_kind": "unrelated_legacy_test",
|
||
"validated_assertions": [
|
||
"multi_reference_reading_summary_frame_presence"
|
||
],
|
||
"not_validated_reason": "receipt does not prove the rule formula: only string wiring / boundary text / unrelated legacy structural assertions observed"
|
||
}
|
||
},
|
||
{
|
||
"admission_state": "candidate_mapped",
|
||
"assertion_boundary": "does_not_imply_runtime_execution",
|
||
"implementation_targets": [
|
||
"mcp_server.py",
|
||
"references/strict-workflow-router.md",
|
||
"tests/test_mcp_strict_workflow_relationship.py"
|
||
],
|
||
"non_verbatim_rule_summary": "Before a conclusion, validate the chart against known history and combine relevant chart layers, timing systems, strength, and condition; select techniques by the user's question rather than treating one factor as a complete reading.",
|
||
"page_locator": "Volume 1 PDF pp. 1069-1070; printed pp. 408-409, Interpretation",
|
||
"rule_id": "science_of_light_v1_interpretation_multilayer_validation",
|
||
"source_id": "science_of_light_v1",
|
||
"validation": {
|
||
"status": "not_validated",
|
||
"test_path": "tests/test_mcp_strict_workflow_relationship.py::test_relationship_strict_contract_exposes_adjudication_stages_and_multi_reference_summary",
|
||
"validation_kind": "unrelated_legacy_test",
|
||
"validated_assertions": [
|
||
"multi_reference_reading_summary_frame_presence"
|
||
],
|
||
"not_validated_reason": "receipt does not prove the rule formula: only string wiring / boundary text / unrelated legacy structural assertions observed"
|
||
}
|
||
},
|
||
{
|
||
"admission_state": "candidate_mapped",
|
||
"assertion_boundary": "does_not_imply_runtime_execution",
|
||
"implementation_targets": [
|
||
"scripts/muhurta.py",
|
||
"tests/test_muhurta.py"
|
||
],
|
||
"non_verbatim_rule_summary": "Read Panchanga as a five-limbed temporal structure, retaining Vara, Tithi, Nakshatra, Yoga, and Karana together rather than treating one limb as the complete time judgment.",
|
||
"page_locator": "Volume 1 PDF pp. 995-997; printed pp. 382-384, Panchanga introduction",
|
||
"rule_id": "science_of_light_v1_panchanga_five_limbs",
|
||
"source_id": "science_of_light_v1",
|
||
"validation": {
|
||
"status": "not_validated",
|
||
"test_path": "tests/test_muhurta.py::TestPanchangaComplete::test_five_elements_present",
|
||
"validation_kind": "structural_legacy_test",
|
||
"validated_assertions": [
|
||
"five_panchanga_elements_present"
|
||
],
|
||
"not_validated_reason": "receipt does not prove the rule formula: only string wiring / boundary text / unrelated legacy structural assertions observed"
|
||
}
|
||
},
|
||
{
|
||
"admission_state": "candidate_mapped",
|
||
"assertion_boundary": "traditional_supportive_practice_not_clinical_or_guaranteed_outcome",
|
||
"implementation_targets": [
|
||
"scripts/remedies.py",
|
||
"tests/test_science_of_light_remedies.py"
|
||
],
|
||
"non_verbatim_rule_summary": "Present traditional remedies as optional supportive practices across practical lifestyle choices, reflective or breathing practices, and devotional or charitable acts; do not represent them as clinical care or guaranteed outcomes.",
|
||
"page_locator": "Volume 1 PDF p. 964; Introduction to Remedies",
|
||
"rule_id": "science_of_light_v1_remedies_supportive_practices",
|
||
"source_id": "science_of_light_v1",
|
||
"validation": {
|
||
"status": "not_validated",
|
||
"test_path": "tests/test_science_of_light_remedies.py::test_science_of_light_remedies_remain_supportive_and_non_clinical",
|
||
"validation_kind": "boundary_text",
|
||
"validated_assertions": [
|
||
"advisory_boundary_text",
|
||
"three_supportive_practice_categories"
|
||
],
|
||
"not_validated_reason": "receipt does not prove the rule formula: only string wiring / boundary text / unrelated legacy structural assertions observed"
|
||
}
|
||
},
|
||
{
|
||
"admission_state": "candidate_mapped",
|
||
"assertion_boundary": "does_not_imply_runtime_execution",
|
||
"implementation_targets": [
|
||
"scripts/shadbala.py",
|
||
"tests/test_shadbala_complete.py"
|
||
],
|
||
"non_verbatim_rule_summary": "Separate a planet or house's strength from the quality and direction of its results; strength alone cannot support a final interpretation and must be combined with functional role and other evidence.",
|
||
"page_locator": "Volume 1 PDF p. 460; printed p. 161, Strength, States and Results",
|
||
"rule_id": "science_of_light_v1_strength_interpretation_boundary",
|
||
"source_id": "science_of_light_v1",
|
||
"validation": {
|
||
"status": "not_validated",
|
||
"test_path": "tests/test_shadbala_complete.py::TestShadbalaFull::test_all_7_planets_calculated",
|
||
"validation_kind": "unrelated_legacy_test",
|
||
"validated_assertions": [
|
||
"all_7_planets_calculated"
|
||
],
|
||
"not_validated_reason": "receipt does not prove the rule formula: only string wiring / boundary text / unrelated legacy structural assertions observed"
|
||
}
|
||
},
|
||
{
|
||
"admission_state": "candidate_mapped",
|
||
"assertion_boundary": "does_not_imply_runtime_execution",
|
||
"implementation_targets": [
|
||
"mcp_server.py",
|
||
"references/strict-workflow-router.md",
|
||
"tests/test_mcp_strict_workflow_relationship.py"
|
||
],
|
||
"non_verbatim_rule_summary": "Treat a divisional chart as a refinement of natal-chart indications for its specific life area; do not produce an independent outcome claim from a varga alone.",
|
||
"page_locator": "Volume 1 PDF p. 877; Varga Chakra (Interpretation of Divisional Charts)",
|
||
"rule_id": "science_of_light_v1_varga_refinement_boundary",
|
||
"source_id": "science_of_light_v1",
|
||
"validation": {
|
||
"status": "not_validated",
|
||
"test_path": "tests/test_mcp_strict_workflow_relationship.py::test_relationship_strict_contract_exposes_adjudication_stages_and_multi_reference_summary",
|
||
"validation_kind": "unrelated_legacy_test",
|
||
"validated_assertions": [
|
||
"divisional_frame_presence_in_summary"
|
||
],
|
||
"not_validated_reason": "receipt does not prove the rule formula: only string wiring / boundary text / unrelated legacy structural assertions observed"
|
||
}
|
||
},
|
||
{
|
||
"admission_state": "validated_reference",
|
||
"assertion_boundary": "does_not_imply_runtime_execution",
|
||
"implementation_targets": [
|
||
"scripts/dasha_calculator_enhanced.py",
|
||
"tests/test_science_of_light_dasha.py"
|
||
],
|
||
"non_verbatim_rule_summary": "Derive the birth Vimshottari lord and remaining Mahadasha balance from the Moon's exact longitude inside its Nakshatra, including the remaining arc to that Nakshatra's end.",
|
||
"page_locator": "Volume 1 PDF p. 730; printed p. 289, How to calculate Vimshottari Dasha",
|
||
"rule_id": "science_of_light_v1_vimshottari_moon_balance",
|
||
"source_id": "science_of_light_v1",
|
||
"validation": {
|
||
"status": "fixture_passed",
|
||
"test_path": "tests/test_science_of_light_dasha.py::test_science_of_light_bharani_example_uses_exact_moon_longitude",
|
||
"validation_kind": "fixture_numeric",
|
||
"validated_assertions": [
|
||
"nakshatra_name_is_bharani_for_13deg48min_aries",
|
||
"vimshottari_lord_is_venus"
|
||
]
|
||
}
|
||
},
|
||
{
|
||
"admission_state": "candidate_mapped",
|
||
"assertion_boundary": "does_not_imply_runtime_execution",
|
||
"implementation_targets": [
|
||
"scripts/special_lagnas.py",
|
||
"tests/test_science_of_light_hora_lagna.py"
|
||
],
|
||
"non_verbatim_rule_summary": "Use Hora Lagna as a wealth and resource lens, with the second house from it contributing a timing signal; cross-check it with Dasha, transit, and other wealth factors before any conclusion.",
|
||
"page_locator": "Volume 2 PDF pp. 239-240; printed pp. 218-219, Dhana Yogada",
|
||
"rule_id": "science_of_light_v2_hora_lagna_wealth_timing",
|
||
"source_id": "science_of_light_v2",
|
||
"validation": {
|
||
"status": "not_validated",
|
||
"test_path": "tests/test_science_of_light_hora_lagna.py::test_science_of_light_hora_lagna_is_a_cross_checked_timing_lens",
|
||
"validation_kind": "wiring_only",
|
||
"validated_assertions": [
|
||
"source_reference_packets_field_wiring",
|
||
"interpretation_boundary_text"
|
||
],
|
||
"not_validated_reason": "receipt does not prove the rule formula: only string wiring / boundary text / unrelated legacy structural assertions observed"
|
||
}
|
||
},
|
||
{
|
||
"admission_state": "candidate_mapped",
|
||
"assertion_boundary": "does_not_imply_runtime_execution",
|
||
"implementation_targets": [
|
||
"mcp_server.py",
|
||
"references/strict-workflow-router.md",
|
||
"tests/test_mcp_strict_workflow_relationship.py"
|
||
],
|
||
"non_verbatim_rule_summary": "Use complementary Dasha frames for timing context instead of treating one Dasha system as sufficient on its own; retain the systems' distinct roles.",
|
||
"page_locator": "Volume 2 PDF pp. 10-11; printed pp. viii-ix, Naisargika Dasa chapter framing",
|
||
"rule_id": "science_of_light_v2_multi_dasha_crosscheck",
|
||
"source_id": "science_of_light_v2",
|
||
"validation": {
|
||
"status": "not_validated",
|
||
"test_path": "tests/test_mcp_strict_workflow_relationship.py::test_relationship_strict_contract_exposes_adjudication_stages_and_multi_reference_summary",
|
||
"validation_kind": "unrelated_legacy_test",
|
||
"validated_assertions": [
|
||
"multi_reference_reading_summary_frame_presence"
|
||
],
|
||
"not_validated_reason": "receipt does not prove the rule formula: only string wiring / boundary text / unrelated legacy structural assertions observed"
|
||
}
|
||
},
|
||
{
|
||
"admission_state": "candidate_mapped",
|
||
"assertion_boundary": "does_not_imply_runtime_execution",
|
||
"implementation_targets": [
|
||
"mcp_server.py",
|
||
"references/strict-workflow-router.md",
|
||
"tests/test_mcp_strict_workflow_relationship.py"
|
||
],
|
||
"non_verbatim_rule_summary": "Interpret Rashi Dasha through the active sign's lord, aspects, planetary condition, Arudha/Ashtakavarga and other relevant factors; do not reduce the period to the sign label or the running Dasha alone.",
|
||
"page_locator": "Volume 2 PDF p. 280; printed p. 259, Rashi Dasha discussion",
|
||
"rule_id": "science_of_light_v2_rashi_dasha_condition_crosscheck",
|
||
"source_id": "science_of_light_v2",
|
||
"validation": {
|
||
"status": "not_validated",
|
||
"test_path": "tests/test_mcp_strict_workflow_relationship.py::test_relationship_strict_contract_exposes_adjudication_stages_and_multi_reference_summary",
|
||
"validation_kind": "unrelated_legacy_test",
|
||
"validated_assertions": [
|
||
"multi_reference_reading_summary_frame_presence"
|
||
],
|
||
"not_validated_reason": "receipt does not prove the rule formula: only string wiring / boundary text / unrelated legacy structural assertions observed"
|
||
}
|
||
},
|
||
{
|
||
"admission_state": "candidate_mapped",
|
||
"assertion_boundary": "does_not_imply_runtime_execution",
|
||
"implementation_targets": [
|
||
"references/raman-house-judgment-methodology.md",
|
||
"references/event_judgment_marriage.md",
|
||
"references/strict-workflow-router.md",
|
||
"tests/test_mcp_strict_workflow_relationship.py"
|
||
],
|
||
"non_verbatim_rule_summary": "Judge marriage and seventh-house matters through the seventh house itself, its lord, Venus as karaka, occupants and associations; retain whole-chart and Navamsa strength checks before applying any placement rule.",
|
||
"page_locator": "How to Judge a Horoscope Vol. 2 transcription rendered pp. 8-12; Concerning the Seventh House, Main Considerations and placement cautions",
|
||
"rule_id": "raman_horoscope_v2_seventh_house_house_lord_karaka_method",
|
||
"source_id": "raman_horoscope_v2",
|
||
"validation": {
|
||
"status": "not_validated",
|
||
"test_path": "tests/test_mcp_strict_workflow_relationship.py::test_relationship_strict_contract_exposes_adjudication_stages_and_multi_reference_summary",
|
||
"validation_kind": "boundary_text",
|
||
"validated_assertions": [
|
||
"relationship_route_exposes_multi_layer_method_boundary"
|
||
],
|
||
"not_validated_reason": "receipt does not prove a formula: locator supports a methodology boundary only; requires future case-calibrated tests before runtime promotion"
|
||
}
|
||
},
|
||
{
|
||
"admission_state": "candidate_mapped",
|
||
"assertion_boundary": "does_not_imply_runtime_execution",
|
||
"implementation_targets": [
|
||
"references/raman-house-judgment-methodology.md",
|
||
"references/event_judgment_marriage.md",
|
||
"tests/test_mcp_strict_workflow_relationship.py"
|
||
],
|
||
"non_verbatim_rule_summary": "A well-placed seventh lord in the seventh house can be read as supportive for alliance, spouse quality and public relational magnetism; weakness or affliction can reverse the result, so dignity and condition must be adjudicated first.",
|
||
"page_locator": "How to Judge a Horoscope Vol. 2 transcription rendered pp. 10-12; seventh lord in seventh house and whole-chart caution",
|
||
"rule_id": "raman_horoscope_v2_seventh_lord_in_seventh_conditioned_result",
|
||
"source_id": "raman_horoscope_v2",
|
||
"validation": {
|
||
"status": "not_validated",
|
||
"test_path": "tests/test_mcp_strict_workflow_relationship.py::test_relationship_strict_contract_exposes_adjudication_stages_and_multi_reference_summary",
|
||
"validation_kind": "boundary_text",
|
||
"validated_assertions": [
|
||
"relationship_route_exposes_conditioned_interpretation_boundary"
|
||
],
|
||
"not_validated_reason": "receipt does not prove a formula: this is a conditional interpretive rule and needs case-calibrated validation before runtime promotion"
|
||
}
|
||
},
|
||
{
|
||
"admission_state": "candidate_mapped",
|
||
"assertion_boundary": "does_not_imply_runtime_execution",
|
||
"implementation_targets": [
|
||
"references/strict-workflow-router.md",
|
||
"references/vimshottari_dasha_guide.md",
|
||
"references/dasa-convergence-methodology.md",
|
||
"tests/test_mcp_strict_workflow_relationship.py"
|
||
],
|
||
"non_verbatim_rule_summary": "Do not judge Saturn-Venus or Venus-Saturn periods by stock benefic/malefic labels; assess the planets functional roles, divisional links, sub-sub periods, transits and event context, including mixed success and pressure signatures.",
|
||
"page_locator": "Learn Successful Predictive Techniques transcription rendered pp. 7, 26, 50-52; replication, dasha caution and Saturn-Venus examples",
|
||
"rule_id": "rao_predictive_techniques_saturn_venus_contextual_dasha_method",
|
||
"source_id": "rao_predictive_techniques",
|
||
"validation": {
|
||
"status": "not_validated",
|
||
"test_path": "tests/test_mcp_strict_workflow_relationship.py::test_relationship_strict_contract_exposes_adjudication_stages_and_multi_reference_summary",
|
||
"validation_kind": "boundary_text",
|
||
"validated_assertions": [
|
||
"multi_reference_reading_summary_frame_presence"
|
||
],
|
||
"not_validated_reason": "receipt does not prove a formula: contextual dasha interpretation requires future event holdout or case-calibrated receipts"
|
||
}
|
||
},
|
||
{
|
||
"admission_state": "candidate_mapped",
|
||
"assertion_boundary": "does_not_imply_runtime_execution",
|
||
"implementation_targets": [
|
||
"references/strict-workflow-router.md",
|
||
"references/dasa-convergence-methodology.md",
|
||
"references/jaimini-complete-system.md",
|
||
"tests/test_mcp_strict_workflow_relationship.py"
|
||
],
|
||
"non_verbatim_rule_summary": "Use Parashari and Jaimini as independent cross-checking frames for major-event timing, then require transit support and accurate birth-time sensitivity notes before distinguishing eligible periods from likely manifestation periods.",
|
||
"page_locator": "Predicting Major Life Events transcription rendered pp. 11-12 and 31-32; method overview, birth-time caution and composite technique",
|
||
"rule_id": "boney_major_life_events_composite_parashari_jaimini_timing",
|
||
"source_id": "boney_major_life_events",
|
||
"validation": {
|
||
"status": "not_validated",
|
||
"test_path": "tests/test_mcp_strict_workflow_relationship.py::test_relationship_strict_contract_exposes_adjudication_stages_and_multi_reference_summary",
|
||
"validation_kind": "boundary_text",
|
||
"validated_assertions": [
|
||
"multi_reference_reading_summary_frame_presence"
|
||
],
|
||
"not_validated_reason": "receipt does not prove a formula: this packet is a methodology admission only until cross-system case calibration is added"
|
||
}
|
||
},
|
||
{
|
||
"rule_id": "jaimini_seventh_from_karakamsha_marriage",
|
||
"source_id": "web:jaimini_seventh_from_kl",
|
||
"source_type": "web_reference",
|
||
"source_url": "https://jagannathhora.com/atmakaraka-darakaraka-together-spouse-soul-integration/",
|
||
"supporting_source_urls": [
|
||
"https://astrologicalmusings.com/jaimini-astrology-and-marriage/"
|
||
],
|
||
"page_locator": "web page section 'The Karakamsa Lagna and the 7th from KL'",
|
||
"admission_state": "reference_only",
|
||
"assertion_boundary": "Modern exposition, not a corpus verbatim passage. The repo corpus defines Karakamsha (69 hits on 'karakamsa') but never joins it to marriage. Treat as a candidate-parameter only until a classical page image is cited.",
|
||
"non_verbatim_rule_summary": "Put the sign that the Atmakaraka occupies in the Navamsha as a derived lagna (Karakamsha Lagna). The 7th house from that derived lagna is read for the spouse. Benefics there favour the partnership channel; malefics without cancellation indicate a challenging channel. This is stated as an additional Jaimini marriage parameter alongside Darakaraka, Darapada and Upapada.",
|
||
"implementation_targets": [
|
||
"reference-only: no formula admitted",
|
||
"requires ATMAKARAKA_D9_SIGN then 7th-from-sign arithmetic"
|
||
],
|
||
"repo_check": {
|
||
"query": "seventh from Karakamsha",
|
||
"hits": 0,
|
||
"queries_also_zero": [
|
||
"Karakamsha marriage"
|
||
],
|
||
"control_query": {
|
||
"query": "karakamsa",
|
||
"hits": 69
|
||
},
|
||
"verdict": "not_detected_in_corpus"
|
||
},
|
||
"intake_record": "references/web_rule_intake_2026_10_06.json",
|
||
"validation": {
|
||
"status": "not_validated",
|
||
"validation_kind": "web_reference_only",
|
||
"not_validated_reason": "Web intake: text received and corpus-absence checked, but no formula, no executable wiring and no case holdout. Must not be promoted to a timing conclusion on its own."
|
||
}
|
||
},
|
||
{
|
||
"rule_id": "jaimini_seventh_from_swamsha_marriage",
|
||
"source_id": "web:jaimini_seventh_from_swamsha",
|
||
"source_type": "web_reference",
|
||
"source_url": "https://astrologicalmusings.com/jaimini-astrology-and-marriage/",
|
||
"supporting_source_urls": [],
|
||
"page_locator": "web page section 'The 7th house from Swamsha'",
|
||
"admission_state": "reference_only",
|
||
"assertion_boundary": "Swamsha itself IS in the corpus (V. P. Goel, Predicting through Jaimini Astrology, line 357 and line 6065: the sign occupied by Atmakaraka in navamsha is called the Swamsha). What is web-only is the specific instruction to read the 7th from Swamsha for marriage. Do not present the word as web-sourced when the definition is corpus-sourced.",
|
||
"non_verbatim_rule_summary": "The sign of the Atmakaraka placed in the Navamsha is Swamsha Lagna; the 7th from Swamsha lagna is also examined for the promise of marriage or relationship.",
|
||
"implementation_targets": [
|
||
"reference-only: no formula admitted",
|
||
"same derived-lagna arithmetic as Karakamsha when AK D9 sign equals the Karakamsha sign"
|
||
],
|
||
"repo_check": {
|
||
"query": "seventh from Swamsha",
|
||
"hits": "not_run_as_such",
|
||
"note": "Swamsha definition verified in corpus at Predicting through Jaimini Astrology (V. P. Goel), lines 357-359 and 6065; the marriage-linkage sentence was not located.",
|
||
"verdict": "definition_in_corpus_linkage_not_detected"
|
||
},
|
||
"intake_record": "references/web_rule_intake_2026_10_06.json",
|
||
"validation": {
|
||
"status": "not_validated",
|
||
"validation_kind": "web_reference_only",
|
||
"not_validated_reason": "Web intake: text received and corpus-absence checked, but no formula, no executable wiring and no case holdout. Must not be promoted to a timing conclusion on its own."
|
||
}
|
||
},
|
||
{
|
||
"rule_id": "upapada_second_from_ul_planet_effects",
|
||
"source_id": "web:upapada_2nd_house_planet_table",
|
||
"source_type": "web_reference",
|
||
"source_url": "https://parasara.net/learn/bphs-ch30-upapada-2nd-ul-marriage-quality-l162",
|
||
"supporting_source_urls": [
|
||
"https://www.sarvatobhadra.com/upapada-lagna-insights-into-marriage-and-spouse",
|
||
"https://www.vedicq.com/en/jaimini-upapada-lagna-marriage"
|
||
],
|
||
"page_locator": "BPHS Ch.30 Upapada verses 1-16 as taught by P.V.R. Narasimha Rao; mirrored by two secondary sites",
|
||
"admission_state": "reference_only",
|
||
"assertion_boundary": "The corpus has the UL-2 CONCEPT with page locators (A course on Jaimini Upadesa Sutra p.325 line 15805, p.476 line 22866; Crux p.232 line 9102, p.245 line 9758, p.246 line 9775, p.270 line 10747). What is web-only is the planet-by-planet consequence table. Classical severity language ('killer of wife') must not be repeated to the user as a prediction; keep it as a symbolic severity grade.",
|
||
"non_verbatim_rule_summary": "The 2nd house from Upapada is the sustenance of the marriage, as the 2nd from Lagna is the food that sustains the body. Judge all influences on it rather than the lord alone: who occupies it, who aspects it in rasi, which navamsha portion that sign falls in, and the natural and functional nature of those planets. A strong 2nd lord or benefic support gives lasting continuity; malefic occupation or malefic aspect gives strain, illness or separation pressure.",
|
||
"implementation_targets": [
|
||
"reference-only: no formula admitted",
|
||
"requires UL sign then +1 sign for UL-2, plus rasi drishti and D9 amsa of that sign"
|
||
],
|
||
"repo_check": {
|
||
"query": "malefic in the second from Upapada",
|
||
"hits": 0,
|
||
"queries_also_zero": [
|
||
"Saturn in the second from Upapada",
|
||
"Upapada Jupiter"
|
||
],
|
||
"control_query": {
|
||
"query": "second from Upapada",
|
||
"hits": 16
|
||
},
|
||
"verdict": "concept_in_corpus_planet_table_not_detected"
|
||
},
|
||
"intake_record": "references/web_rule_intake_2026_10_06.json",
|
||
"validation": {
|
||
"status": "not_validated",
|
||
"validation_kind": "web_reference_only",
|
||
"not_validated_reason": "Web intake: text received and corpus-absence checked, but no formula, no executable wiring and no case holdout. Must not be promoted to a timing conclusion on its own."
|
||
}
|
||
},
|
||
{
|
||
"rule_id": "upapada_and_darakaraka_transit_timing",
|
||
"source_id": "web:upapada_dk_transit_timing",
|
||
"source_type": "web_reference",
|
||
"source_url": "https://bhyrav.com/blog/when-will-i-get-married-according-to-my-horoscope-and-nakshatra",
|
||
"supporting_source_urls": [
|
||
"https://grahasutra.com/marriage-timing-through-upapada-lagna/",
|
||
"https://astronidan.com/blog/marriage-timing-astrology",
|
||
"https://www.indiadivine.org/content/topic/1182387-marriage-and-narayana-dasa-robyn/"
|
||
],
|
||
"page_locator": "web pages, transit-trigger sections",
|
||
"admission_state": "reference_only",
|
||
"assertion_boundary": "No corpus passage was located that links a slow-planet transit to Upapada or to the natal Darakaraka. The in-repo Rao 8-parameter file and the double-transit engine operators do NOT cover this variant. Do not merge this with K.N. Rao's eight-parameter scoring or with the engine's double-transit PAC output; they are separate rule families.",
|
||
"non_verbatim_rule_summary": "Marriage formalisation is reported where transiting Saturn contacts the Upapada Lagna, its lord, or the trines of the lord; and where the natal Darakaraka is aspected by transiting Jupiter, Mars or Saturn. Jupiter transiting the Upapada, the Upapada lord, the 7th house, the 7th lord or the Darakaraka is treated as the opening trigger. The three-tier reading is kept: natal promise, then dasha, then transit as trigger only.",
|
||
"implementation_targets": [
|
||
"reference-only: no formula admitted",
|
||
"would need UL longitude, UL lord, DK longitude as required inputs"
|
||
],
|
||
"repo_check": {
|
||
"query": "Saturn transit Upapada",
|
||
"hits": 0,
|
||
"queries_also_zero": [
|
||
"Saturn aspects Darakaraka",
|
||
"transit Darakaraka",
|
||
"Saturn Upapada marriage"
|
||
],
|
||
"verdict": "not_detected_in_corpus"
|
||
},
|
||
"intake_record": "references/web_rule_intake_2026_10_06.json",
|
||
"validation": {
|
||
"status": "not_validated",
|
||
"validation_kind": "web_reference_only",
|
||
"not_validated_reason": "Web intake: text received and corpus-absence checked, but no formula, no executable wiring and no case holdout. Must not be promoted to a timing conclusion on its own."
|
||
}
|
||
},
|
||
{
|
||
"rule_id": "spouse_meeting_place_via_seventh_from_venus",
|
||
"source_id": "web:meeting_place_7th_from_venus",
|
||
"source_type": "web_reference",
|
||
"source_url": "https://www.indiadivine.org/content/topic/1281978-fwd-upapada-lagna-location-in-chart",
|
||
"supporting_source_urls": [
|
||
"https://celestialdigits.org/blog/spouse-meeting-circumstances-seventh-lord"
|
||
],
|
||
"page_locator": "forum post body, paragraph 2: 'The actual place of meeting the spouse is seen from the seventh lord from Venus'",
|
||
"admission_state": "reference_only",
|
||
"assertion_boundary": "The corpus DOES contain the seventh-from-Venus point, but only as a DAŚĀ-timing rule (Crux p.273 L10855-10857; Science of Light p.861 L20811-20818). The PLACE-of-meeting application of the same point is not detected in the corpus. Do not merge the two usages.",
|
||
"non_verbatim_rule_summary": "Take the seventh sign counted from Venus's natal position. Its nature/sign-lord describes the setting in which the spouse is actually met (overseas vs nearby, a restaurant vs an institution, and so on). Reported as a distinct statement from the daśā-timing use of the same point.",
|
||
"implementation_targets": [
|
||
"reference-only: no formula admitted",
|
||
"derived point already computable: 7th from VENUS_LON"
|
||
],
|
||
"repo_check": {
|
||
"query": "place of meeting",
|
||
"hits": 0,
|
||
"queries_also_zero": [
|
||
"where you meet"
|
||
],
|
||
"control_query": {
|
||
"query": "seventh from Venus",
|
||
"hits": 3
|
||
},
|
||
"control_note": "The 3 hits are daśā-timing uses (Crux p.273, Crux p.155, R G Rao p.86), confirming the point exists in-corpus while the place application does not.",
|
||
"verdict": "not_detected_in_corpus"
|
||
},
|
||
"intake_record": "references/web_rule_intake_2026_10_06_romance.json",
|
||
"validation": {
|
||
"status": "not_validated",
|
||
"validation_kind": "web_reference_only",
|
||
"not_validated_reason": "Romance/meeting intake: text received and corpus-absence checked with controls, but no formula, no executable wiring and no case holdout. Must not be promoted to a timing conclusion on its own."
|
||
}
|
||
},
|
||
{
|
||
"rule_id": "upapada_house_meeting_activity",
|
||
"source_id": "web:upapada_house_activity",
|
||
"source_type": "web_reference",
|
||
"source_url": "https://www.indiadivine.org/content/topic/1281978-fwd-upapada-lagna-location-in-chart",
|
||
"supporting_source_urls": [
|
||
"https://vaya.so/blog/upapada-lagna-ul",
|
||
"https://www.jyotishvidya.co.in/jyotish-gyan/upapada-lagna"
|
||
],
|
||
"page_locator": "forum post body: 'The placement of the Upapada will show which activity you must be doing to find the spouse' + per-house examples (UL in 2nd = family/in-laws; 4th = mother; 9th = college; 10th = work)",
|
||
"admission_state": "reference_only",
|
||
"assertion_boundary": "The corpus defines Upapada (468 hits) and the SECOND-from-Upapada sustenance rule (16 hits), but no Upapada-house -> activity mapping was detected. This is a prescriptive-remedial reading layer, not an event timer. Do not use it to date anything.",
|
||
"non_verbatim_rule_summary": "Read the house occupied by the Upapada as the life-domain in which the native must actually be active for the spouse to appear: UL in 2nd = through family or in-laws; 4th = through the mother / home; 5th = education or creative settings; 6th = workplace or service; 7th = explicitly dating-oriented venues; 9th = higher education / father / guru; 10th = work; 11th = associates or elder siblings; 12th = religious or retreat settings. The remedy form is to engage in that domain's activity.",
|
||
"implementation_targets": [
|
||
"reference-only: no formula admitted",
|
||
"requires UPAPADA_SIGN then house-of-UL from LAGNA"
|
||
],
|
||
"repo_check": {
|
||
"query": "Upapada tenth",
|
||
"hits": 0,
|
||
"queries_also_zero": [
|
||
"Upapada second",
|
||
"Upapada ninth",
|
||
"Upapada fourth",
|
||
"meeting place"
|
||
],
|
||
"control_query": {
|
||
"query": "Upapada",
|
||
"hits": 468
|
||
},
|
||
"control_note": "'meeting place' has 2 hits but both are incidental prose (a worship line in Science of Light; bhajan singers in K.N. Rao), not a doctrine.",
|
||
"verdict": "not_detected_in_corpus"
|
||
},
|
||
"intake_record": "references/web_rule_intake_2026_10_06_romance.json",
|
||
"validation": {
|
||
"status": "not_validated",
|
||
"validation_kind": "web_reference_only",
|
||
"not_validated_reason": "Romance/meeting intake: text received and corpus-absence checked with controls, but no formula, no executable wiring and no case holdout. Must not be promoted to a timing conclusion on its own."
|
||
}
|
||
},
|
||
{
|
||
"rule_id": "first_meeting_scene_seventh_from_seventh_lord",
|
||
"source_id": "web:first_meeting_scene_7th_from_7L",
|
||
"source_type": "web_reference",
|
||
"source_url": "https://celestialdigits.org/blog/spouse-meeting-circumstances-seventh-lord",
|
||
"supporting_source_urls": [],
|
||
"page_locator": "blog section 'The Technique in Three Steps'",
|
||
"admission_state": "reference_only",
|
||
"assertion_boundary": "A modern descriptive technique with no classical citation offered by its own source. Its own author asks that it be treated as 'a descriptive layer on top of serious marriage analysis, not a replacement'. Lowest evidential weight of the four.",
|
||
"non_verbatim_rule_summary": "Find the sign occupied by the 7th lord; then take the sign opposite to it (the 7th from the 7th lord). The symbolism of that target sign (animal, element, colours, venue themes) is said to appear as background detail in the scene of the first meeting.",
|
||
"implementation_targets": [
|
||
"reference-only: no formula admitted",
|
||
"requires SEVENTH_LORD_SIGN then 7th-from-sign arithmetic"
|
||
],
|
||
"repo_check": {
|
||
"query": "first meeting",
|
||
"hits": 3,
|
||
"queries_also_zero": [
|
||
"meeting period"
|
||
],
|
||
"control_query": {
|
||
"query": "Arudha",
|
||
"hits": 1161
|
||
},
|
||
"control_note": "The 3 'first meeting' hits were inspected and are all incidental narrative (a condescending first meeting; muhurta mutual liking; a biographer's first meeting). No scene-reading doctrine.",
|
||
"verdict": "not_detected_in_corpus"
|
||
},
|
||
"intake_record": "references/web_rule_intake_2026_10_06_romance.json",
|
||
"validation": {
|
||
"status": "not_validated",
|
||
"validation_kind": "web_reference_only",
|
||
"not_validated_reason": "Romance/meeting intake: text received and corpus-absence checked with controls, but no formula, no executable wiring and no case holdout. Must not be promoted to a timing conclusion on its own."
|
||
}
|
||
},
|
||
{
|
||
"rule_id": "spouse_direction_planet_and_house",
|
||
"source_id": "web:spouse_direction_tables",
|
||
"source_type": "web_reference",
|
||
"source_url": "https://www.astroword.in/blog/where-will-i-meet-my-spouse-direction-location-astrology",
|
||
"supporting_source_urls": [
|
||
"https://astropower.co.in/blog/spouse-direction-partner-prediction"
|
||
],
|
||
"page_locator": "sections 'Level 1: Planetary Direction Table' and 'Level 2: Distance'",
|
||
"admission_state": "reference_only",
|
||
"assertion_boundary": "No classical page image is cited by the source for the direction table. The repo does not contain a spouse-direction system. Treat purely as a descriptive parameter; never feed it into a timing window.",
|
||
"non_verbatim_rule_summary": "Two stacked tables: (a) each planet carries a compass direction (Sun=E, Moon=NW, Mars=S, Mercury=N, Jupiter=NE, Venus=SE, Saturn=W, Rahu=SW, Ketu=S in the source's own table); (b) the house occupied by the 7th lord indicates distance and circumstance (1st=neighbourhood, 9th=far/foreign, 12th=foreign, 11th=social network, and so on). Where the 7th lord's direction and the Darakaraka's direction agree the reading is treated as stronger.",
|
||
"implementation_targets": [
|
||
"reference-only: no formula admitted",
|
||
"requires 7L_PLANET, 7L_HOUSE, DK_PLANET"
|
||
],
|
||
"repo_check": {
|
||
"query": "spouse direction",
|
||
"hits": 0,
|
||
"queries_also_zero": [
|
||
"direction of spouse",
|
||
"meeting circumstances",
|
||
"Darakaraka house"
|
||
],
|
||
"control_query": {
|
||
"query": "compass direction",
|
||
"hits": 2
|
||
},
|
||
"control_note": "'compass direction' has 2 hits (Light on Life, on the direction a person faces) — unrelated to spouse direction.",
|
||
"verdict": "not_detected_in_corpus"
|
||
},
|
||
"intake_record": "references/web_rule_intake_2026_10_06_romance.json",
|
||
"validation": {
|
||
"status": "not_validated",
|
||
"validation_kind": "web_reference_only",
|
||
"not_validated_reason": "Romance/meeting intake: text received and corpus-absence checked with controls, but no formula, no executable wiring and no case holdout. Must not be promoted to a timing conclusion on its own."
|
||
}
|
||
},
|
||
{
|
||
"rule_id": "nakshatra_rising_facial_appearance_ashlesha",
|
||
"source_id": "web:ashlesha_rising_facial",
|
||
"source_type": "web_reference",
|
||
"source_url": "http://dev.dkscore.com/jyotishmedium/ashlesha-nakshatra-by-prash-trivedi-301",
|
||
"supporting_source_urls": [
|
||
"https://www.astrosharmistha.com/?p=1982"
|
||
],
|
||
"page_locator": "Prash Trivedi, Ashlesha chapter, the 'Ashlesha rising gives ...' sentence; the same sentence appears verbatim on the AstroSharmistha Ashlesha pada page",
|
||
"admission_state": "reference_only",
|
||
"assertion_boundary": "Modern nakshatra exposition republished across two independent astrology sites; no classical page image was cited by either source. Appearance descriptors only; no behaviour, timing or event content. Must not be used to eliminate a candidate minute on its own, and must not be used to overwrite a recorded_time.",
|
||
"non_verbatim_rule_summary": "When Ashlesha is rising the sources describe a squarish face; parallel, straight and wide thin lips; beady small eyes; a naturally suspicious look; and a pale complexion, alongside a sexually appealing body and snake-like movement.",
|
||
"implementation_targets": [
|
||
"reference-only: no formula admitted",
|
||
"question-selection material for the appearance domain only",
|
||
"requires the candidate chart's lagna nakshatra to be computed first"
|
||
],
|
||
"repo_check": {
|
||
"query": "squarish",
|
||
"hits": 0,
|
||
"queries_also_zero": [
|
||
"beady"
|
||
],
|
||
"queries_with_hits_checked": [
|
||
{
|
||
"query": "thin lips",
|
||
"hits": 1,
|
||
"inspected": "single hit is Deva Keralam (Chandra Kala Nadi) Vol.2 p.90 L7321 describing a yoga, not a rising-nakshatra face rule"
|
||
},
|
||
{
|
||
"query": "Ashlesha rising",
|
||
"hits": 4,
|
||
"inspected": "all four hits are Light on Life (de Fouw/Svoboda) p.250 L8472 and pp.391-392 L13577/L13618, which give behavioural descriptors (blunt character; secret intrigue and manipulation; insight and wisdom coupled with painful separations) and named natives, not facial descriptors"
|
||
},
|
||
{
|
||
"query": "complexion",
|
||
"hits": 126,
|
||
"inspected": "not exhaustively inspected; no facial-bundle rule located in the sampled hits"
|
||
}
|
||
],
|
||
"control_query": {
|
||
"query": "Arudha",
|
||
"hits": 1161
|
||
},
|
||
"control_note": "The control confirms the search path is live, so the zero counts above are query-level non-detection rather than a broken index.",
|
||
"verdict": "facial_bundle_not_detected_in_corpus"
|
||
},
|
||
"intake_record": "references/web_rule_intake_2026_10_07.json",
|
||
"validation": {
|
||
"status": "not_validated",
|
||
"validation_kind": "web_reference_only",
|
||
"not_validated_reason": "Appearance-domain web intake: text received and corpus-absence checked with a live control, but no classical page image, no executable wiring and no dated hidden-case holdout. Cannot be promoted to a decisive orientation on its own."
|
||
}
|
||
},
|
||
{
|
||
"rule_id": "nakshatra_rising_facial_appearance_pushya",
|
||
"source_id": "web:pushya_rising_facial",
|
||
"source_type": "web_reference",
|
||
"source_url": "https://archive.org/download/astrology-book-collection/The%20Real%20Secret%20of%20Vedic%20Astrology_Nakshatras_Acharya%20Bharat.pdf",
|
||
"supporting_source_urls": [
|
||
"http://www.nammamatchmaker.com/home/astro_tips"
|
||
],
|
||
"page_locator": "Acharya Bharat, The Real Secret of Vedic Astrology, nakshatra chapters 8 (Pushya) and 9 (Ashlesha), 'When this star is on the ascendant ...' paragraphs; nammamatchmaker 'Astro Tips' Pushya section",
|
||
"admission_state": "reference_only",
|
||
"assertion_boundary": "One public-domain-style downloadable compilation plus one low-tier commercial astrology page; no classical page image was cited. Body/face and character descriptors only. The same source also labels Pushya the best of the 27 stars and Ashlesha a rakshasa star, which is doctrinal colouring rather than a measurable test and must not be quoted at a client.",
|
||
"non_verbatim_rule_summary": "With Pushya on the ascendant the sources describe a well-built or plump body and a round, bright face with a gentle appearance, together with an earnest, thoughtful and religious character. The commercial page adds a muscular full frame and a round bright face.",
|
||
"implementation_targets": [
|
||
"reference-only: no formula admitted",
|
||
"question-selection material for the appearance domain only",
|
||
"requires the candidate chart's lagna nakshatra to be computed first"
|
||
],
|
||
"repo_check": {
|
||
"query": "plump",
|
||
"hits": 4,
|
||
"queries_also_zero": [],
|
||
"queries_with_hits_checked": [
|
||
{
|
||
"query": "round face",
|
||
"hits": 3,
|
||
"inspected": "sampled hits do not form a rising-nakshatra face rule"
|
||
},
|
||
{
|
||
"query": "Pushya",
|
||
"hits": 362,
|
||
"inspected": "sampled hits are pada boundaries, dasha context and nakshatra lists (e.g. A Manual of Hindu Astrology, B V Raman, p.96 L779 gives the Pushya/Aslesha boundary degrees), not a rising-nakshatra body-and-face rule"
|
||
}
|
||
],
|
||
"control_query": {
|
||
"query": "Arudha",
|
||
"hits": 1161
|
||
},
|
||
"control_note": "Same live control as the Ashlesha packet.",
|
||
"verdict": "body_and_face_bundle_not_detected_in_corpus"
|
||
},
|
||
"intake_record": "references/web_rule_intake_2026_10_07.json",
|
||
"validation": {
|
||
"status": "not_validated",
|
||
"validation_kind": "web_reference_only",
|
||
"not_validated_reason": "Appearance-domain web intake: text received and corpus-absence checked with a live control, but no classical page image, no executable wiring and no dated hidden-case holdout. Cannot be promoted to a decisive orientation on its own."
|
||
}
|
||
}
|
||
]
|
||
}
|