Vendor integration is retired.
This page preserves value-free evidence from systems being replaced. Every current and future calculation, interpretation and API contract is a first-party The Indian Astrology product.
Every consumed field now has an honest disposition.
Automated synthetic native runs proved that every declared native path existed when this archive was frozen. Candidate mappings are retained as history only; they do not define current formulas, fields or product priorities.
What path verification proves
The named field exists in a synthetic response from the same native engine selected by the observed public form. It prevents documentation drift and broken translation targets.
What it does not prove
It does not establish provider values, defaults, date formatting, array ordering or semantic equivalence. Those questions stay behind the authorized runtime-fixture and shadow-acceptance gate.
Preserve the input. Upgrade the engine.
POST an observed form identifier and fields to the migration route. It derives an IANA timezone from lat/lang, ignores identity fields, and returns the authoritative TIA native envelope with an explicit non-compatibility boundary.
POST /api/v2/migrations/mahaguru/public-form
{
"formIdentifier": "ascendant",
"birthday": 1,
"birthmonth": 1,
"birthyear": 1990,
"birthtime": 12,
"birthminute": 0,
"lat": 28.6139,
"lang": 77.209,
"timezone": 5.5,
"language": "en",
"referenceDate": "2026-09-10"
}Inspect the OpenAPI contract ↗Mahaguru form inventory
These public paths and form identifiers were observed directly on 11 September 2026. The migration route can now normalize all 17 into transparent native calculations, but it deliberately does not imitate the private provider response.
| Public path | Calculator | Form identifier | Surface | Evidence |
|---|---|---|---|---|
/ascendant-calculator/ | Ascendant | ascendant | shared birth form | form observed |
/kaal-sarp-dosha-calculator/ | Kaal Sarp Dosha | kalsarpa_dosha | shared birth form | form observed |
/shani-sade-sati-calculator/ | Shani Sade Sati | sadhesati | shared birth form | form observed |
/pitra-dosha-calculator/ | Pitra Dosha | pitradosha | shared birth form | form observed |
/manglik-dosha-calculator/ | Manglik Dosha | manglikdosha | shared birth form | form observed |
/nakshatra-calculator/ | Nakshatra | nakshatra | shared birth form | form observed |
/yogini-dasha-calculator/ | Yogini Dasha | yoginidasha | shared birth form | form observed |
/moon-sign-calculator/ | Moon Sign | moonsign | shared birth form | form observed |
/biorhythm-calculator/ | Biorhythm | biorhythm | shared birth form | form observed |
/atmakaraka-calculator/ | Atmakaraka | atmakaraka | shared birth form | form observed |
/ishta-devata-calculator/ | Ishta Devata | ishatdevta | shared birth form | form observed |
/lucky-bracelet-calculator/ | Lucky Bracelet | luckybracelate | shared birth form | form observed |
/lucky-rudraksha-calculator/ | Lucky Rudraksha | luckyrudraksha | shared birth form | form observed |
/unlucky-date-calculator/ | Unlucky Date | unluckydate | shared birth form | form observed |
/lucky-date-calculator/ | Lucky Date | luckydate | shared birth form | form observed |
/numerology-lucky-colour-calculator/ | Lucky Colour | luckycolour | shared birth form | form observed |
/lucky-vehicle-number-calculator/ | Lucky Vehicle Number | vehicle-number | page-local form | form observed |
Eleven call the provider. Six stay local.
A credential-free, visitor-log-free audit of the active AstroNumero 1.0.1 handler identified the exact execution split. Source fingerprints are published in the JSON manifest; source code and secrets are not.
14 observed v1 resources
general_ascendant_reportkalsarpa_detailssadhesati_life_detailssadhesati_current_statuspitra_dosha_reportmanglikgeneral_rashi_report/moongeneral_nakshatra_reportplanetscurrent_yogini_dashamajor_yogini_dashabiorhythmjaimini_detailsisht_devata
Six local-only handlers
luckybracelateluckyrudrakshaunluckydateluckydateluckycolourvehicle-number
Two systems called Mahaguru—now kept separate.
The active WordPress calculators above use AstroNumero and AstrologyAPI. A separate private Mahaguru repository contains a newer native API surface. Its frozen source index is useful migration evidence, but it is not proof of live traffic, calculation validity or endpoint parity.
| Source family | Anonymous operations | TIA authority | Evidence status |
|---|---|---|---|
ashtakvarga | 2 | kundli-and-dosha | subject overlap only |
aspects | 3 | kundli-and-dosha | subject overlap only |
astrology | 10 | kundli-and-dosha | subject overlap only |
btr | 2 | classical-workbench | subject overlap only |
dashamsha | 2 | kundli-and-dosha | subject overlap only |
dosha-yoga | 4 | kundli-and-dosha | subject overlap only |
doshas | 3 | kundli-and-dosha | subject overlap only |
dwadashamsha | 2 | kundli-and-dosha | subject overlap only |
festivals | 5 | panchang-and-calendar | subject overlap only |
horoscope | 4 | predictions | subject overlap only |
kundli | 3 | kundli-and-dosha | subject overlap only |
matching | 9 | match-making | subject overlap only |
muhurat | 8 | muhurat | subject overlap only |
navamsa | 2 | kundli-and-dosha | subject overlap only |
numerology | 2 | numerology | subject overlap only |
panchang | 14 | panchang-and-calendar | subject overlap only |
rudraksha | 3 | review-only-recommendations | subject overlap only |
sade-sati | 2 | kundli-and-dosha | subject overlap only |
saptamsha | 2 | kundli-and-dosha | subject overlap only |
transit | 3 | predictions | subject overlap only |
varshaphal | 2 | kundli-and-dosha | subject overlap only |
vastu | 5 | vastu-and-direction | subject overlap only |
yogas | 3 | kundli-and-dosha | subject overlap only |
yogas-auspicious | 2 | muhurat | subject overlap only |
Validation stays honest
The source plugin manifest marks 0 calculation plugins as validated. Route presence and a successful synthetic response therefore cannot become formula authority.
Two count gaps retained
The narrative says 202 routes while its route index contains 200. The partial Vrat plugin also declares 5 patterns absent from that index. Both remain review gates.
The fields in use are now visible.
Only field paths and data types are recorded—never sample interpretation text. This clean-room comparison shows what Mahaguru reads, what the current official samples structurally expose, and where runtime fixtures are still indispensable.
Biorhythm: stop and verify
The current official sample is a JSON string, but the production handler dereferences physical, emotional, intellectual and average objects. An actual redacted runtime response is required before translation code is safe.
Ishta Devata: source only
The active handler calls isht_devata and reads devata_name plus report, but no current public reference page was found. TIA will not invent the missing contract or copy provider prose.
Capture shape. Discard every value.
The maintainer-only capture command reads an explicitly authorized synthetic JSON response from standard input. It emits registered paths, types, consumed-field coverage and a SHA-256 shape fingerprint. Scalar values and array indexes are discarded; unknown keys become a generic review sentinel. No credential or network request is accepted.
cd api
uv run tia-capture-legacy-contract \
--resource biorhythm \
--kind success \
< authorized-synthetic-response.jsonCapture-only evidence is not compatibility approval.
The outgoing request is now traced.
A value-free source audit records the exact provider payload shape used by the 14 observed resources. It publishes field origins and missing defaults—not credentials, visitor values or the client's private placeholder text.
Nine provider fields
day · month · year · hour · min · lat · lon— visitor-derived calculation valuestzone— returned by a separate timezone lookup with isDst=falsename— a static client placeholder; the visitor name is not forwarded and the literal remains unpublished
Defaults still unverified
- The form language is not forwarded; the public handler makes zero setLanguage calls and sends no Accept-Language header.
- No ayanamsha field is transmitted, so the effective provider/account default remains unverified.
- This documents old source behavior; it is not a pattern for the native API to copy.
The current guide and the legacy client have drifted.
Current official guidance documents eight required birth fields and date-aware timezone_with_dst resolution. The active legacy client adds a static name field and uses the older timezone request. Treating those contracts as identical would hide a calculation risk.
timezone_with_dst
The current guide resolves tzone from latitude, longitude and the birth date. Date-sensitive DST is part of the documented calculation path.
Why the old study stopped
Public documentation could not prove exact account response shapes, defaults or historical behaviour. Rather than imitate an uncertain contract, the product direction now builds independent native outputs.
Historical evidence, not a product dependency.
The maintainer-only comparison command is retained to reproduce past audit records. It has no HTTP client, credential option or public endpoint and cannot authorize integration, compatibility work or native formulas.
cd api
uv run tia-compare-legacy-shadow \
< authorized-synthetic-comparison.jsonTooling is ready; authorized runtime fixtures still equal zero.
What maps—and what does not
| Documented endpoint | Category | Native destination | Status | Reason |
|---|---|---|---|---|
/v1/planets | Basic Astro | /api/v2/calculations/kundli | candidate | Graha fields overlap; consumer fixture required. |
/v1/basic_panchang | Panchang | /api/v2/calculations/panchang | candidate | Timezone and response-field translation must be compared. |
/v1/current_vdasha | Vimshottari Dasha | /api/v2/calculations/kundli | candidate | Dasha evidence exists; legacy nesting is not assumed. |
/v1/kp_planets | KP Astrology | /api/v2/calculations/kp-prashna | not-equivalent | Horary KP is not a proven natal KP drop-in. |
/v1/lalkitab_horoscope | Lal Kitab | /api/v2/calculations/lal-kitab | candidate | Independent fixed-house evidence; proprietary prose excluded. |
/v1/match_ashtakoot_points | Match Making | /api/v2/calculations/match-making | candidate | Auditable Ashtakoota exists; exception fields need fixtures. |
/v1/numero_table | Numerology | /api/v2/calculations/numerology | candidate | Independent numbers only; vendor interpretations are not copied. |
/v1/sun_sign_prediction/daily/{sign} | Horoscopes | /api/v2/predictions/daily | not-equivalent | Vedic Moon-sign output cannot masquerade as Sun-sign output. |
Retired product direction
- No AstrologyAPI integration
- No vendor-compatible response contract
- No future adapter wave
- Build missing products natively
Frozen boundaries
- No proxy calls or vendor credentials
- No proprietary interpretations copied
- No /compat legacy routes published
- Native API remains source of truth
Historical machine-readable register
This archive accepts no birth data and exists only to document the retired migration study. Native product APIs are authoritative.
JSON archive ↗Back to native API →Page method and limits पृष्ठ विधि और सीमाएँ
Historical migration evidence: method, evidence and limits
A non-product audit archive documenting old dependency surfaces that independent The Indian Astrology products replace.
स्वतंत्र The Indian Astrology उत्पादों द्वारा बदले गए पुराने dependency surfaces का गैर-उत्पाद ऑडिट संग्रह।
How it works / कार्यविधि
Value-free historical inventories are retained for clean-room audit only; they do not define formulas or native API contracts.
मान-रहित ऐतिहासिक सूचियाँ केवल clean-room audit के लिए रखी गई हैं; वे formulas या native API contracts निर्धारित नहीं करतीं।
Evidence standard / प्रमाण मानक
This route links only to registered source and comparison records. Keep the input summary, engine version, calculation version and intermediate values with the result.
यह route केवल दर्ज source और comparison records से जुड़ता है। परिणाम के साथ input summary, engine version, calculation version और मध्यवर्ती मान सुरक्षित रखें।
Limits / सीमाएँ
Vendor integration, proxying, compatibility adapters and cloned response contracts are retired and not planned.
Vendor integration, proxying, compatibility adapters और cloned response contracts समाप्त हैं और नियोजित नहीं हैं।
Route evidence
Sources and contextual next steps / स्रोत और अगला चरण
The organization maintains the page text and route evidence. Versioned software profiles and tests—not a personal byline—establish numerical reproducibility.
संगठन पृष्ठ सामग्री और route evidence बनाए रखता है। संख्यात्मक पुनरुत्पादकता व्यक्तिगत नाम से नहीं, संस्करणबद्ध software profile और tests से स्थापित होती है।
Registered sources / दर्ज स्रोत
TIA-METHOD-EVIDENCE-1The Indian Astrology versioned calculation-evidence contract / The Indian Astrology संस्करणबद्ध गणना-प्रमाण अनुबंधCalculation-evidence contract / गणना-प्रमाण अनुबंधContinue with context / संदर्भ सहित आगे बढ़ें
Calculation methodologyगणना पद्धतिRelated guideसंबंधित मार्गदर्शिकाRelated guideसंबंधित मार्गदर्शिकाQuestions answered on this page
Frequently asked questions / सामान्य प्रश्न
What does the Historical migration evidence page establish? / ऐतिहासिक माइग्रेशन प्रमाण पृष्ठ क्या स्पष्ट करता है?
A non-product audit archive documenting old dependency surfaces that independent The Indian Astrology products replace. Value-free historical inventories are retained for clean-room audit only; they do not define formulas or native API contracts.
स्वतंत्र The Indian Astrology उत्पादों द्वारा बदले गए पुराने dependency surfaces का गैर-उत्पाद ऑडिट संग्रह। मान-रहित ऐतिहासिक सूचियाँ केवल clean-room audit के लिए रखी गई हैं; वे formulas या native API contracts निर्धारित नहीं करतीं।
What is outside this page's scope? / इस पृष्ठ के कार्यक्षेत्र से बाहर क्या है?
Vendor integration, proxying, compatibility adapters and cloned response contracts are retired and not planned.
Vendor integration, proxying, compatibility adapters और cloned response contracts समाप्त हैं और नियोजित नहीं हैं।