🌐 A Panchang & Jyotish App That Runs Online — And Fully Offline From One File

Panchang, Rasi, Navamsa, Dasha, transits, six languages, Share State and reports — all in one Jyotish Atlas.


What if a Panchang and Jyotish astrology application did not need a server, cloud account, external CSV file, or live ephemeris API every time you used it?

What if you could simply open it in your browser, calculate a chart, inspect Panchang values, study Vimshottari Dasha, view transits — and then download the same application and continue using it fully offline?

That is what SSM-JA v3.7.41 now provides.

It is a live online Panchang and Jyotish calculation and observation application, available in six languages, while remaining a single standalone HTML file that can operate locally after download.

No installation.

No login.

No cloud calculation dependency.

No external CSV loading at runtime.

No live ephemeris API required for core calculation within the supported release range.

And now, broader language access for the Jyotish community.


🚀 Try SSM-JA v3.7.41

Open the same frozen release directly in your preferred language:

English

हिन्दी — Hindi

ಕನ್ನಡ — Kannada

മലയാളം — Malayalam

தமிழ் — Tamil

తెలుగు — Telugu

All six links open the same frozen SSM-JA v3.7.41 release. Only the presentation language changes.

🔗 SSM-JA Repository


🪔 What Can You Actually Do With It?

SSM-JA is browser-based Panchang and Jyotish software.

The current release includes:

  • Panchang
  • Rasi chart
  • Navamsa chart
  • Vimshottari Dasha
  • Mahadasha
  • Antardasha
  • Pratyantardasha
  • Sookshma Antardasha
  • Transit charts
  • Nakshatra
  • Nakshatra lord
  • Moon Nakshatra and Pada
  • Yoga
  • Karana
  • Paksha
  • Sunrise and sunset
  • Selected-date Moonrise cycle
  • Previous-date Moonrise cycle
  • Global location atlas
  • Manual location entry
  • Explicit timezone-offset input
  • Share State
  • Brief and Detailed reports
  • Browser print/PDF workflow
  • Responsive desktop and mobile layouts

And all of this is available in:

English • Hindi • Kannada • Malayalam • Tamil • Telugu

The application is designed for calculation, observation, reproducibility, research, and educational exploration.

It does not provide predictions, remedies, prescriptions, fortune-telling, or professional decision guidance.


🌍 Online When You Want It. Offline When You Need It.

There are really two ways to use SSM-JA.

Online

Open one of the six language links above and use it directly in a modern browser.

Offline

Download the standalone HTML release and open it locally.

After download, the core calculation environment does not require:

  • an internet connection
  • a cloud account
  • a server
  • an external CSV
  • a database
  • an external astronomical service
  • a runtime ephemeris API

The browser becomes the local calculation environment:

one file -> browser -> Panchang and Jyotish observation


✨ What Changed in v3.7.41?

The earlier public JA release demonstrated that a deterministic Jyotish observatory could run from embedded structure.

v3.7.41 turns that foundation into a much broader user-facing application.

The major visible changes include:

🌐 Six-language presentation

SSM-JA now supports:

English, Hindi, Kannada, Malayalam, Tamil, and Telugu.

Direct language URLs allow the application to open immediately in the selected presentation language.

The calculation remains the same underneath:

same inputs + same release + different presentation language -> same calculation structure


🔗 Share State

A chart state can be shared and reconstructed through the application’s Share State workflow.

Conceptually:

shared state -> restored state -> deterministic re-realization

That is useful for comparison, teaching, research, and repeatable observation.


🌙 Expanded Panchang and Moonrise observation

The Panchang layer now includes a broader observational presentation, including:

  • Nakshatra
  • Pada
  • Yoga
  • Karana
  • Paksha
  • Sunrise
  • Sunset
  • selected-date Moonrise cycle
  • previous-date Moonrise cycle

🖨️ Better reports

The current release provides both:

  • Brief report
  • Detailed report

with multilingual and responsive browser print/PDF presentation.


📱 Desktop and mobile presentation

The application is designed to work across desktop and mobile browser layouts.

A single HTML file now acts as:

application + embedded deterministic kernel + user interface + reporting environment + runtime integrity check


🧠 The Architectural Idea Behind SSM-JA

Most astronomy and astrology software eventually depends on some runtime chain such as:

request -> ephemeris -> calculation engine -> chart

SSM-JA asks a different question:

What if the observational structure needed for a bounded supported range travels inside the application itself?

Its direction is:

embedded structure -> deterministic realization -> reproducible observation

The current supported user input range is:

01 Jan 1950 -> 31 Dec 2100

The embedded Golden Kernel extends across:

01 Jan 1900 -> 31 Dec 2100

and contains:

  • 73,414 dates
  • 9 planetary bodies

Astronomical ephemerides remain foundational to the underlying data.

The claim is not that ephemerides are unnecessary.

The narrower architectural claim is:

within the supported range and frozen release, runtime access to an external ephemeris source is not required for reproducible SSM-JA realization

That distinction matters.


📦 From ~29 MB Source Data to One ~4.5 MB Application

The engineering result is compact:

The source Golden CSV was approximately:

~29 MB

The current complete standalone HTML application is approximately:

~4.5 MB

So the release direction becomes:

~29 MB source Golden CSV -> embedded deterministic kernel -> ~4.5 MB standalone HTML

No separate runtime CSV or data-file pairing is required.

The observatory travels as one file.


🖼️ Architecture Diagram

SSM-JA v3.7.41 architecture — inputs flow into an embedded deterministic engine and produce Panchang, Jyotish charts, Dasha, transit and observational outputs inside one browser-native application, with verification kept as a distinct boundary.


🔒 The File Can Check Its Own Embedded Kernel

The current release includes a frozen SHA-256 identity for the embedded Golden Kernel.

Where browser Web Crypto is available, SSM-JA performs the integrity check locally.

The frozen embedded-kernel SHA-256 is:

7bdebadfc764ef1f1cc2fc75cd3aaccdc48733f343f3e7311bc4503c354fa351

The exact v3.7.41 standalone HTML file is:

4,635,245 bytes

with whole-file SHA-256:

0fade1279bc389028ba05001e9d6542c5ab0ec40fc51988b06e55f1544451eb1

These are intentionally different identities:

whole-file HTML SHA-256 != embedded-kernel SHA-256

One identifies the frozen application.

The other identifies the deterministic kernel inside it.

This makes integrity something the software can check, rather than only something documentation can claim.


🔁 Why Deterministic Replay Matters

If the important inputs and the application release remain identical, SSM-JA is designed to reproduce the same chart structure.

The practical rule is simple:

same input + same release -> same deterministic chart structure

Why is that useful?

Because calculation software can otherwise accumulate differences through:

  • timezone assumptions
  • interpolation choices
  • runtime libraries
  • server changes
  • rounding policies
  • external API updates
  • implementation differences
  • future timezone-rule projections

SSM-JA does not claim to eliminate every source of astronomical or civil-time uncertainty.

Instead, it makes its own realization pathway fixed, visible, replayable, and testable.


🕰️ Explicit Timezone Assumptions

Timezone handling deserves special attention in astrology software.

SSM-JA uses an explicit UTC offset such as:

+05:30

or:

-04:00

This means the calculation pathway is visible:

birth input -> declared UTC offset -> UTC moment -> deterministic kernel -> Jyotish realization

For locations where DST or historical civil-time rules matter, users should verify the appropriate offset for the date being examined.

The important point is transparency:

same input + same UTC offset + same release -> same realization

and:

changed UTC offset -> changed realization

The software does not pretend that timezone complexity disappears.

It makes the assumption explicit.


🌅 Observational Continuity

SSM-JA was also tested against published sunrise and sunset reference values across consecutive dates and geographically distributed locations.

Two concrete examples follow.


📊 A Concrete Nine-Day Sunrise & Sunset Check

One useful continuity witness comes from Chicago, Illinois, USA, across 15 May 2026 -> 23 May 2026.

SSM-JA values were compared with values published by timeanddate.com and retrieved after the corresponding dates had passed. These comparison values are treated as post-event published reference values, not as independently confirmed physical observations unless the publishing source explicitly states that status.

Sunrise

+-------------+-------------+---------------------+
| Date | SSM-JA | Published Reference |
+-------------+-------------+---------------------+
| 15 May 2026 | 05:30:31 AM | 05:30 AM |
| 16 May 2026 | 05:29:32 AM | 05:29 AM |
| 17 May 2026 | 05:28:35 AM | 05:28 AM |
| 18 May 2026 | 05:27:39 AM | 05:27 AM |
| 19 May 2026 | 05:26:45 AM | 05:26 AM |
| 20 May 2026 | 05:25:53 AM | 05:25 AM |
| 21 May 2026 | 05:25:02 AM | 05:24 AM |
| 22 May 2026 | 05:24:14 AM | 05:24 AM |
| 23 May 2026 | 05:23:27 AM | 05:23 AM |
+-------------+-------------+---------------------+

Sunset

+-------------+-------------+---------------------+
| Date | SSM-JA | Published Reference |
+-------------+-------------+---------------------+
| 15 May 2026 | 08:03:39 PM | 08:04 PM |
| 16 May 2026 | 08:04:40 PM | 08:05 PM |
| 17 May 2026 | 08:05:40 PM | 08:06 PM |
| 18 May 2026 | 08:06:39 PM | 08:07 PM |
| 19 May 2026 | 08:07:38 PM | 08:08 PM |
| 20 May 2026 | 08:08:36 PM | 08:08 PM |
| 21 May 2026 | 08:09:33 PM | 08:09 PM |
| 22 May 2026 | 08:10:29 PM | 08:10 PM |
| 23 May 2026 | 08:11:25 PM | 08:11 PM |
+-------------+-------------+---------------------+

The objective is not bit-identical agreement with another service.

The useful observation is that the standalone deterministic release preserves a smooth, reproducible progression across consecutive astronomical states.

same release + consecutive dates -> coherent deterministic continuity


🌏 Six-City India Observational Witness

A second check looked at geographically distributed Indian locations on 28 May 2026, comparing SSM-JA with sunrise and sunset values published on India Meteorological Department Regional Meteorological Centre (RMC) live portals.

These RMC values are treated as official live-portal published values, not as independently confirmed physical observations unless the relevant RMC or IMD source explicitly states that status.

Sunrise

+-----------+-------------+--------------------+
| Location | SSM-JA | RMC Published |
+-----------+-------------+--------------------+
| New Delhi | 05:24:49 AM | 05:25:00 AM |
| Chennai | 05:41:30 AM | 05:42:00 AM |
| Kolkata | 04:52:19 AM | 04:52:00 AM |
| Mumbai | 06:01:08 AM | 06:01:00 AM |
| Nagpur | 05:32:05 AM | 05:32:00 AM |
| Guwahati | 04:31:51 AM | 04:32:00 AM |
+-----------+-------------+--------------------+

Sunset

+-----------+-------------+--------------------+
| Location | SSM-JA | RMC Published |
+-----------+-------------+--------------------+
| New Delhi | 07:12:06 PM | 07:12:00 PM |
| Chennai | 06:30:48 PM | 06:31:00 PM |
| Kolkata | 06:15:18 PM | 06:15:00 PM |
| Mumbai | 07:10:50 PM | 07:11:00 PM |
| Nagpur | 06:49:44 PM | 06:50:00 PM |
| Guwahati | 06:08:50 PM | 06:09:00 PM |
+-----------+-------------+--------------------+

The objective is not bit-identical agreement or formal astronomical certification. The comparison tests cross-regional observational coherence across geographically distributed witnesses.


🌙 Long-Horizon Vimshottari Dasha

Dasha is particularly interesting because small differences at the beginning of a calculation can propagate across decades.

The realization depends on elements including:

  • Moon longitude
  • Nakshatra placement
  • starting Dasha lord
  • birth balance
  • Dasha arithmetic
  • date normalization
  • civil-time interpretation

That makes long-horizon Dasha a useful cumulative stability test.

The core observation remains:

same input + same UTC moment + same release -> same Dasha realization

Testing included DST and non-DST regions, high-latitude and future-date cases, historically complex civil-time regions, and neighbouring-region comparisons.

The goal is stable, replayable realization within SSM-JA’s declared model — not universal agreement with every astrology program.


🕰️ Astana–Tashkent: When a Small Civil-Time Shift Can Move a Dasha Boundary by Months

A long-horizon stress test compared Astana, Kazakhstan and Tashkent, Uzbekistan using the same local date, local time, and declared UTC+5 assumption.

+-----------------+----------+----------------------+-------------------------------+
| Date            | Time     | Location             | SSM-JA Mahadasha End          |
+-----------------+----------+----------------------+-------------------------------+
| 21 May 2098     | 02:30 PM | Astana, Kazakhstan   | 25 November 2214              |
| 21 May 2098     | 02:30 PM | Tashkent, Uzbekistan | 25 November 2214              |
| 01 January 2050 | 09:30 AM | Astana, Kazakhstan   | 15 April 2157                 |
| 01 January 2050 | 09:30 AM | Tashkent, Uzbekistan | 15 April 2157                 |
+-----------------+----------+----------------------+-------------------------------+

Here, UTC+5 is a declared test assumption, not a prediction of future civil-time law.

In comparative testing, changing the civil-time assumption by just one or two hours shifted some century-scale Dasha boundaries by several months — in some cases approaching nine months.

SSM-JA, meanwhile, remained internally consistent across both Astana/Tashkent pairs under the same declared UTC+5 assumption.

This does not establish that one implementation is universally correct. It demonstrates how strongly long-horizon Dasha results can depend on civil-time interpretation.

different civil-time assumption -> potentially large long-horizon divergence

declared UTC offset -> reproducible realization

Timezone complexity does not disappear. It becomes visible, replayable, and testable.


🌐 Why Six Languages Matter

Panchang and Jyotish terminology is culturally and linguistically meaningful.

SSM-JA localizes important presentation areas while preserving the same underlying calculation:

same inputs + same release + different presentation language -> same calculation structure

English, Hindi, Kannada, Malayalam, Tamil and Telugu are six presentations of the same frozen deterministic release.


🪐 Panchang & Jyotish Software — Without Becoming a Prediction Engine

Calling SSM-JA astrology software does not make it a prediction engine.

It calculates and displays structure. It does not provide predictions, remedies, prescriptions, fortune-telling, or medical, legal, financial, or professional decision guidance.

observation before interpretation

calculation before judgment

Meaning remains outside the software.


🔬 What Has Been Verified in v3.7.41?

The frozen release underwent a final verification cycle covering the application, kernel, multilingual presentation, reports and Moon-cycle behavior.

Published release results include:

  • JavaScript syntax: 13/13 PASS
  • duplicate DOM IDs: 0
  • deterministic numerical regression: PASS
  • multilingual and print closure: 58/58 PASS
  • kernel and Moon-cycle closure: 12/12 PASS
  • six-language presentation: PASS
  • Share State integrity: PASS
  • responsive layout closure: PASS
  • embedded-kernel SHA-256 verification: PASS
  • final release-freeze audit: PASS
  • unresolved release-blocking failures: 0

The release verification records are published alongside SSM-JA on GitHub.

This is still a research and observation release.

Verification does not mean formal astronomical certification, production qualification, or third-party certification.


🧩 SSM-JA and SSM-JTK

SSM-JA sits inside the broader SSM-JTK — Symbolic Mathematics Jyotish Transit Kernel repository.

SSM-JTK -> deterministic transit-kernel foundation

SSM-JA -> browser-native Panchang and Jyotish application

SSM-JA turns the SSM-JTK kernel direction into a browser-native Panchang and Jyotish observation environment.


🔐 Privacy by Architecture

SSM-JA does not require:

  • an account
  • login
  • remote birth-data storage
  • cloud synchronization
  • server-side chart processing
  • a central chart database

Core chart calculation occurs locally in the browser.

Optional saved location presets remain local to the browser.

The design direction can be summarized as:

local observation without centralized personal-data dependency

For software dealing with birth details and location data, that architectural choice matters.


💡 The Bigger Idea

The most interesting part of SSM-JA may not ultimately be a particular chart or Panchang value.

It may be the architectural question behind it:

How much useful software can continue to resolve correctly when a runtime dependency stops being the sole authority?

For SSM-JA:

runtime ephemeris dependency during execution -> removed

while:

embedded deterministic observational structure -> retained

and:

reproducible supported realization -> remains

This does not make external ephemerides irrelevant.

It changes when they are required.

The scientific source can remain foundational without needing to remain an active runtime dependency every time the application executes.

That is the distinction being explored.



🔍 Inspect, Verify and Challenge It

The complete SSM-JA release, documentation and verification material are public:

SSM-JA — GitHub Repository

Researchers, astronomers, Jyotish practitioners, software engineers and reproducibility researchers are encouraged to:

use it • compare it • reproduce it • inspect it • challenge it

The project should be judged through observable behavior and reproducibility, not assertion.


🌐 Explore the Wider Shunyaya Ecosystem

SSM-JA is one applied system within the wider Shunyaya structural research ecosystem.

Shunyaya Symbolic Mathematics — Master Documentation

The broader direction asks whether declared structure can preserve reproducible outcomes while reducing dependence on runtime mechanisms that were previously treated as sole authorities.

For SSM-JA, that becomes:

embedded deterministic structure -> reproducible Panchang and Jyotish observation


✨ Closing Reflection

SSM-JA began with a simple architectural question:

Could useful Jyotish observation remain reproducible without continuously returning to an external ephemeris service during execution?

v3.7.41 turns that question into a practical six-language browser application.

Open the browser. Choose your language. Use the Panchang and Jyotish software. Take the observatory offline whenever you want — as one file.


✨ One File. Six Languages. One Deterministic Jyotish Atlas.

Panchang • Rasi • Navamsa • Dasha • Transits • Reports

Six languages. One frozen release. Reproducible by design.

same input + same release -> same deterministic chart structure

Open it. Use it. Verify it. Take it offline.

SSM-JA v3.7.41


Scope: Observation • Education • Research
Not for critical decision-making.


OMP

Comments

Popular posts from this blog

🌟 SSM-AIM — A Tiny 108 KB Verifiable Personal AI With a Big Promise

🌟 SSM-AIM Mini — A 23 KB Transparent Personal AI Built for Every Human — Full Source Code Uploaded

🌟 When Geometry Explains the Iconic Leaning Tower of Pisa through Reproducible Structural Mathematics