42
Active lenses
GLOBAL · 4 national · IN states + UTs
Coverage isn't equal across all 42 lenses — and pretending it is would be dishonest. This page shows the truth: where we have depth, where we're thin, and which lenses we're actively scaling.
The default lens. Topics that genuinely transcend borders — tech, science, climate, AI/agents, geopolitics. About a third of all output. Articles published to any other lens are also published to GLOBAL by default.
Anchor markets at v2.0: India national, United States, United Kingdom, Bangladesh, Canada. Country expansion follows reader demand and source-coverage depth.
28 Indian states + 8 Union Territories under IN-*. Where we have depth we go deep; where we are thin we say so. The Lighter Coverage Banner names the threshold and walks the fallback chain (e.g. IN-MH → IN → GLOBAL).
Country-level: PK, AE, SG, DE, FR, JP, AU, BR — gated on source-corpus depth. India: state-level depth ramps follow stringer recruitment. Cross-region buckets (EU, SEA) explored v2.5+.
Bars are scaled to the busiest lens this week (50 stories). Anything below 7× the daily floor is thin; below 40% of that is critical — we do not pretend it’s a full lens.
| Lens | Stories · 7d | Today | vs benchmark | Status |
|---|---|---|---|---|
| Global | 0 | 0 | Not yet live | |
| United States | 0 | 0 | Not yet live | |
| United Kingdom | 0 | 0 | Not yet live | |
| India | 0 | 0 | Not yet live | |
| Bangladesh | 0 | 0 | Not yet live | |
| Canada | 0 | 0 | Not yet live | |
| Andhra Pradesh | 0 | 0 | Not yet live | |
| Arunachal Pradesh | 0 | 0 | Not yet live | |
| Assam | 0 | 0 | Not yet live | |
| Bihar | 0 | 0 | Not yet live | |
| Chhattisgarh | 0 | 0 | Not yet live | |
| Goa | 0 | 0 | Not yet live | |
| Gujarat | 0 | 0 | Not yet live | |
| Haryana | 0 | 0 | Not yet live | |
| Himachal Pradesh | 0 | 0 | Not yet live | |
| Jharkhand | 0 | 0 | Not yet live | |
| Karnataka | 0 | 0 | Not yet live | |
| Kerala | 0 | 0 | Not yet live | |
| Madhya Pradesh | 0 | 0 | Not yet live | |
| Maharashtra | 0 | 0 | Not yet live | |
| Manipur | 0 | 0 | Not yet live | |
| Meghalaya | 0 | 0 | Not yet live | |
| Mizoram | 0 | 0 | Not yet live | |
| Nagaland | 0 | 0 | Not yet live | |
| Odisha | 0 | 0 | Not yet live | |
| Punjab | 0 | 0 | Not yet live | |
| Rajasthan | 0 | 0 | Not yet live | |
| Sikkim | 0 | 0 | Not yet live | |
| Tamil Nadu | 0 | 0 | Not yet live | |
| Telangana | 0 | 0 | Not yet live | |
| Tripura | 0 | 0 | Not yet live | |
| Uttar Pradesh | 0 | 0 | Not yet live | |
| Uttarakhand | 0 | 0 | Not yet live | |
| West Bengal | 0 | 0 | Not yet live | |
| Andaman and Nicobar Islands | 0 | 0 | Not yet live | |
| Chandigarh | 0 | 0 | Not yet live | |
| Dadra and Nagar Haveli and Daman and Diu | 0 | 0 | Not yet live | |
| Delhi | 0 | 0 | Not yet live | |
| Jammu and Kashmir | 0 | 0 | Not yet live | |
| Ladakh | 0 | 0 | Not yet live | |
| Lakshadweep | 0 | 0 | Not yet live | |
| Puducherry | 0 | 0 | Not yet live |
Different from the table above (bars there are scaled to the busiest lens). Here every bar is normalized against the floor for that specific lens — so a Lakshadweep meter at 100% means 1 story today against a daily floor of 1, not 1 story against the global 487/wk benchmark. This is the meter the homepage Lighter Coverage Banner uses to decide warning vs critical.
No lenses are currently flagged critical. The Lighter Coverage Banner appears on the homepage when this changes.
A row in v2.articles with status = 'published' and published_at > now() - 7d, bucketed by every lens row in v2.article_lenses for that article. Counted via the nightly lens_daily_volume rollup. Newsletters, briefings, and revisions don’t count.
Editorial call: 7× the daily floor (one per day) is the floor for what a reader could call “a section.” Below 40% of that, we no longer pretend it’s a section. Numbers will move with volume; we’ll note the change in this page’s revision log when they do.
Hiding gaps is what every other publisher does. We show them on purpose — same logic that puts the bias meter on every article. If we’re light somewhere, you should know before you click.
Public JSON at /api/lens-coverage ships with v2.1 — refreshed hourly, no auth, build whatever dashboard you want. Until then, query v2.lens_daily_volume directly via the public Supabase URL ( /methodology/lens lists the table contracts).