Supporting evidence
Rainfall data and insurance
The complete artifacts and detailed records behind the account. Current public references, original work and proposed designs retain their labels.
Detailed material
The problem
A rainfall grid can group nearby locations even when their conditions differ. More local information would matter only if it was valid and usable for the insurance-pricing decision.
Use finer information for a defined pricing task
The starting constraint was publicly available 25 km rainfall information and the cost of obtaining more detail. The project developed a 10 km by 10 km model using satellite estimates, local weather stations, terrain and historical rainfall patterns.
The requirement was not simply a smaller grid cell. I worked on connecting that output to the local information an actuarial team could use in premium tables. The evidence does not provide a publishable acceptance threshold or show that every finer cell was more accurate.
Keep the sandbox milestone distinct
The historical account describes grid development and actuarial pricing use. It separately describes the related PMFBY sandbox as continuing into execution. That stage is not upgraded to a completed insurance rollout.
The current FinStac product range is a separate, later reference. Its advertised cover and distribution do not establish my delivery of each product or the issuance and claims outcomes of the historical grid work.
Grid scope and reported use
Documented scope: the rainfall grid changed from 25 km to 10 km × 10 km. This describes spatial resolution, not model accuracy.
An earlier career record reports a 27% premium reduction for a use case, without its cohort, comparison or period. The related PMFBY sandbox is recorded as ongoing execution, not completed rollout.
Resolution must serve a validated decision
Moving from 25 km to 10 km specifies spatial resolution, not accuracy. In another data product I would ask what local distinction the receiving team needs, how that distinction is validated and what changes in its decision. That is the useful connection between a technical improvement and product value.
Validation before interpreting resolution
Ground-truth work across monsoon cycles formed part of the account, alongside actuarial collaboration. The product link was from rainfall information to a pricing task; grid development alone was not treated as the whole institutional delivery.
No redacted pricing example or validation-to-acceptance decision is supplied. The reconstructed workflow therefore identifies the documented inputs and handoff without inventing a station-level result, pricing rule or measured causal effect.
Current FinStac context · October 2026
FinStac’s October 2026 page describes agricultural cover and climate triggers. Its current offering includes crop, cattle, motor, livestock and fishery insurance, DigiFasal self-service, app/API access, POS agents and paravets. This is wider product context, separate from the historical rainfall contribution.
Optional current public-page montage
A silent overview of FinStac’s 13 October 2026 public pages. It does not show the historical grid model or an authenticated pricing task.
Walkthrough descriptionSilent visual walkthrough using captured public pages and illustrations. Upaj FinStac. It presents public product information; authenticated application and transaction screens were not recorded.
Archived current cover and distribution
The gallery records the public cover, DIY and distribution propositions, including heat spells, flash floods and extreme rainfall. It does not document historical model performance, policy issuance or claims performance, and does not substantiate advertised “first” claims.
Notes and sources
- Source: earlier historical career record, self-reported grid/pricing scope and ongoing PMFBY sandbox. The record does not publish the actuarial comparison supporting the 27% figure.
- FinStac media was captured on 13 October 2026 and describes the wider current insurance catalogue. It is not a historical rainfall-model, policy-issuance or claims-performance record.
Upaj portfolio public reference · Reference pages 1–6 · 13 October 2026 · Post-tenure public product capture
Authored walkthrough from public product captures · 13 October 2026 · Silent generated reference; no authenticated task executed