sync: import panchanga closure packets

2026-07-21 16:56:19 +08:00
parent a9d756691a
commit c60b3af7c3
8 changed files with 368 additions and 2 deletions
@@ -0,0 +1,29 @@
+# Panchanga local ↔ jyotishganit comparison — TEMCQ-061
+
+Date: 2026-07-21
+
+This packet closes the first local comparison step for the Panchanga schema ticket without writing a new Panchanga algorithm.
+
+## Result
+
+- Local method: `scripts/muhurta.py::calc_panchanga`
+- Case: Steve Jobs
+- Compared fields: `vaara`, `tithi`, `nakshatra`, `yoga`, `karana`
+- Result: 4 exact matches + 1 naming alias
+- Truth upgrade: 0
+
+## Field comparison
+
+| Field | Local | jyotishganit | Status |
+|---|---|---|---|
+| vaara | Thursday | Thursday | within_tolerance |
+| tithi | Shukla Tritiya | Shukla Tritiya | within_tolerance |
+| nakshatra | Uttara Bhadrapada | Uttara Bhadrapada | within_tolerance |
+| yoga | Shubha | Shubha | within_tolerance |
+| karana | Garija | Gara | alias_match |
+
+`Gara` and `Garija` are recorded as a naming alias, not a formula mismatch.
+
+## Boundary
+
+This is still `research_observation_only`. It does not upgrade Panchanga to global truth because VedAstro and PyJHora/JHora five-field normalized packets are not pinned for this same comparison, and sunrise-relative semantics still need multi-case closure.
@@ -0,0 +1,26 @@
+# Panchanga TEMCQ-061 schema packet — 2026-07-21
+
+## Result
+
+- Status: `schema_mapping_required`
+- Normalized fields ready: `0`
+- Truth upgrades: `0`
+
+## Observed jyotishganit raw
+
+- Vaara: Thursday
+- Tithi: Shukla Tritiya
+- Nakshatra: Uttara Bhadrapada
+- Yoga: Shubha
+- Karana: Gara
+
+## Blockers
+
+- Local archived high-rigor raw lacks a normalized Panchanga field.
+- PyJHora/JHora normalized Panchanga raw is not archived.
+- VedAstro shared Panchanga endpoint/method is not pinned.
+- Naming and calculation conventions must be fixed before field comparison.
+
+## Boundary
+
+This is schema mapping only. It does not prove Panchanga parity or production timing readiness.
@@ -0,0 +1,27 @@
+# Three-engine jyotishganit bridge applied — 2026-07-21
+
+## Status
+
+- Claim status: `observation_only`
+- Truth upgrades: `0`
+- Source selected hash: `4709b8ade84efdea4d0a67c15f3e32cea516a5aa2e8abe3885578feda20cb3f4`
+
+## Applied rows
+
+- Existing TEMCQ tickets mapped: `18`
+- No existing ticket: `1`
+
+Mapped groups:
+
+- D2/D4/D9/D10 sign rows → existing `endpoint_or_varga_semantics` tickets.
+- BAV/SAV rows → existing `ashtakavarga_table_or_contributor_variant` tickets.
+- Panchanga → no old mismatch ticket; create a separate closure row before comparison.
+
+## Boundary
+
+This packet only proves that jyotishganit selected raw can be routed into the
+existing closure queue. It does not prove formula truth, timing readiness, or
+commercial production tuning.
+
+Shadbala remains an explicit gap because the current jyotishganit probe does not
+expose `shadbala` or `strengths` in selected raw.