732642856
9.3 KiB
Strict Workflow Router for Jyotish Readings
Purpose: Prevent advanced techniques from being skipped. Route the user's plain-language question to a mandatory module checklist, then expose which modules were used, which were not used, and how omissions affect confidence.
Use this file before any Jyotish reading involving career timing, relationship timing, finance, event prediction, reliability verification, or advanced analysis.
0. Core rule: do not let the user name the techniques
The user should not need to ask for Chara Dasha, A10, Argala, Shadbala, Ashtakavarga, KP, or divisional charts. Infer the question type and run the required checklist automatically.
Every non-trivial reading must end with a Technique Audit Table.
1. Question router
| User intent | Route | Required depth |
|---|---|---|
| "When will career opportunities appear?" / job / project / public status / profession | career-timing-strict |
Level 3 |
| Marriage / partner / relationship timing | relationship-timing-strict |
Level 3 |
| Money / income / gains / assets | wealth-timing-strict |
Level 2 or 3 |
| "Will this event happen?" / concrete yes-no / project landing | event-timing-strict |
Level 3 |
| "Why did this past event happen?" / technique reliability | event-verification-strict |
Level 3 |
| General natal reading | full-reading-strict |
Level 2 |
| PDF/文字星盘 | PDF quality gate first, then route by intent | Level 2 or 3 |
If the user asks for methodological rigor, academic validation, past-event verification, or "do not guess", upgrade to Level 3.
2. Shared mandatory baseline
For every Level 2+ reading, complete or explicitly mark unavailable:
- D1 Rashi: houses, lords, dignity, exact degrees, Nakshatra, dispositor chain.
- D9 Navamsa: dignity confirmation, Vargottama, major dignity reversals.
- Relevant divisional chart: D10 for career, D7 for children, D12 for family/ancestral themes, D2 for wealth, D24 for education.
- Vimshottari Dasha: MD/AD/PD when timing is requested.
- Transit: Saturn/Jupiter/Rahu-Ketu, plus Moon trigger for month/day-level timing.
- Functional benefic/malefic status by Lagna.
- Shadbala and Ashtakavarga when a claim depends on planetary strength or transit strength.
- MEVG external verification for non-obvious interpretive claims.
- Confidence label: A/B/C/insufficient.
3. career-timing-strict
Use when the user asks about career, profession, job, project, public recognition, work direction, script/project landing, status, or timing of new opportunity.
Mandatory modules
| Layer | Required checks | Engine / reference |
|---|---|---|
| D1 career promise | 10H, 10L, 6H, 7H, 2H, 11H, Sun, Saturn, Mercury, Venus, exact degrees | chart, aspects |
| D9 confirmation | 10L dignity in D9, AK/AmK dignity, Vargottama | varga-full, jaimini |
| D10 execution | D10 Asc, 10H/10L, D10 Lagna lord, D10 Saturn/Sun/Mercury/Venus, D10 dispositor chain | varga-full |
| Dasha | Vimshottari MD/AD/PD; Dasha lord relation to 10H/10L/D10 | dasha |
| Jaimini | Chara Karaka, Amatya Karaka, Karakamsha, Chara Dasha | jaimini --antardasha |
| Arudha | AL and A10/Karma Pada if available | special lagna / manual if needed |
| Strength | Shadbala for Dasha lord, 10L, AmK, Saturn, Jupiter | shadbala |
| Transit strength | SAV/BAV for key transit signs and houses | ashtakavarga |
| Argala | Argala/Virodha on 10H, 10L, D10 10H, AmK | argala |
| KP / sub-lord | Use for yes/no or project landing questions | nakshatra-adv, KP references |
| Historical reliability | If user gives events, back-test same technique | predict --past-verify if applicable |
Career timing output
Always separate:
- Opportunity contact: message/interview/initial approach.
- Structural opportunity: contract, formal role, long-term project, institution.
- Public/result manifestation: release, payment, credit, visible status.
Do not merge these into one vague "career opportunity".
4. relationship-timing-strict
Use when the user asks marriage, relationship, spouse, partner, reconciliation, dating, or relationship outcome.
Mandatory modules
- Confirm gender and day/night context before spouse significator analysis.
- D1: 7H, 7L, Venus, Jupiter, Mars, Moon, DK.
- D9: Lagna, 7H/7L, Venus/Jupiter, DK placement.
- Jaimini: Darakaraka, Upapada Lagna, Chara Dasha.
- Double Transit: Jupiter/Saturn activation of 7H/7L/DK/UL.
- Vimshottari: MD/AD/PD activation of 7H/7L/Venus/Jupiter/DK/UL.
- KP 7H sub-lord when asking if a relationship will formalize.
- Historical relationship event verification if available.
5. wealth-timing-strict
Use when the user asks money, income, payment, asset, gains, business profit, funding, debt, or financial recovery.
Mandatory modules
- D1: 2H, 11H, 5H, 9H, 8H, 12H; 2L/11L; Jupiter, Venus, Mercury.
- D2 Hora if available; D10 if income is career-derived.
- Dasha: activation of 2L/11L/5L/9L/10L and D2/D10 indicators.
- Shadbala: 2L/11L/Jupiter/Venus/Mercury.
- Ashtakavarga: SAV/BAV of 2H/11H and transit Jupiter/Saturn positions.
- Argala: opening/blocking on 2H and 11H.
- KP: use for payment到账/settlement yes-no questions.
6. event-timing-strict
Use when the user asks for concrete timing, yes/no, project approval, launch, move, travel, contract, payment, or whether something will happen.
Mandatory modules
- Define the event house and event significators.
- Check natal promise in D1 and relevant Varga.
- Check Vimshottari MD/AD/PD.
- Cross-check Chara Dasha if event is major.
- Check Saturn/Jupiter/Rahu-Ketu transit to event houses/lords.
- Check Double Transit where applicable.
- Use KP/Sub-lord if the question is binary or landing-specific.
- Use Moon transit only as a trigger inside an already-supported window.
- Give time windows, not unsupported exact-day claims.
7. event-verification-strict
Use when the user provides past events and asks whether the technique is reliable.
Method
- Extract the exact event date or window.
- Identify which prediction rule would have implied it.
- Apply the same rule to the past event without changing interpretation after seeing the result.
- Score match quality:
- A: same theme + same timing + multiple systems support.
- B: same theme + approximate timing or delayed manifestation.
- C: symbolic match only.
- Fail: contradicted by event.
- Convert the result into a personalized rule only after at least two matching examples.
Output table
| Past event | Technique tested | Match | Adjustment |
|---|---|---|---|
| date/window + event | rule | A/B/C/fail | keep/downgrade/modify |
8. Technique Audit Table
Every Level 2+ output must include this table near the end.
| Technique | Status | Key result | Effect on confidence |
|---|---|---|---|
| D1 | Used / not used | ... | ... |
| D9 | Used / not used | ... | ... |
| D10 / relevant Varga | Used / not used | ... | ... |
| Vimshottari | Used / not used | ... | ... |
| Jaimini / Chara Dasha | Used / not used | ... | ... |
| AmK / Karakamsha | Used / not used | ... | ... |
| AL / A10 | Used / partial / unavailable | ... | ... |
| Shadbala | Used / not used | ... | ... |
| Ashtakavarga | Used / not used | ... | ... |
| Argala | Used / not used | ... | ... |
| KP / Sub-lord | Used / not required / unavailable | ... | ... |
| Historical verification | Used / not provided | ... | ... |
Never omit unavailable techniques silently. Mark them as unavailable or not integrated.
9. Known product gaps
The current skill has strong coverage, but these areas must be treated as incomplete unless a future module is added:
| Gap | Current handling | Impact |
|---|---|---|
| A10 / 10th Arudha / Karma Pada | Calculate manually if possible; otherwise mark unavailable | Career public-image layer incomplete |
| Full Bhava Chalit | Use cusp/KP data if present; otherwise mark partial | House placement near cusps may need recalibration |
| Pushkara Navamsa / Pushkara Bhaga automation | Check manually from references if necessary | D9 strength may be undercounted |
| Sudarshana Chakra | Manually synthesize D1+D9+D10 | Three-chart simultaneous confirmation incomplete |
| Dasha Sandhi | Estimate manually around Dasha transitions | Transition periods may be over/understated |
| Strict output orchestration | This file provides the workflow | Must be followed explicitly |
10. Confidence rules
| Confidence | Requirements |
|---|---|
| A | Natal promise + relevant Varga + Dasha + Transit + at least one verification layer support. For personal prediction, historical back-test preferred. |
| B | Three major systems support, but one key layer missing or timing is broad. |
| C | One or two indicators only; symbolic or exploratory. |
| Insufficient | Missing birth data, missing relevant Varga, no Dasha support, or unsupported exact timing. |
Do not upgrade confidence because the interpretation sounds elegant. Upgrade only when independent techniques converge.
11. Output discipline
- State what the question type is.
- State which strict route was used.
- Separate promise, activation, trigger, and manifestation.
- Separate contact, formalization, and visible result.
- Flag missing modules explicitly.
- Avoid industry-specific guessing unless the chart and user-provided context both support it.
- If the user asks for academic rigor, include technique limitations and failure modes.