Gold Rate Tracker
Buying gold jewellery in India? This page tells you today's 22K gold rate, how fresh that number is, and whether today's price is cheap or expensive compared with the recent past — in plain language, for free, with no ads and no sign-up.
Open it: https://gaurav-gandhi-2411.github.io/gold-rate-tracker/ — works in any phone browser, and can be installed like an app (iPhone: Safari → Share → Add to Home Screen; Android: Chrome → Install app).
Screenshots of the live page. Numbers in them are real production data at capture time, not mocked.
What you'll see
- Today's 22K rate, with a date on it. The price is based on the rate published by IBJA (the India Bullion and Jewellers Association — India's national bullion benchmark) and upgraded to a directly-read Tanishq rate when that is available. Every price carries a "last updated" label, so you always know how old it is. On days IBJA doesn't publish (weekends, holidays) you see the last published rate, clearly dated — never a stale number pretending to be today's.
- How fresh the data is. The data is refreshed automatically several times a day. Over the last 7 days, Tanishq's listed price was typically read every 4.3 (as of 2026-10-29) hours; the longest wait (counting any wait still going) was 10.3 hours. If updates stall, the page shows a warning banner instead of quietly showing an old price.
- A likely range, not just one number. Next to the price is a range the real rate usually falls within. It's aimed at being right 80% of the time; checked against real IBJA rates, in a test on past weeks it landed inside the range about 7 times out of 10 — a bit narrower than it should be, so treat it as a guide. We re-check this every week; How we know has the exact numbers behind both figures.
- "Is today cheap or expensive?" A plain-language read of where today's price sits compared with the past few weeks and months — near a recent low, near a recent high, or in between — and whether prices have recently been steadying or still falling. This describes what has already happened.
- How much prices typically swing over a few days, so a small daily move doesn't look like a big one.
Want phone alerts when the price moves? They are available if you run your own copy of the project (free, via the ntfy app) — see For developers.
What it won't tell you — and why
No prediction of where the price goes next. No "% chance it rises." No buy or sell advice.
That's deliberate, not an omission. Every week the project tests whether any model can call the next move better than the simple rule "gold usually goes up, so just guess up". So far none has, with enough evidence to trust it, so the page shows nothing rather than a guess dressed up as insight (ADR 019, ADR 020). Even if a model someday passes that test, it still cannot appear on the page without a separate, explicit human sign-off (ADR 036).
The latest weekly results, updated automatically:
| Question | Honest answer | Source |
|---|
| Can any model call tomorrow's direction? | No, at either timeframe tested. Next day: <!--METRIC:data/direction_baseline.json#horizons.h1.logistic_metrics.accuracy:pct1 | n=horizons.h1.n_test_folds |
| Does the price forecast beat "just use today's price"? | No. Naive flat-hold: ₹249/g avg error. Chronos-Bolt-Tiny: ₹292/g avg error — 17% worse, over 209 walk-forward folds (p≈0). So the page shows today's price as the headline, not a forecast. | data/backtest.json @ ad42160 |
| Is the headline's own "likely range" well-calibrated? | Not yet known either way. Since a July 2026 fix (ADR 022), it has contained the real price <!--METRIC:data/coverage_metrics.json#coverage:pct1 | n=n |
How it works
No server, no database, no paid API. A scheduled GitHub Actions job fetches the IBJA rate (and tries Tanishq), works out the calibrated estimate and range, and commits the results as small JSON files; GitHub Pages serves a static web app that reads them. It costs nothing to run.
- Where the price comes from (ADR 025). IBJA is the primary source: it publishes a daily benchmark reliably. Tanishq's site is harder to read automatically — over the last 7 days a direct read succeeded 100.0% (n=41, as of 2026-10-29) of the time — so it only ever upgrades the IBJA-based estimate, never replaces it.
- How the estimate is made. Retail 22K prices track the IBJA rate very closely (fit R²=0.98 (n=105, as of 2026-10-15)), so the page converts IBJA's rate into an estimated retail rate, and its range comes from how far past estimates actually missed (ADR 027).
- The page itself is plain HTML + JavaScript that reads those JSON files directly. No accounts and no ads. It counts visits with GoatCounter, a cookieless counter that stores nothing in your browser and says it keeps no internet address; the page footer says so. Beyond GitHub itself, it loads its chart library from a public CDN (jsDelivr) and uses an error tracker (Sentry) that reports crashes in the page so they can be fixed.
flowchart TD
subgraph cron["check-price.yml — scheduled"]
A["IBJA fetch<br/>primary source"] --> C
B["Tanishq read<br/>opportunistic enrichment"] --> C
C["prices.json<br/>ibja_rates.parquet"]
end
C --> D["ml.inference<br/>today's price headline<br/>+ IBJA calibration"]
D --> E["forecast.json"]
E --> F["ntfy.sh alerts"]
E --> G["commit data JSON to master"]
G --> H["GitHub Pages<br/>static web app"]
H --> I(("Your phone"))
subgraph weekly["eval-direction.yml — weekly"]
J["feature store"] --> K["direction models"]
K --> L{{"beats 'always guess up'<br/>with significance?"}}
L -->|"no"| M["stays hidden<br/>(ADR 019)"]
end
style M fill:#3a2418,stroke:#c67a4b,color:#e8c8a8
style D fill:#2a2015,stroke:#d4932a,color:#f0d9a8
For developers
Run your own copy (fork, set your own ntfy topic, enable Pages), alert setup, and troubleshooting: see docs/RUNBOOK.md → Running your own copy. Operating this deployment (rollback, CI debugging, staleness response, scraper and runner ops): docs/RUNBOOK.md. System design: docs/ARCHITECTURE.md. Audit history: docs/SESSION_AUDIT_2026-08.md.
| Path | What |
|---|
index.html, app.js, service-worker.js | The web app (what users see) |
scraper/ | Tanishq read (Node; a plain-HTTP path is tried first but is blocked by Cloudflare — it has succeeded 0 of <!--METRIC:data/tanishq_scrape_success_rate.json#n:int |
ml/ | Inference, calibration, notifications, the direction-eval harness |
data/ | Committed price/forecast/eval JSON the web app reads |
.github/workflows/ | check-price.yml (scheduled data refresh), lint.yml, eval-direction.yml, weekly-backtest.yml, scraper-canary.yml |
docs/ | RUNBOOK, ARCHITECTURE, ADRs, CURRENT_STATE, DIRECTION_SIGNAL_STATUS |
Every number in this README is injected from data/*.json by scripts/inject_metrics.py and re-checked in CI (docs-freshness), so it can't silently go stale — never type one by hand.
Design decisions (ADRs)
- ADR 005 — always report when the model loses to the simple baseline
- ADR 012 — today's price as the headline; the Chronos model only as a hidden companion
- ADR 019 — the direction signal doesn't beat the base rate; ship nothing
- ADR 025 — IBJA primary, Tanishq opportunistic enrichment
- ADR 036 — no direction signal reaches users without an explicit, human-approved promotion record
AI/LLM usage
Built and maintained with heavy use of Claude Code — architecture decisions, ADRs, the ML pipeline, the web app, and CI are all human-directed but substantially AI-implemented. Documented here rather than hidden: every non-trivial design choice has a linked ADR explaining the why, written and kept current regardless of who typed the diff.
License
MIT
