Files
Jyotisha/references/interpretation_template_registry.json
T

424 lines
20 KiB
JSON

{
"schema_version": 1,
"scope": "jyotish_interpretation_template_registry",
"purpose": "Skill-level high-granularity interpretation templates distilled from local references and user-supplied article clues. These templates are guarded by source levels, cross-checks, confidence ceilings and forbidden claims.",
"global_rules": [
"Do not turn online article claims into hard predictions without D1/Varga/Dasha/Transit cross-checks.",
"Use these templates after the strict workflow router has established the relevant promise and timing layer.",
"Keep personal user data out of persistent skill files and public repositories.",
"Treat JHora/PyJHora as external oracle sources only; do not copy incompatible licensed implementations."
],
"templates": {
"yogi_asc_tight_orb_wealth": {
"title": "Yogi Point / Ascendant Degree / Tight Orb Wealth Activation",
"status": "frozen_template",
"authority_level": "A/B/C layered",
"domain": ["wealth", "lagna", "panchanga", "tight_orb"],
"source_refs": [
"references/yogi-asc-tight-orb-wealth-freeze-guide.md",
"references/yogi-avayogi-system.md",
"scripts/aspects.py",
"scripts/special_lagnas.py"
],
"trigger_patterns": [
"财富点",
"吉祥天女财富点",
"Yogi Point",
"上升点度数定位",
"紧密合相",
"1度内合相"
],
"required_cross_checks": [
"D1 wealth promise: 2H/11H/5H/9H and their lords",
"Dhana/Lakshmi Yoga and Jupiter/Venus support",
"D2, D9 and D10 confirmation when wealth is career-linked",
"Dasha and transit activation of Yogi planet, Duplicate Yogi or wealth lords",
"Avayogi damage check before upgrading confidence"
],
"confidence_ceiling": "B unless wealth promise, varga support and timing activation all agree; C when only Yogi/tight-orb signal exists.",
"forbidden_claims": [
"Yogi Point conjunct Lagna guarantees wealth",
"A tight orb alone proves millionaire status",
"Gemstone/remedy guarantees money"
],
"safe_output_patterns": [
"Yogi Point can refine the prosperity activation channel after the main wealth promise is established.",
"A <1° contact is a sensitivity amplifier, not an independent wealth promise.",
"Avayogi contacts should be framed as leakage or friction to manage, not fatalism."
]
},
"ashwini_talent_profile": {
"title": "Ashwini / Ketu Nakshatra Talent And Action Style",
"status": "frozen_template",
"authority_level": "A/B/C layered",
"domain": ["nakshatra", "talent", "career", "muhurta"],
"source_refs": [
"references/ashwini-abhijit-ketu-nakshatra-freeze-guide.md",
"references/nakshatra_deities.md",
"references/nakshatra-chinese-quick-ref.md",
"scripts/kalachakra_dasha.py"
],
"trigger_patterns": [
"娄宿",
"Ashwini",
"Ketu星宿",
"天赋特征",
"Abhijit",
"快速启动"
],
"required_cross_checks": [
"Placement of Moon, Lagna, Sun, AK, AmK, 10L or 1L in Ashwini/Magha/Mula",
"Ketu condition, dispositor and Dasha activation",
"Mars condition because Ashwini is in Aries",
"D9, D10 and D24 support for talent-to-career conversion",
"Panchanga context for electional use"
],
"confidence_ceiling": "B for career style when D10/Dasha support exists; C for personality color only.",
"forbidden_claims": [
"Ashwini alone makes someone a doctor",
"Ashwini guarantees wealth or spiritual status",
"Ketu nakshatra days are always bad"
],
"safe_output_patterns": [
"Ashwini favors quick response, repair, healing, mobility and pioneer behavior when the chart supports it.",
"Ketu nakshatra days are task-sensitive: useful for cutting, repair and root-work; cautious for pure stability commitments.",
"Abhijit is mainly an electional support window, not a standalone natal destiny marker."
]
},
"rtn_high_order_d9": {
"title": "Rashi Tulya Navamsa And High-Order D9 Anomaly Reading",
"status": "frozen_template",
"authority_level": "A/B/C layered",
"domain": ["d9", "navamsa", "relationship", "deep_motive"],
"source_refs": [
"references/rtn-high-order-d9-freeze-execution-guide.md",
"references/rashi-tulya-navamsa-root-impulse.md",
"references/high-order-d9-execution-guide.md",
"scripts/rashi_tulya_navamsa.py"
],
"trigger_patterns": [
"RTN",
"Rashi Tulya Navamsa",
"高阶D9",
"D9异象",
"Navamsa返照"
],
"required_cross_checks": [
"Standard D1 and D9 promise first",
"Vargottama and Pushkara check before RTN weighting",
"D9 7L, Venus/Jupiter, DK and D9 Lagna condition",
"Mapped D1 house condition and event-relevant Varga",
"Dasha/transit activation before event claims"
],
"confidence_ceiling": "B for motive/inner-pattern interpretation; C for timing unless Dasha and event Varga agree.",
"forbidden_claims": [
"RTN alone proves divorce, death or disaster",
"Yama/Preta/Pisacha labels can be used as deterministic outcomes",
"D9 anomaly overrides D1 promise"
],
"safe_output_patterns": [
"RTN explains how Navamsa motives project into D1 life fields.",
"High-order D9 anomalies are warnings that require timing confirmation.",
"Use RTN as a depth layer after ordinary D1/D9 analysis, not as the first judgment."
]
},
"bhrigu_pada_all_event": {
"title": "Bhrigu Pada / Arudha Pada All-Event Progression Template",
"status": "frozen_template",
"authority_level": "A/B/C layered",
"domain": ["arudha", "bhrigu", "event", "timing"],
"source_refs": [
"references/bhrigu-pada-all-event-freeze-execution-guide.md",
"references/bhrigu-pada-dasha-marriage-counting.md",
"scripts/bhrigu_pada_dasha.py",
"scripts/jaimini.py",
"scripts/special_lagnas.py"
],
"trigger_patterns": [
"Bhrigu Pada",
"Arudha Pada",
"A10",
"A2",
"UL",
"全事件推进"
],
"required_cross_checks": [
"D1 promise for the event domain",
"Select correct Pada: A2/A5/A7/A8/A10/A11/UL",
"Pada lord condition and relevant Varga",
"Vimshottari/Chara/transit convergence",
"Past-event verification before personal rule upgrade"
],
"confidence_ceiling": "B as auxiliary event confirmation; C if used without Dasha/transit convergence.",
"forbidden_claims": [
"Bhrigu Pada Dasha alone proves an event",
"A single progression proves exact date",
"Marriage-counting rules can be generalized to all charts without verification"
],
"safe_output_patterns": [
"Use the relevant Arudha Pada to identify how an event becomes visible in the world.",
"Treat Bhrigu Pada as a confirmation/progression layer, not a standalone prediction engine.",
"Upgrade only after Dasha, transit and event Varga agree."
]
},
"tithi_lord_relationship": {
"title": "Tithi Lord Relationship And Emotional Rhythm Template",
"status": "frozen_template",
"authority_level": "B/C guarded",
"domain": ["tithi", "relationship", "moon_sun", "panchanga"],
"source_refs": [
"references/tithi-lord-freeze-execution-guide.md",
"references/tithi-lord-relationship-system.md"
],
"trigger_patterns": [
"Tithi Lord",
"月相主",
"关系节奏",
"情绪周期"
],
"required_cross_checks": [
"D1/D9 relationship promise",
"Moon, Venus/Jupiter and 7L condition",
"Dasha activation of Tithi lord or relationship significators",
"Transit Moon/Jupiter/Saturn trigger only inside supported windows"
],
"confidence_ceiling": "C for standalone relationship judgment; B only when D1/D9/Dasha agree.",
"forbidden_claims": [
"Tithi Lord alone decides marriage fate",
"One lunar-day trait proves compatibility"
],
"safe_output_patterns": [
"Tithi Lord can describe emotional rhythm and response style after relationship promise is checked.",
"Use it to refine timing texture, not to replace 7H/D9/Dasha."
]
},
"pancha_pakshi_swara_boundary": {
"title": "Pancha Pakshi / Swara Boundary Template",
"status": "covered_template",
"authority_level": "B/C guarded",
"domain": ["tamil", "muhurta", "panchanga", "action_timing"],
"source_refs": [
"references/pancha-pakshi-nakshatra-systems.md"
],
"trigger_patterns": [
"Pancha Pakshi",
"五鸟",
"Swara",
"行动窗口",
"择时细节"
],
"required_cross_checks": [
"Primary Muhurta factors: Tithi, Vara, Nakshatra, Yoga, Karana",
"Moon strength and Tarabala/Chandrabala when available",
"Natal Dasha/transit relevance for personal actions",
"Avoid replacing core Muhurta with Pakshi/Swara alone"
],
"confidence_ceiling": "C as auxiliary electional texture; B only with full Muhurta support.",
"forbidden_claims": [
"Pakshi/Swara alone makes a time auspicious",
"One folk-timing layer overrides bad Moon or Dasha"
],
"safe_output_patterns": [
"Use Pakshi/Swara as a final action-timing refinement after ordinary Muhurta checks.",
"Frame weak Pakshi/Swara periods as caution or lower efficiency, not unavoidable failure."
]
},
"lakshmi_dhana_activation_chain": {
"title": "Lakshmi Yoga / Dhana Yoga / Wealth Activation Chain",
"status": "frozen_template",
"authority_level": "A/B/C layered",
"domain": ["wealth", "yoga", "dhana", "timing"],
"source_refs": [
"references/consultation-case-library.md",
"references/yogi-asc-tight-orb-wealth-freeze-guide.md",
"references/modern-language-guide.md",
"docs/research/high_granularity_technique_deepening_backlog_2026_06_26.md"
],
"trigger_patterns": [
"Lakshmi Yoga",
"吉祥天女瑜伽",
"Dhana Yoga",
"财富格局",
"财富激活链",
"wealth activation"
],
"required_cross_checks": [
"D1 wealth promise through 2H, 11H, 5H, 9H, 10H and their lords",
"Lakshmi Yoga / Dhana Yoga / Raja Yoga overlap and benefic support",
"D2, D9 and D10 confirmation for asset, merit and career monetization",
"Shadbala, Ashtakavarga and dignity support before upgrading confidence",
"Dasha, transit and annual activation before claiming a wealth window"
],
"confidence_ceiling": "B unless promise, divisional support and timing all agree; C when only one wealth yoga or article-style signal is present.",
"forbidden_claims": [
"Lakshmi Yoga alone guarantees great wealth",
"Dhana Yoga alone proves millionaire status",
"A single wealth yoga overrides weak houses, weak D2 or hostile Dasha"
],
"safe_output_patterns": [
"Treat Lakshmi and Dhana Yogas as wealth potential that still needs divisional support and timing activation.",
"Explain whether wealth comes through career, luck, family, assets or patronage rather than only saying rich/not rich.",
"If Avayogi, weak D2 or hostile Dasha interferes, frame the result as delayed or effort-heavy wealth rather than denial or guarantee."
]
},
"darakaraka_ul_spouse_depth": {
"title": "Darakaraka / Upapada / D9 Spouse Depth Template",
"status": "frozen_template",
"authority_level": "A/B/C layered",
"domain": ["relationship", "jaimini", "d9", "spouse"],
"source_refs": [
"references/relationship-astrology-guide.md",
"references/navamsa-marriage-deep-analysis.md",
"references/varga-system-quick-reference.md",
"references/prediction-boundary-protocol.md"
],
"trigger_patterns": [
"Darakaraka",
"DK",
"Upapada",
"UL",
"配偶深层特质",
"spouse profile"
],
"required_cross_checks": [
"D1 seventh house, seventh lord and classical spouse significators first",
"D9 seventh house, D9 lagna, Venus/Jupiter and DK condition",
"UL sign, UL lord and second-from-UL support",
"Declare DK system ambiguity when 7-karaka and 8-karaka methods disagree",
"Dasha, transit and relationship timing support before event or marriage timing claims"
],
"confidence_ceiling": "B for spouse profile when D1, D9, DK and UL converge; C when only one Jaimini indicator is active or DK method is disputed.",
"forbidden_claims": [
"DK alone proves the spouse type",
"UL alone guarantees marriage outcome",
"A single DK or UL signal alone predicts divorce, widowhood or exact marriage fate"
],
"safe_output_patterns": [
"Use DK to describe the spouse archetype, UL to describe the visible marriage narrative, and D9 to describe the lived marriage quality.",
"If DK methods disagree, weaken DK and let D1 seventh house plus Venus/Jupiter lead the interpretation.",
"Upgrade only when D1 promise, D9 support, UL condition and timing all point in the same direction."
]
},
"natural_malefic_functional_role_guardrail": {
"title": "Natural Malefic vs Functional Role Guardrail",
"status": "frozen_template",
"authority_level": "A/B/C layered",
"domain": ["interpretation_boundary", "functional_role", "saturn", "mars", "rahu", "ketu"],
"source_refs": [
"AGENTS.md",
"SKILL.md",
"references/prediction-boundary-protocol.md",
"docs/research/malefic_overread_top10_2026_06_27.md"
],
"trigger_patterns": [
"Saturn negative",
"Mars negative",
"Rahu negative",
"Ketu negative",
"功能性吉凶星",
"自然凶星",
"Rahu/Ketu 负面",
"土星是不是坏",
"火星是不是坏"
],
"required_cross_checks": [
"Separate natural benefic/malefic status from functional role under the current Lagna",
"State the topic-domain role before giving any positive or negative conclusion",
"Check D1 promise plus the relevant Varga before calling the planet harmful or helpful",
"Check Dasha/Transit activation before upgrading from trait to event claim",
"For Rahu/Ketu, declare node mode/dispositor and evaluate both breakthrough and loss patterns"
],
"confidence_ceiling": "B when natural role, functional role, topic-domain role and timing all agree; C when only natural malefic language is available or the functional role is unresolved.",
"forbidden_claims": [
"Saturn alone means failure",
"Mars alone means relationship destruction",
"Rahu or Ketu alone proves damage, scandal or collapse",
"A natural malefic label alone overrides functional role, D1 promise or timing"
],
"safe_output_patterns": [
"Always describe the planet in four layers: natural nature, functional role, topic-domain role and current activated outcome.",
"Frame Saturn as delay, responsibility, structure or long-cycle payoff depending on promise and activation, not as automatic negativity.",
"Frame Mars as conflict, execution, surgery, competition or entrepreneurial drive depending on context, not as automatic damage.",
"Frame Rahu and Ketu as dual-edge amplifiers that can produce breakthrough, disruption, detachment or leakage depending on promise, dispositor and activation.",
"If natural and functional meanings conflict, explicitly lower confidence and let the promise/timing layer decide the practical reading."
]
},
"pushkara_vargottama_avastha_synthesis": {
"title": "Pushkara / Vargottama / Avastha / RTN Synthesis Template",
"status": "frozen_template",
"authority_level": "A/B/C layered",
"domain": ["deep_varga", "d9", "avastha", "motivation"],
"source_refs": [
"references/deep-varga-avastha-execution-guide.md",
"references/high-order-d9-execution-guide.md",
"references/rtn-high-order-d9-freeze-execution-guide.md",
"references/strict-workflow-router.md"
],
"trigger_patterns": [
"Pushkara",
"Vargottama",
"Avastha",
"RTN",
"高阶D9联动",
"深分盘状态"
],
"required_cross_checks": [
"D1 promise and event-relevant houses/lords first",
"D9 dignity, reversal and relationship to the D1 promise",
"Avastha states used as delivery-capacity modifiers rather than standalone verdicts",
"Pushkara and Vargottama treated as protection/consistency weighting only",
"RTN, D24, D30 or D60 used only after Dasha and transit confirm the active topic"
],
"confidence_ceiling": "B when natal promise, D9 support, avastha delivery state and timing all converge; C when the pattern is only a high-order explanatory layer.",
"forbidden_claims": [
"Pushkara or Vargottama alone guarantees the event",
"A single avastha state alone proves success or failure",
"RTN or D60 alone can override the main D1 promise or produce exact timing"
],
"safe_output_patterns": [
"Use Pushkara and Vargottama to explain why a promise is preserved, stabilized or slightly protected rather than guaranteed.",
"Use avastha to describe whether the relevant planet is awake enough to deliver its promise cleanly, with weak states framed as drag or uneven expression.",
"Use RTN and deep varga layers to describe motive, background pressure or hidden developmental themes after the main promise and timing are already established."
]
},
"asc_degree_nakshatra_pada_personality": {
"title": "Ascendant Degree / Nakshatra / Pada Personality And Rectification Template",
"status": "frozen_template",
"authority_level": "A/B/C layered",
"domain": ["lagna", "nakshatra", "pada", "rectification"],
"source_refs": [
"references/birth-time-rectification-advanced.md",
"references/nakshatra-chinese-quick-ref.md",
"references/pdf-chart-reading-guide.md",
"docs/research/high_granularity_technique_deepening_backlog_2026_06_26.md"
],
"trigger_patterns": [
"上升点度数",
"Lagna degree",
"Asc degree",
"Ascendant Pada",
"上升星宿",
"出生时间矫正"
],
"required_cross_checks": [
"Validate ascendant degree against the actual sign, nakshatra and pada boundaries before any interpretation",
"Separate sign-level Lagna expression from nakshatra-level style and pada-level micro-tone",
"Use body type, temperament and life-launch style as supportive evidence only, not as standalone rectification proof",
"For rectification claims, require event timing, D9/D10 plausibility or multiple independent appearance/life-pattern checks",
"Downgrade confidence sharply when the ascendant sits near a sign or pada boundary"
],
"confidence_ceiling": "B for personality and launch-style interpretation when degree, nakshatra, pada and chart context agree; C when used near boundaries or for rectification hints only.",
"forbidden_claims": [
"Ascendant degree alone proves exact birth time",
"A single Lagna nakshatra or pada alone determines fate, profession or marriage outcome",
"Body appearance alone is sufficient to finalize rectification"
],
"safe_output_patterns": [
"Use the Lagna sign for the main behavioral frame, the nakshatra for instinctive style, and the pada for fine-grained expression tone.",
"When the ascendant is close to a boundary, explicitly say the result is sensitive and should be verified with life events, D9/D10 and timing evidence.",
"Frame ascendant degree interpretation as a launch-style or embodiment modifier, not a standalone verdict on wealth, marriage or destiny."
]
}
}
}