Concept

Expert reading patterns

Beyond the 7-phase reading protocol, Lumin's orchestration prompt teaches the LLM six named patterns from senior practitioners. Pattern A through F. Each turns a verbose 5-15 step recipe into a single recognisable name.

Note

Three of these patterns are also exposed as deterministic composite workflow tools (Pattern B, C, E), for when latency or consistency matters more than LLM reasoning. The rest live in the system prompt for the LLM to chain.

Pattern A: KSK Strict CSL-DBA Marriage Formula

Krishnamurti's canonical Reader 4 example. For marriage timing:

Run analyze_natal_promise, confirm the 7th-house CSL signifies houses 2/7/11.
Run get_significators, identify the principal significator of each of houses 2, 7, 11 (one planet per house, strongest by L1>L2>L3>L4).
Run find_event_timing_v2, find the DBA where MD = principal of one house, AD = principal of another, PD = principal of third.
Run get_transit_advanced, triple transit confirmation on the predicted day.
Run get_ruling_planets at the predicted moment, must overlap fruitful significators.

The result names the DBA exactly: "marriage in [MD] mahadasha, [AD] antardasha, [PD] pratyantardasha, because each is the principal significator of houses [2/7/11]." This is how KSK predicted to the day in Reader 4.

Pattern B: K.N. Rao Triple-Dasha Consensus

Cross-validate event timing across THREE independent dasha systems:

get_event_dasha, Vimshottari (120-yr cycle).
get_yogini_dasha, 36-yr cycle.
get_chara_dasha, Jaimini sign-based dasha.

When all three flag the same calendar window, confidence is highest. When they disagree, surface the disagreement, never hide it. K.N. Rao taught that triple-dasha consensus is the most reliable predictive signal in Vedic astrology.

Also exposed as the atomic workflow run_triple_dasha_consensus with convergence levels STRONG / PARTIAL / WEAK / DIVERGENT.

Pattern C: Sanjay Rath Karakamsa Spiritual Lens

For soul-purpose / dharma / spiritual questions:

get_chara_karakas, identify Atmakaraka (planet at highest degree within own sign).
get_d9_chart, Atmakaraka's sign in D9 = Karakamsa.
get_ishta_devata, 12th from Karakamsa = personal deity / liberation gate.
get_d20_chart, spirituality (Vimshamsa).
get_past_life_karmic_panel, Saturn + Ketu + 12th + Karakamsa moksha-gate synthesis.

Also exposed as the atomic workflow run_karakamsa_spiritual_lens.

Pattern D: Cross-System Reconciliation

When KP and Vedic schools disagree, Lumin presents BOTH and explains why. Never hide a disagreement.

Marriage: KP analyze_natal_promise (7th CSL → 2/7/11) vs Vedic get_ashta_koota_milan (36-pt) vs Jaimini get_upapada_lagna (UL relationship).
Career: KP get_career_advanced + get_career_signature vs Vedic get_d10_chart vs Jaimini Amatyakaraka in get_chara_karakas.
Children: KP get_fertility_window vs Vedic get_d7_chart vs Jaimini Putrakaraka.

Higher concordance = stronger prediction. Lower concordance = the chart is genuinely ambiguous; surface that uncertainty rather than forcing a confident verdict.

Pattern E: Strict Pre-Verdict Audit

Before committing to ANY promise verdict:

get_boundary_warnings, any cusp within 6 arc-minutes of a sub-lord boundary?
get_combust_planets, any FULL combust on a key significator?
get_graha_yuddha, any war suppressing a key planet's significations?
get_vargottama_planets, are key significators vargottama (doubled-strength)?

If any of (1)-(3) fire, present the verdict with explicit confidence reduction. If (4) confirms, raise it. Also exposed as the atomic workflow run_pre_verdict_audit.

Pattern F: Multi-Varga Strength Aggregation

For "is this person/event truly strong" questions, run get_vimsopaka_bala, it aggregates dignity across 16 vargas (D1, D2, D3, D7, D9, D10, D12, D16, D20, D24, D27, D30, D40, D45, D60). A planet scoring ≥17/20 is exceptionally strong; under 8 is structurally weak regardless of natal sign. Use this as a tie-break weight in any matching, career, or longevity assessment.

PreviousKP / Vedic / Jaimini / Tajik NextContact support