Calibrate Jyotish benchmarks and downgrade partial modules
This commit is contained in:
732642856
@@ -3,7 +3,7 @@
|
||||
**创建日期**：2026-04-22
|
||||
**来源**：Bavishyavani.in、Vedicmarga.com
|
||||
|
||||
> **来源标签**: 【传统·现代大师】 — Jaimini完整系统（Chara Karaka+Chara Dasha+Karakamsha）
|
||||
> **来源标签**: 【传统·现代大师】 — Jaimini知识层完整；当前计算层 Karaka/Karakamsha 可用，Chara Dasha timing 为 partial，需 KN Rao/PVN Rao/Iranganti 回归验证。
|
||||
---
|
||||
|
||||
## 一、Jaimini vs Parashari 核心区别
|
||||
|
||||
@@ -359,7 +359,7 @@ SCRIPT=~/.workbuddy/skills/jyotish-vedic-astrology/scripts/jyotish_engine.py
|
||||
| 子命令 | 功能 | 典型用法 |
|
||||
|--------|------|---------|
|
||||
| `aspects` | 度数精确相位系统（tight/moderate/loose + 入相位/出相位） | `aspects --year 1990 --month 1 --day 1 --hour 12 --minute 0 --lat 39.9 --lon 116.4 --tz 8` |
|
||||
| `jaimini` | Jaimini完整系统（Chara Karaka 7/8 + Chara Dasha + Karakamsha）+ `--antardasha` | `jaimini --year 1990 --month 1 --day 1 --hour 12 --minute 0 --lat 39.9 --lon 116.4 --tz 8 --mode all --antardasha` |
|
||||
| `jaimini` | Jaimini Karaka/Karakamsha；Chara Dasha timing 当前为 partial，需 KN Rao/PVN Rao 回归验证 | `jaimini --year 1990 --month 1 --day 1 --hour 12 --minute 0 --lat 39.9 --lon 116.4 --tz 8 --mode all --antardasha` |
|
||||
| `nakshatra-adv` | 高级Nakshatra（Tara Bala + Sub-Lord KP + 兼容性） | `nakshatra-adv --year 1990 --month 1 --day 1 --hour 12 --minute 0 --lat 39.9 --lon 116.4 --tz 8 --mode all` |
|
||||
| `argala` | Argala门闩系统（主/副Argala + Virodha反干预 + 净评分） | `argala --year 1990 --month 1 --day 1 --hour 12 --minute 0 --lat 39.9 --lon 116.4 --tz 8` |
|
||||
| `tajika` | Tajika年运盘（Muntha + YearLord + Mudda Dasha + Tri-Pataka） | `tajika --year 1990 --month 1 --day 1 --hour 12 --minute 0 --lat 39.9 --lon 116.4 --tz 8 --age 33` |
|
||||
@@ -369,7 +369,7 @@ SCRIPT=~/.workbuddy/skills/jyotish-vedic-astrology/scripts/jyotish_engine.py
|
||||
|
||||
| 子命令 | 功能 | 典型用法 |
|
||||
|--------|------|---------|
|
||||
| `shadbala` | 六重力量计算（Sthana/Dig/Kala/Chesta/Naisargika/Drik Bala） | `shadbala --year 1990 --month 1 --day 1 --hour 12 --minute 0 --lat 39.9 --lon 116.4 --tz 8` |
|
||||
| `shadbala` | 六重力量计算（内部一致；外部绝对值校准前为 partial） | `shadbala --year 1990 --month 1 --day 1 --hour 12 --minute 0 --lat 39.9 --lon 116.4 --tz 8` |
|
||||
| `ashtakavarga` | 八分法计算（BPHS完整8×8矩阵，SAV=337） | `ashtakavarga --year 1990 --month 1 --day 1 --hour 12 --minute 0 --lat 39.9 --lon 116.4 --tz 8` |
|
||||
| `validate` | R1-R10数学验证（SAV/BAV/延伸角/Rahu-Ketu/逆行/Dasha/完整性/度数/宫位） | `validate --year 1990 --month 1 --day 1 --hour 12 --minute 0 --lat 39.9 --lon 116.4 --tz 8` |
|
||||
| `audit` | P1-P12行星审计管线（Identity/Health/Resource/SAV/Dignity/Shadbala/Aspects/Nakshatra/Yogas） | `audit --year 1990 --month 1 --day 1 --hour 12 --minute 0 --lat 39.9 --lon 116.4 --tz 8` |
|
||||
@@ -444,7 +444,7 @@ SCRIPT=~/.workbuddy/skills/jyotish-vedic-astrology/scripts/jyotish_engine.py
|
||||
|
||||
### 分盘与力量评估（7个）
|
||||
30. **ashtakavarga-complete-system.md**：Ashtakavarga完整体系（SAV=337）
|
||||
31. **shadbala-complete-methodology.md**：Shadbala完整计算方法论
|
||||
31. **shadbala-complete-methodology.md**：Shadbala计算方法论（当前计算层 partial，内部一致但外部绝对值校准待完成）
|
||||
32. **planetary-strength-quick-ref.md**：行星力量速查表
|
||||
33. **varga-system-quick-reference.md**：综合九层分盘体系对照手册
|
||||
34. **varga-divisional-charts-quick-reference.md**：分盘快速参考
|
||||
|
||||
@@ -1,15 +1,17 @@
|
||||
# Shadbala完整计算方法论
|
||||
# Shadbala计算方法论
|
||||
|
||||
**创建日期**：2026-04-23
|
||||
**版本**：v2.0.0
|
||||
**版本**：v2.1.0-capability-partial
|
||||
**优先级**：⭐⭐⭐⭐⭐ 行星力量量化基础
|
||||
|
||||
> **来源标签**: 【混合·古典+传统+现代】 — Shadbala六重力量完整体系（BPHS计算+现代解读）
|
||||
> **来源标签**: 【混合·古典+传统+现代】 — Shadbala六重力量知识体系；当前 `scripts/shadbala.py` 为内部一致的近似计算层，外部绝对值校准前状态为 `partial`。
|
||||
---
|
||||
|
||||
## 一、Shadbala概述
|
||||
|
||||
**Shad** = 六，**Bala** = 力量。Shadbala是Parashara系统中量化行星力量的完整方法，由六种力量组成。
|
||||
**Shad** = 六，**Bala** = 力量。Shadbala是Parashara系统中量化行星力量的方法，由六种力量组成。
|
||||
|
||||
> **v6.0.11 工程状态提醒**：第九轮内部不变量 benchmark 已通过 1200/1200，证明当前输出结构、总分聚合、Rupa/Virupa 换算、排名和 full-reading 一致性可靠；但源码仍有 Nathonnata、Saptavargaja、Chesta、Drik 等简化项。因此当前分数只能作为内部一致的相对强弱参考，不得声称已经完成 JHora/公开书例级别的传统绝对值校准。
|
||||
|
||||
### 综合评分体系
|
||||
|
||||
|
||||
@@ -120,7 +120,7 @@ Use when the user asks for concrete timing, yes/no, project approval, launch, mo
|
||||
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.
|
||||
4. Cross-check Jaimini static indicators if event is major; Chara Dasha timing is partial and must be treated as low-weight corroboration only.
|
||||
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.
|
||||
@@ -163,10 +163,10 @@ Every Level 2+ output must include this table near the end.
|
||||
| D9 | Used / not used | ... | ... |
|
||||
| D10 / relevant Varga | Used / not used | ... | ... |
|
||||
| Vimshottari | Used / not used | ... | ... |
|
||||
| Jaimini / Chara Dasha | Used / not used | ... | ... |
|
||||
| Jaimini / Chara Dasha | Used / partial / not used | Karaka/Karakamsha reliable; Chara Dasha timing partial if used | Cap timing confidence unless independently corroborated |
|
||||
| AmK / Karakamsha | Used / not used | ... | ... |
|
||||
| AL / A10 | Used / partial / unavailable | ... | ... |
|
||||
| Shadbala | Used / not used | ... | ... |
|
||||
| Shadbala | Used / partial / not used | Internally consistent relative strength; external absolute calibration pending | Cap precise strength claims |
|
||||
| Ashtakavarga | Used / not used | ... | ... |
|
||||
| Argala | Used / not used | ... | ... |
|
||||
| KP / Sub-lord | Used / not required / unavailable | ... | ... |
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
# Technique Capability Matrix — Jyotish Skill v6.0.2
|
||||
# Technique Capability Matrix — Jyotish Skill v6.0.11
|
||||
|
||||
> Purpose: prevent vague statements like “covered” or “missing”. Each technique is classified by four layers: knowledge, computation, orchestration, and output.
|
||||
|
||||
@@ -21,10 +21,10 @@
|
||||
| D9 / Navamsa | Yes | Yes | Yes | Yes | `covered` | `varga-full`, D9 expanded dignity. |
|
||||
| D10 / Dasamsa | Yes | Yes | Yes | Yes | `covered` | `varga-full`, strict career route requires it. |
|
||||
| Vimshottari Dasha | Yes | Yes | Yes | Yes | `covered` | `dasha` and `full-reading`. |
|
||||
| Chara Dasha / Jaimini | Yes | Yes | Yes | Yes | `covered` | `jaimini` module with antardasha. |
|
||||
| Chara Dasha / Jaimini | Yes | Partial | Yes | Partial | `partial` | Chara Karaka/Karakamsha are usable, but Chara Dasha timing is a simplified implementation. Round 7 benchmark vs PyJHora KN Rao method matched only 58/240 fields (24.17%); do not use as high-confidence timing until KN Rao/PVN Rao/Iranganti method is implemented and revalidated. |
|
||||
| Karakamsha / AK | Yes | Yes | Yes | Yes | `covered` | `full-reading` uses AK, not DK. |
|
||||
| Argala | Yes | Yes | Yes | Yes | `covered` | `argala` module and strict routes. |
|
||||
| Shadbala | Yes | Yes | Yes | Yes | `covered` | `shadbala` module and `full-reading`. |
|
||||
| Shadbala | Yes | Partial | Yes | Yes | `partial` | Internal invariants passed 1200/1200 in Round 9, and `shadbala` matches `full-reading`; however current implementation still contains simplified Nathonnata Bala, Saptavargaja approximations, Chesta speed buckets and simplified Drik weights. Use as internally consistent strength reference, not externally calibrated Parashara absolute Shadbala. |
|
||||
| Ashtakavarga | Yes | Yes | Yes | Yes | `covered` | `ashtakavarga` module and validation. |
|
||||
| Avastha | Yes | Yes | Yes | Yes | `covered` | `scripts/avastha_calculator.py` integrated in `full-reading`. |
|
||||
| Vargottama | Yes | Yes | Yes | Yes | `covered` | App existed before; v6.0.2 adds `full-reading.modules.vargottama`. |
|
||||
@@ -44,6 +44,8 @@
|
||||
When producing a Technique Audit Table:
|
||||
|
||||
1. Do not mark a technique as missing if any layer exists.
|
||||
2. Use `partial` for Bhava Chalit and Sudarshana until full traditional modules are added.
|
||||
3. Use `covered` for A10, Vargottama, Pushkara, Avastha, and Dasha Sandhi from v6.0.2 onward, but still state whether the current run actually called `full-reading`.
|
||||
4. If a user provides only PDF text without exact degrees, Pushkara/Vargottama/A10 may degrade to `manual` or `unavailable` because the data layer is insufficient.
|
||||
2. Use `partial` for Chara Dasha/Jaimini timing, Shadbala, Bhava Chalit, and Sudarshana until full traditional modules are added or externally benchmark-validated.
|
||||
3. For Jaimini output, separate reliable Karaka/Karakamsha indicators from partial Chara Dasha timing; cap timing confidence if Chara Dasha is used.
|
||||
4. For Shadbala output, state that current scores are internally consistent but not yet externally calibrated to a full Parashara/JHora-style absolute Shadbala table.
|
||||
5. Use `covered` for A10, Vargottama, Pushkara, Avastha, and Dasha Sandhi from v6.0.2 onward, but still state whether the current run actually called `full-reading`.
|
||||
6. If a user provides only PDF text without exact degrees, Pushkara/Vargottama/A10 may degrade to `manual` or `unavailable` because the data layer is insufficient.
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
{
|
||||
"version": "v6.0.3-engineering-foundation",
|
||||
"version": "v6.0.11-shadbala-capability-downgrade",
|
||||
"source_inspiration": [
|
||||
{
|
||||
"name": "jyotishyamitra",
|
||||
@@ -72,12 +72,13 @@
|
||||
"jaimini_chara_dasha": {
|
||||
"name": "Jaimini / Chara Dasha",
|
||||
"domains": ["timing", "career", "relationship"],
|
||||
"status": "covered",
|
||||
"status": "partial",
|
||||
"knowledge_refs": ["references/jaimini-complete-system.md"],
|
||||
"commands": ["jaimini", "full-reading"],
|
||||
"output_paths": ["modules.jaimini"],
|
||||
"audit_label": "Jaimini/Chara",
|
||||
"missing_impact": "Rashi-based timing confirmation missing."
|
||||
"missing_impact": "Rashi-based timing confirmation is partial; timing confidence must be capped unless corroborated by Vimshottari, Dasha Sandhi, transit, D10/A10 and Ashtakavarga.",
|
||||
"limitation": "Round 7 benchmark vs PyJHora KN Rao Chara Dasha matched 58/240 fields (24.17%). Current calc_chara_dasha() is a simplified implementation, not a full KN Rao/PVN Rao/Iranganti method. Karaka/Karakamsha remain usable; Chara Dasha timing is partial."
|
||||
},
|
||||
"karakamsha_ak_amk": {
|
||||
"name": "Karakamsha / AK / AmK",
|
||||
@@ -112,12 +113,13 @@
|
||||
"shadbala": {
|
||||
"name": "Shadbala",
|
||||
"domains": ["strength", "static"],
|
||||
"status": "covered",
|
||||
"status": "partial",
|
||||
"knowledge_refs": ["references/shadbala-complete-methodology.md"],
|
||||
"commands": ["shadbala", "full-reading"],
|
||||
"output_paths": ["modules.shadbala"],
|
||||
"audit_label": "Shadbala",
|
||||
"missing_impact": "Planetary strength claims are not quantitatively anchored."
|
||||
"missing_impact": "Planetary strength claims are quantitatively anchored only as an internally consistent reference, not as externally calibrated absolute Parashara Shadbala.",
|
||||
"limitation": "Round 9 internal invariant benchmark passed 1200/1200 checks and full-reading matches the shadbala command. However scripts/shadbala.py still uses simplified Nathonnata Bala, approximate Saptavargaja sub-vargas, Chesta speed buckets and simplified Drik aspect weights. Use for relative strength ranking with confidence cap until an external full Shadbala table benchmark is frozen."
|
||||
},
|
||||
"ashtakavarga": {
|
||||
"name": "Ashtakavarga",
|
||||
|
||||
Reference in New Issue
Block a user