Add strict workflow router for Jyotish skill
This commit is contained in:
732642856
@@ -1,5 +1,48 @@
|
||||
# 印度占星 Skill 更新日志
|
||||
|
||||
## v6.0.1-orchestration（2026-06-03）— Strict Workflow Router + Technique Audit 防遗漏编排
|
||||
|
||||
> **触发原因**：实际解读中发现 skill 已覆盖大量高级技法（Jaimini、Chara Dasha、Karakamsha、Argala、Shadbala、Ashtakavarga、Yogini、Avastha 等），但 AI 未必会自动调用。用户必须懂技法名才能逼迫调用，导致 D10、Jaimini、A10、Bhava Chalit、Sudarshana、Dasha Sandhi 等关键层容易遗漏。
|
||||
|
||||
### ① 新增 Strict Workflow Router
|
||||
|
||||
新增 `references/strict-workflow-router.md`，作为问题类型驱动的强制路由文件。核心目标：
|
||||
|
||||
- 不让用户负责点名高级技法；
|
||||
- 由 skill 根据问题类型自动选择 mandatory checklist；
|
||||
- 每次输出必须暴露已调用/未调用/partial/unavailable 模块；
|
||||
- 防止只看 D1、只看 Dasha、只看单一 Transit 的偷懒式解读。
|
||||
|
||||
### ② 新增六类 strict route
|
||||
|
||||
| Route | 触发场景 | 强制深度 |
|
||||
|---|---|---|
|
||||
| `career-timing-strict` | 事业机会、职业方向、项目落地、公开身份 | Level 3 |
|
||||
| `relationship-timing-strict` | 婚恋、婚姻、伴侣、复合、关系结果 | Level 3 |
|
||||
| `wealth-timing-strict` | 财运、收入、到账、资产、收益 | Level 2/3 |
|
||||
| `event-timing-strict` | 具体事件是否发生、应期、项目审批 | Level 3 |
|
||||
| `event-verification-strict` | 历史事件回测、技法可靠性验证 | Level 3 |
|
||||
| `full-reading-strict` | 综合命盘解读 | Level 2 |
|
||||
|
||||
### ③ 强制 Technique Audit Table
|
||||
|
||||
每次 Level 2+ 解读末尾必须输出技法审计表，标注：`called` / `partial` / `unavailable` / `not called`，并说明未调用项对结论置信度的影响。
|
||||
|
||||
### ④ 显式缺口声明
|
||||
|
||||
A10/10th Arudha、完整 Bhava Chalit、Pushkara 自动化、Sudarshana Chakra、Dasha Sandhi 等若无法计算，不得静默省略，必须声明缺失原因和影响。
|
||||
|
||||
### ⑤ 修改文件
|
||||
|
||||
| 文件 | 变更 |
|
||||
|---|---|
|
||||
| `SKILL.md` | 增加严格路由入口、阶段负一、阶段八 Technique Audit、预测清单缺口声明 |
|
||||
| `references/strict-workflow-router.md` | 新增问题类型路由、mandatory checklist、审计模板、缺口声明规则 |
|
||||
| `references/quick-reference-guide.md` | 专项分析强制接入 strict route |
|
||||
| `references/ai-reading-workflow-prompt.md` | 阶段二新增 Strict Workflow Router |
|
||||
|
||||
---
|
||||
|
||||
## v4.3.0（2026-05-03）— Dasha 浮点边界修复 + App UI 全面优化
|
||||
|
||||
> **触发原因**：多案例交叉验证中发现 Barack Obama 案例 Dasha 0/9 匹配，定位到浮点边界 bug。
|
||||
|
||||
@@ -7,7 +7,8 @@ description: 印度占星（Jyotish）专业解盘与推运系统。核心能力
|
||||
# 印度占星专业解盘与推运系统
|
||||
|
||||
> **执行总控**：`references/quick-reference-guide.md`（⭐推荐优先阅读）
|
||||
> **版本**：v6.0.0 | **详细变更**：`CHANGELOG.md`
|
||||
> **严格路由**：`references/strict-workflow-router.md`（⭐涉及事业/婚恋/财务/应期/技法验证时必须优先读取）
|
||||
> **版本**：v6.0.1-orchestration | **详细变更**：`CHANGELOG.md`
|
||||
|
||||
---
|
||||
|
||||
@@ -23,6 +24,7 @@ description: 印度占星（Jyotish）专业解盘与推运系统。核心能力
|
||||
|
||||
**强制工作流**（完整规范 → `references/ai-reading-workflow-prompt.md` v3.0）：
|
||||
|
||||
0. **阶段负一**：问题类型路由（事业/婚恋/财务/应期/历史验证/综合解盘）→ 必须先读 `references/strict-workflow-router.md`，按对应 strict checklist 执行；用户不需要主动点名高级技法。
|
||||
1. **阶段零**：入口路由（A/B/C自动判断）
|
||||
2. **阶段一**（仅B）：PDF/图片提取 + Quality Gate
|
||||
3. **阶段二**：意图识别 → 路由目标宫位（无明确意图→Level 2综合解盘）
|
||||
@@ -31,11 +33,22 @@ description: 印度占星（Jyotish）专业解盘与推运系统。核心能力
|
||||
6. **阶段五**：应期输出（五层验证→时间窗口→Actionable Output+案例检索）
|
||||
7. **阶段六**：补救措施（可选）
|
||||
8. **阶段七**：现代措辞包装
|
||||
9. **阶段八**：输出 Technique Audit Table，逐项声明已调用/未调用/部分可用/缺失模块及其对置信度的影响。
|
||||
|
||||
---
|
||||
|
||||
## ⚠️ 强制规则（与"不跳步"同级）
|
||||
|
||||
### Strict Workflow Router（v6.0.1-orchestration）
|
||||
|
||||
**凡是用户询问事业、婚恋、财务、事件应期、历史回测或技法可靠性，必须先读取 `references/strict-workflow-router.md`。**
|
||||
|
||||
核心要求：
|
||||
1. 先判断问题类型，再自动选择 `career-timing-strict` / `relationship-timing-strict` / `wealth-timing-strict` / `event-timing-strict` / `event-verification-strict`。
|
||||
2. 用户不需要知道 Chara Dasha、A10、Argala、Shadbala、Ashtakavarga 等技法名称；AI 必须按问题类型自动调用。
|
||||
3. 输出末尾必须给出 Technique Audit Table，说明每项高级技法是否调用、结果是什么、缺失会如何降低置信度。
|
||||
4. 不得把未实现或未调用的技法静默省略；A10、完整 Bhava Chalit、Pushkara 自动化、Sudarshana Chakra、Dasha Sandhi 等若未能计算，必须显式标注为 partial/unavailable。
|
||||
|
||||
### MEVG 强制外部验证门控（v4.2.0+）
|
||||
|
||||
**所有解读结论必须经过外部权威来源验证，禁止仅凭 AI 训练记忆输出。**
|
||||
@@ -165,6 +178,8 @@ $PYTHON $SCRIPT <子命令> [参数]
|
||||
|
||||
## 预测清单
|
||||
|
||||
- [ ] **Strict Router**：已读取 `references/strict-workflow-router.md`，并声明本轮使用的 strict route
|
||||
- [ ] **Technique Audit Table**：输出末尾已列出已调用/未调用/partial/unavailable 技法及置信度影响
|
||||
- [ ] **MEVG-静态门控**：所有静态解读声明必须web_search验证
|
||||
- [ ] 静态星盘分析（行星配置、Yoga、Nakshatra、宫位）
|
||||
- [ ] Argala检查（2/4/5/8/11宫干预+Virodha）
|
||||
@@ -183,6 +198,7 @@ $PYTHON $SCRIPT <子命令> [参数]
|
||||
- [ ] 预测边界检查（置信度标注，禁止绝对断言）
|
||||
- [ ] **案例检索**：动态预测必须先检索真实案例
|
||||
- [ ] **MEVG-预测门控**：确认每条预测有来源+置信度一致
|
||||
- [ ] **缺口声明**：若 A10/完整Bhava Chalit/Pushkara/Sudarshana/Dasha Sandhi 等未计算，已说明原因与影响
|
||||
|
||||
---
|
||||
|
||||
|
||||
@@ -449,20 +449,32 @@ AI不应该凭空假设一个时间，而应该通过结构化互动帮助用户
|
||||
|
||||
## 阶段二：用户意图识别与路由
|
||||
|
||||
### 2.0 Strict Workflow Router（v6.0.1-orchestration）
|
||||
|
||||
在使用下方意图路由表之前，先读取 `strict-workflow-router.md`。凡涉及事业、婚恋、财务、事件应期、历史回测、技法可靠性或高级分析，必须选择对应 strict route，并在最终输出附 Technique Audit Table。
|
||||
|
||||
| 用户意图 | Strict route | 必须额外完成 |
|
||||
|----------|-------------|-------------|
|
||||
| 事业机会/职业方向/项目落地 | `career-timing-strict` | D1+D9+D10+Vimshottari+Jaimini+AmK/Karakamsha+AL/A10+Shadbala+AV+Argala |
|
||||
| 婚恋/婚姻/伴侣/关系结果 | `relationship-timing-strict` | 性别/昼夜确认+D1+D9+DK+UL+Double Transit+KP |
|
||||
| 财运/收入/到账/资产 | `wealth-timing-strict` | 2H/11H+D2/D10+Shadbala+AV+Argala+KP |
|
||||
| 具体事件是否发生/何时发生 | `event-timing-strict` | 事件宫位定义+Dasha+Transit+KP+Moon trigger |
|
||||
| 历史事件验证/技法可靠性 | `event-verification-strict` | 同一技法回测+命中/失败评分+个人化规则 |
|
||||
|
||||
### 2.1 意图路由表
|
||||
|
||||
| 用户意图 | 目标宫位 | 核心参考文件 | 承诺模板 |
|
||||
|----------|---------|-------------|---------|
|
||||
| 婚姻/恋爱/关系 | 7宫 | `relationship-astrology-guide.md` | §1 |
|
||||
| 事业/职业/工作 | 10宫 | `house-modern-mapping.md` | §2 |
|
||||
| 财富/收入/投资 | 2宫+11宫 | `house-domain-planet-mapping.md` | §3 |
|
||||
| 婚姻/恋爱/关系 | 7宫 | `strict-workflow-router.md` + `relationship-astrology-guide.md` | §1 |
|
||||
| 事业/职业/工作 | 10宫 | `strict-workflow-router.md` + `house-modern-mapping.md` | §2 |
|
||||
| 财富/收入/投资 | 2宫+11宫 | `strict-workflow-router.md` + `house-domain-planet-mapping.md` | §3 |
|
||||
| 子女/创作 | 5宫 | `modern-life-scenarios-complete.md` | §4 |
|
||||
| 健康/体质 | 1宫+6宫+8宫 | — | §5 |
|
||||
| 教育/学业 | 4宫+9宫 | — | §6 |
|
||||
| 出国/迁移 | 9宫+12宫 | — | §7 |
|
||||
| 灵性/修行 | 9宫+12宫 | — | §8 |
|
||||
| 合盘/关系匹配 | 7宫 | `synastry` + `relationship-astrology-guide.md` | §1 |
|
||||
| 综合解盘（全盘） | 全部 | `comprehensive-reading-workflow.md` | 全部 |
|
||||
| 合盘/关系匹配 | 7宫 | `strict-workflow-router.md` + `synastry` + `relationship-astrology-guide.md` | §1 |
|
||||
| 综合解盘（全盘） | 全部 | `strict-workflow-router.md` + `comprehensive-reading-workflow.md` | 全部 |
|
||||
|
||||
**（承诺模板→ `promise-assessment-templates.md`）**
|
||||
|
||||
|
||||
@@ -119,24 +119,26 @@ Dasa Convergence给出"哪个时间段"，Transit给出"精确触发点"。
|
||||
|
||||
---
|
||||
|
||||
## 四、实战案例：一楠命盘的Dasa Convergence
|
||||
## 四、实战案例：关系领域的Dasa Convergence匿名模板
|
||||
|
||||
> 注意：本节仅示范Convergence方法，不代表任何特定个案。实际使用时必须替换为当事人的真实7宫、7宫主、DK、当前Dasha与可用条件Dasha数据。
|
||||
|
||||
### 目标：关系/婚姻启动时机
|
||||
|
||||
**Step 1 结果**：7宫=Aquarius，7宫主=Saturn，7宫内行星=Saturn+Moon，DK=Mars
|
||||
**Step 1 示例**：先定位7宫、7宫主、7宫内行星、DK、UL及D9相关指标。
|
||||
|
||||
**Step 2-3 结果**（2027年3月）：
|
||||
**Step 2-3 示例**：检查同一时间段是否有多个独立Dasha系统共同激活关系领域。
|
||||
|
||||
| Dasha系统 | 当前周期 | 关系激活？ | 证据 |
|
||||
| Dasha系统 | 当前周期 | 关系激活？ | 证据示例 |
|
||||
|-----------|---------|-----------|------|
|
||||
| Vimsottari | Saturn Maha + **Venus Bhukti** | ✅ | Venus是8宫内行星（入庙）且是女命恋爱征象星 |
|
||||
| Yogini | Saturn周期 | ✅ | Saturn是7宫主=关系结构激活 |
|
||||
| Sudasa | Leo→Aquarius重叠期 | ✅ | Aquarius=7宫=关系宫 |
|
||||
| Kalachakra | 待精确计算 | ⚠️ | 需外部计算 |
|
||||
| Vimsottari | Maha + Bhukti | ✅/❌ | Maha/Bhukti主星是否为7宫主、7宫内行星、DK、UL主或关系Karaka |
|
||||
| Yogini | 当前Yogini | ✅/❌ | 当前Yogini主星是否连接7宫、D9或关系Karaka |
|
||||
| Chara/Sudasa | 当前星座周期 | ✅/❌ | 当前星座是否包含DK、照7宫/UL，或与D9关系轴形成连接 |
|
||||
| Kalachakra/其他 | 待精确计算 | ⚠️ | 需外部计算，不能伪造 |
|
||||
|
||||
**Convergence等级**：**Level 2（3系统同时激活）**
|
||||
**Convergence等级**：按同时激活系统数量评估，2个为弱收敛，3个为中收敛，4个以上为强收敛。
|
||||
|
||||
**结论**：2027年3月前后，3个独立Dasha系统同时指向关系领域激活 → 关系启动概率从基础60%提升至80-85%
|
||||
**结论模板**：当多个独立Dasha系统同时指向关系领域，再叠加Transit触发时，关系事件概率上调；但Convergence不等于确定事件，仍需本命承诺、分盘与过境共同确认。
|
||||
|
||||
---
|
||||
|
||||
|
||||
@@ -11,11 +11,10 @@
|
||||
|
||||
**当前分析偏差**：Ketu在推运解读中被系统性偏重"放手/解脱"属性，忽略"突然转变/非预期开启"属性。
|
||||
|
||||
**典型案例**：
|
||||
- 一楠 Saturn-Ketu小运（2026-01至2027-03）
|
||||
- 分析结论："清零年、放手、结束旧模式"
|
||||
- 遗漏信号：Ketu也掌管**突然的职业转变、非预期的新机会、技术/灵性突破**
|
||||
- 外部占星师正确识别：2026年5-6月"新工作"信号
|
||||
**典型分析偏差**：
|
||||
- Saturn-Ketu小运容易被机械解读为"清零年、放手、结束旧模式"
|
||||
- 遗漏信号：Ketu也可能掌管**突然转变、非预期开启、技术/灵性突破、旧资源回头**
|
||||
- 但也要避免反向误判：不能仅凭Ketu或12宫/外出信号就断"新工作"，必须同时检查10宫/10主/D10/2宫/11宫/合同收益线是否同步激活
|
||||
|
||||
**偏差机制**：Ketu的字面含义（" severed head"、无头之身）容易被解读为纯粹的"失去/脱离"，但经典文献明确记载其双重属性。
|
||||
|
||||
@@ -118,22 +117,20 @@
|
||||
|
||||
---
|
||||
|
||||
## 六、一楠案例复盘（2026 Saturn-Ketu）
|
||||
## 六、案例复盘提示（2026 Saturn-Ketu）
|
||||
|
||||
### 星盘数据
|
||||
- Ketu在摩羯座8宫
|
||||
- Ketu受木星（11宫主）三分相位
|
||||
- Saturn在水瓶座9宫（Saturn-Ketu Dasha）
|
||||
### 使用前校验
|
||||
- 本节用于提醒：**不要把Ketu小运机械解读为清零、失去或纯负面**。
|
||||
- 若用于具体个人案例，必须重新读取当前星盘数据，核对Ketu宫位、星座、定位星、合相/相位、D10/D9/D4分盘与Dasha层级；不得沿用旧会话或模板中的个人配置。
|
||||
|
||||
### 原始分析（偏误）
|
||||
- ✅ 属性A：清零、放手旧模式 → **正确但片面**
|
||||
- ❌ 遗漏属性B：Ketu在8宫=深度研究突破、灵性转变、非预期事件
|
||||
### 原始分析常见偏误
|
||||
- ✅ 属性A：清零、放手旧模式 → **可能正确但片面**
|
||||
- ❌ 遗漏属性B：Ketu也可能带来非预期转向、研究/技术/灵性突破、旧资源回流、局部执行或弱兑现
|
||||
|
||||
### 修正分析（双重属性）
|
||||
- **属性A（60%）**：结束旧的事业模式、清理未完成的事务
|
||||
- **属性B（40%）**：突然的深度研究突破、8宫领域的转变（心理学/灵性/投资研究）
|
||||
- **过境配合**：2026年5月木星进巨蟹→从Chandra Lagna看6宫=新工作
|
||||
- **综合**：Saturn-Ketu期间并非单纯"清零"，而是**在放手旧模式的同时，突然开启新方向**
|
||||
- **属性A**：结束旧模式、清理未完成事务、降低外部执着、结果不完整
|
||||
- **属性B**：突然开启新方向、非传统项目/技术/研究/灵性领域突破、旧资源回流带来局部执行
|
||||
- **综合**：Saturn-Ketu期间并非单纯"清零"，而是可能表现为**一边剥离旧结构，一边产生非传统入口或弱兑现事件**；具体偏向必须由本命承诺、分盘、Dasha和Transit共同判断。
|
||||
|
||||
### 关键教训
|
||||
> Ketu小运期间，"放手"和"突破"是**同时发生的两面**。只看一面会导致预测严重偏差。
|
||||
|
||||
@@ -121,9 +121,10 @@ Pratyantar时长 = (该行星在120年周期中的年数 / 120年) × Antardasha
|
||||
- 从Chandra Lagna看：6宫（新工作/服务）⭐
|
||||
4. **叠加效应**：月亮Pratyantar + 木星过境 = Chandra Lagna被双重激活
|
||||
|
||||
**预测**：
|
||||
- 2026年4月底-6月初：**新工作/职业方向的信号最强期**
|
||||
- 这正是外部占星师预测的"5月底6月初新工作"窗口
|
||||
**预测边界修正**：
|
||||
- 2026年4月底-6月初：可标记为**12宫/移动/非日常场域信号增强期**，但不得直接写成“新工作/职业方向最强期”。
|
||||
- 若要判断为工作或职业事件，必须额外看到10宫/10主/D10/2宫/11宫/合同收益线同步触发；否则只能输出为“出行、住宿、支出、关系场域、幕后事务、服务/义务增加”等广义主题。
|
||||
- 外部占星师或既有文本中的“新工作”说法只能作为待验证假设，不能作为结论。
|
||||
|
||||
---
|
||||
|
||||
|
||||
@@ -99,16 +99,18 @@
|
||||
|
||||
**判断类型**：专项事件分析
|
||||
|
||||
**强制入口**：先读取 `references/strict-workflow-router.md`。如果问题是事业机会/职业方向/项目落地，必须走 `career-timing-strict`；如果是财运/收入/到账，必须走 `wealth-timing-strict`；如果是具体事件能否发生，必须走 `event-timing-strict`。
|
||||
|
||||
**参考路由**：
|
||||
|
||||
| 用户意图 | 主参考文件 | 引擎命令 |
|
||||
|---------|-----------|---------|
|
||||
| 事业时机 | references/yoga-phala-timing-guide.md | `dasha` + `transit` |
|
||||
| 事业时机 | references/strict-workflow-router.md + references/yoga-phala-timing-guide.md | `full-reading` + `varga-full` + `dasha` + `jaimini` + `shadbala` + `ashtakavarga` + `argala` + `transit` |
|
||||
| **→ Actionable Output** | references/transit-actionable-output-guide.md ⭐v4.1.0 | 必须输出时间段+行动+置信度 |
|
||||
| 财运来源 | references/darakaraka-complete-guide.md（DK财富5模式）| `chart` + `yoga` |
|
||||
| 财运来源 | references/strict-workflow-router.md + references/darakaraka-complete-guide.md（DK财富5模式）| `chart` + `varga-full` + `dasha` + `shadbala` + `ashtakavarga` + `argala` |
|
||||
| 学业考试 | references/planetary-dignity-complete-reference.md（D24分析） | `varga -d 24` |
|
||||
| 健康预后 | references/advanced-techniques.md（8宫+6宫） | `chart` + `shadbala` |
|
||||
| 职业方向 | references/d10-varga-guide.md（D10事业盘） | `varga -d 10` |
|
||||
| 职业方向 | references/strict-workflow-router.md + references/d10-varga-guide.md（D10事业盘） | `varga-full` + `jaimini` + `shadbala` + `ashtakavarga` |
|
||||
|
||||
---
|
||||
|
||||
|
||||
@@ -0,0 +1,215 @@
|
||||
# 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:
|
||||
|
||||
1. **Opportunity contact**: message/interview/initial approach.
|
||||
2. **Structural opportunity**: contract, formal role, long-term project, institution.
|
||||
3. **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
|
||||
|
||||
1. Define the event house and event significators.
|
||||
2. Check natal promise in D1 and relevant Varga.
|
||||
3. Check Vimshottari MD/AD/PD.
|
||||
4. Cross-check Chara Dasha if event is major.
|
||||
5. Check Saturn/Jupiter/Rahu-Ketu transit to event houses/lords.
|
||||
6. Check Double Transit where applicable.
|
||||
7. Use KP/Sub-lord if the question is binary or landing-specific.
|
||||
8. Use Moon transit only as a trigger inside an already-supported window.
|
||||
9. 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
|
||||
|
||||
1. Extract the exact event date or window.
|
||||
2. Identify which prediction rule would have implied it.
|
||||
3. Apply the same rule to the past event without changing interpretation after seeing the result.
|
||||
4. 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.
|
||||
5. 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.
|
||||
@@ -160,7 +160,7 @@ Step 6: 三层吻合 → 高概率事件
|
||||
|
||||
| 情况 | Lagna过境 | Chandra过境 | 解读 | 案例 |
|
||||
|------|---------|---------|------|------|
|
||||
| L隐退C新工作 | ❌ 12宫 | ✅ **6宫** | **幕后创业/转向新领域** = 一楠2026年6月案例 | ⚠️ 最容易遗漏 |
|
||||
| L隐退C新工作 | ❌ 12宫 | ✅ **6宫** | **幕后创业/转向新领域**；但若缺少10宫/10主/D10/2宫/11宫同步触发，不能把所有外出或非日常事件直接归因为工作 | ⚠️ 最容易遗漏 |
|
||||
| 外好内差 | ✅ 7宫吉 | ❌ 月亮受克 | 外在事件顺利但内心不安 | |
|
||||
| 外差内好 | ❌ 10宫受克 | ✅ 月亮受吉 | 外在困难但内心平静 | |
|
||||
| 双好 | ✅ | ✅ | 最佳状态，外内一致 | |
|
||||
|
||||
Reference in New Issue
Block a user