Dashboard
Today's open-source intelligence picture
Ingestion volume — last 14 days
High relevance — discovered in last 48h
Items NIGRANI added in the last 48h — the item's own date/time may be older (common for X, whose search can surface a post up to 7 days after it was made).
Map
Geo-tagged activity across Punjab, Rajasthan and Gujarat
Browse & search
Search the full intelligence record by keyword, tag, region, or date
Pattern analysis
Aggregate trends across regions and factions — no individual-level tracking
Active alerts
Explore & trends
Notable sentiment
Notable severity
Notable accounts
Regional & faction activity
Active alerts
Statistical spikes in geo/faction/keyword mentions compared to their normal baseline — a different detection method from the notable sentiment/severity tabs, which flag individual extreme items rather than an unusual volume pattern.
Explore by state or faction
Not tied to an alert — pick any state and/or faction directly to plot or report on everything currently tagged with it.
Sentiment & severity trend
Notable public sentiment
Individual public posts/articles showing extreme sentiment toward the armed forces, with signs of genuine reach — not a profile of any person or account. Deliberately a high bar: most items, even negative ones, won't appear here.
Notable high-severity events
Individual reports of ambushes, attacks, or casualties with signs of genuine reach — independent of sentiment toward the armed forces.
Notable accounts
X/Telegram/YouTube ACCOUNTS (not individuals — a handle is not a confirmed identity) with a repeated pattern of hostile-sentiment or high-severity posts, or manually added by an analyst for surveillance from any item's detail view. Organized by platform below.
Regional activity (7 days)
Faction activity (30 days)
Faction–region co-occurrence (30 days)
Which factions are mentioned together with which states — pairs with at least 2 co-mentions, highest first.
| Faction | State | Co-mentions |
|---|
Predictive analysis
Forward-looking risk indicators to help prioritise your attention — decision support only, not an automated trigger for action
Overview
Area historical profile
Hotspot forecast
Faction watch list
Adversary assessment
Narrative heat
Account behaviour
Cross-sector
Risk calendar
Coverage gap
Field reports
Scenario / What-if
Critical — review and verify immediately
High — review within the day
Medium — worth monitoring, no immediate action needed
Low — normal baseline activity
What do these numbers mean? (plain-language glossary)
Area historical profile
- Insurgency/terrorism/espionage index (0–100)
- ONE combined score, not three separate counts. It rises when more of this area's past reporting involved a known militant/insurgent faction, or matched terrorism/espionage-linked keywords (e.g. "infiltration", "sleeper cell"). Older activity counts for less than recent activity.
- Severe-event index (0–100)
- How much severe activity (individual incidents rated 4 or 5 out of 5 for severity) this area has racked up historically. Higher = a worse track record. Like the index above, this describes the past — it isn't a forecast by itself.
- Historical tier
- Critical / High / Medium / Low — this area's overall long-term risk level, blending the two indexes above with its long-run sentiment trend into one label.
Hotspot forecast
- Severity slope (per day)
- Is the average "how bad" rating of recent stories in this area rising or falling, and by how much each day? Positive = getting worse day by day over the last 30 days; negative = calming down.
- Sentiment slope (per day)
- Same idea, but for tone. Negative = reporting is drifting more hostile each day; positive = tone is improving.
- Volume velocity
- How many stories came from this area in the last 7 days, compared to its normal rate. 1.0x = normal, 2.0x = double the usual volume, 0.5x = half.
- Historical prior (0–100)
- This area's long-term Historical Threat Index (same number as its Historical tier score) — blended in alongside this week's live trend, so a district with a rough track record isn't graded purely on the last 30 days alone.
Faction watch list
- Baseline (mentions/week)
- How often this faction is normally mentioned per week, before the recent window. Compare it against "Recent mentions" to see if it's suddenly getting talked about a lot more (or less) than usual.
Account behaviour
- Posting cadence (posts/week)
- How many times per week this account typically posts. Useful for spotting a sudden burst of activity above someone's normal pace.
Narrative heat
- Smoothed sentiment
- The average day-to-day tone (on a −5 hostile to +5 supportive scale) for this district/topic, smoothed so one unusually angry or positive single story doesn't swing the number by itself.
- Baseline sentiment
- That same district or topic's OWN normal/average tone over its history — its personal "usual." A district that's always a bit heated is compared to its own past, not to a calmer district's bar.
Probability, clusters & actionable insights
- Probability-style % (e.g. "escalation probability", "resurgence probability")
- A transparent, reproducible squashing of the exact same trend-slope already shown elsewhere on screen, re-expressed on a 0–100 scale instead of a raw score — not a black-box machine-learning output, and always clamped short of 0% or 100% so it never implies false certainty.
- Cluster (e.g. "Critical & Escalating")
- A simple, explainable grouping by tier + trend-direction — not machine clustering. Items land in the same cluster only because they share the same tier and the same up/down/flat direction, so the boundary is exactly as inspectable as the tier and trend labels it's built from.
- Recommended action / actionable insight
- A one-line concrete next step (e.g. "Escalate for immediate review") mapped straight from an item's tier and trend direction — the same standing guidance the tier legend at the top of this page already states, just attached to the specific item it applies to instead of left as a general rule.
- Flag-risk tier (Account behaviour) / Recurrence tier (Risk calendar)
- These two modules never had a Critical/High/Medium/Low classification of their own — these tiers bucket their existing numbers (flagged ratio; historical correlation count) onto the same scale every other tab already uses, so every module now has both a continuous number and a categorical label.
Confidence, calibration & ground truth
- Confidence: Low / Medium / High (the small "Conf:" tag next to a tier badge)
- Independent of the tier itself — this says how much sample size, source diversity, and AI extraction certainty back THIS specific call. A "Critical" hotspot built from 3 items and 1 source is real, but should be trusted less than a "Critical" built from 40 items across 5 independent sources. This never changes the tier or score, only how much weight to give it.
- Calibration / track record (Overview tab)
- Of every past High/Critical forecast that's now had at least 14 days to play out, how often did a real severity 4-5/5 event actually follow in that same district/faction/topic? Entirely automatic — the platform checks its own past calls against what actually happened next, no manual grading required. Shows "not enough history yet" until forecasts have had time to age.
- Field reports
- Manually-submitted, human-corroborated ground truth — kept entirely separate from the OSINT-derived items everywhere else on this page. Use this to record what's actually been confirmed (or contradicted) in the field, with its own credibility label (unverified/plausible/corroborated).
- Response assets / resource-tied recommended actions
- A small inventory of available QRTs, patrols, drones, and civic liaison teams (Overview tab). When a hotspot is Critical or escalating-High, the recommended action names one of these directly if it's marked available in that district, instead of generic advice.
- Narrative "Drivers" line (Narrative heat tab)
- Tallies that row's own driving items (the same ones the "Driving items" button opens) by their AI-classified event type into security-force-facing (ambush, IED, arms recovery...) vs. governance/political (protests, AFSPA debate...) vs. other — so a heat score's underlying cause is visible without opening every item.
Adversary capability & intent assessment
- Capability tier / score (0–100)
- Demonstrated ability to act, not just how often a faction is talked about — built from recency-weighted offensive incidents (ambush/encounter/IED) it was tied to, how many districts it's been active across, and its current operational status, reduced when security forces have recovered arms tied to it. Separate from resurgence: a faction can be quiet-but-capable just as easily as loud-but-hollow.
- Intent tier / score (0–100)
- What a faction appears to WANT — built from recency-weighted coercive/extortion activity, stated political demands reported as news, and whether sentiment on its own coverage is trending more hostile. High capability with low intent, or the reverse, is itself useful information, so the two are always shown side by side rather than blended into one number.
- Assessment narrative
- An auto-generated, plain-English one-liner explaining exactly which observed signals drove that faction's capability and intent scores this pass — the same transparency principle as the driver-breakdown feature elsewhere on this page.
Scenario / What-if comparison tool
- What this is
- Lets an analyst override one or more live inputs (e.g. "what if the severity trend doubled") and see what score/tier the platform's REAL formula would produce — using the exact same calculation the live Hotspot Forecast / Faction Watch List tabs run, not a separate approximation. Nothing here is saved to the database.
- Baseline vs. scenario
- "Baseline" is the district's or faction's current real computed score. "Scenario" is what that same formula outputs once your overrides are applied on top of it. Compare the two tiers/scores side by side to gauge how much a hypothetical change would actually move the needle.
- Important limitation
- This is a recompute of the existing formula under hypothetical inputs — it is NOT a prediction of what will actually happen, and does not itself trigger any alert, snapshot, or calibration record.
A score here is a probability estimate built from patterns in open-source reporting. It is decision support only — not a forecast of certainty — and it does not by itself authorize any operational action. Always verify against ground-level sources before acting.
Calibration / track record
Is this platform's own track record of past High/Critical calls actually good? Checked automatically against what happened afterward — see the glossary above.
Actionable insights
The highest-priority items right now, each with a concrete recommended next step — not just a score. Recommendations name an available response asset directly when one is on hand for that district (see "Response assets" below).
Response assets
QRTs, patrols, drones, and civic liaison teams currently on record — mark one unavailable/deployed as its status changes, so recommended actions above stay accurate.
Active alerts
Top hotspot forecasts
Top faction watch list
Next risk calendar windows
Foundational layer, not itself a forecast. Each district's long-run insurgency/terrorism/espionage history, sentiment trend toward the armed forces, and severe-event record, recency-decayed so a sustained real cooling-off measurably lowers a district's score over time. Every tab on this page weighs its live signal against this baseline.
| District | Historical tier | Insurgency/terrorism/espionage index (0–100) | Sentiment trend (avg) | Severe-event index (0–100) | Total severe events |
|---|
Live trend-slope (severity, sentiment, volume velocity) blended with the district's own history as a prior — the same current trend can land in a different tier depending on that district's track record.
| District | Risk tier | Trend | Outlook (next 30 days) | Severity slope (per day) | Sentiment slope (per day) | Volume velocity | Historical prior (0–100) |
|---|
Mention trend-slope, status changes, and a small analyst-curated calendar of faction-specific anniversary/trigger dates — deliberately rule-based and transparent rather than a black-box model.
| Faction | Status | Resurgence tier | Recent mentions | Baseline (mentions/wk) | Resurgence probability | Next trigger date | Status changed recently |
|---|
Faction trigger dates (anniversaries)
| Faction | Label | Date |
|---|
What a faction can actually DO (capability) versus what it appears to WANT (intent) — two different questions from the Faction watch list's mention-volume tracking. Rule-based and transparent, built from event types and sentiment already collected elsewhere on this page — see the glossary above.
| Faction | Status | Capability tier | Offensive activity (weighted) | Arms recoveries | Geographic reach | Intent tier | Coercive activity (weighted) | Stated intent (weighted) | Assessment narrative |
|---|
Smoothed daily sentiment per district/topic, judged against that same district or topic's OWN historical baseline — never one flat platform-wide threshold, so a naturally noisier district isn't unfairly flagged against a calmer one's bar.
| Dimension | Value | Heat tier | Smoothed sentiment | Baseline sentiment | Probability of continued hostile drift |
|---|
A simple historical-rate calculation ranking already-tracked accounts (see Pattern analysis > Notable accounts) by how likely their next post is flagged — purely to prioritise limited analyst review time. Entity-level only, never a judgement about a person.
| Account | Platform | Priority score (0–100) | Flagged ratio (≈ probability) | Flag-risk tier | Total items | Posting cadence (posts/wk) |
|---|
Unique to NIGRANI's federated five-sector architecture — time-lag correlation between this sector's and a peer sector's recent faction/keyword mention activity. Requires SYNC_SHARED_KEY and at least one active peer server (Admin > Network & sync).
Rolling 90-day forward risk calendar combining the generic trigger dates below and each faction's own anniversaries, each with a historical correlation count drawn directly from the severe-event record.
| Date | Days until | Label | Scope | Historical correlation | Recurrence tier |
|---|
Generic trigger dates (elections, festivals, AFSPA review windows, ...)
| Label | Category | Date | Scope |
|---|
Several sources tied to the same region failing simultaneously — a different pattern from any one source's own health warning. A sudden information vacuum is itself a signal.
Manually-submitted, human-corroborated ground truth — kept entirely separate from the OSINT-derived items in every other tab on this page. Use this to record what's actually been confirmed (or explicitly contradicted) in the field, so a call isn't judged on open-source reporting alone.
| Submitted | District | Faction | Report | Credibility | By |
|---|
Override one or more live inputs and see what the platform's REAL scoring formula would produce — the exact same calculation the Hotspot Forecast / Faction Watch List tabs run, not a separate approximation. This does not predict what will actually happen and nothing here is saved.
Comparison (this session only)
Scenarios you've added below are kept only in this browser tab — refreshing the page clears them.
| Entity | Inputs | Score | Tier | |
|---|---|---|---|---|
| No scenarios added yet. | ||||
Social search
Live search against X — results cover the last 7 days only, and nothing is saved until you import it
Team chat
LAN-wide discussion for all NIGRANI users
Daily reports
Auto-generated each day at 06:00 IST
Commander's Briefing
A one-page summary for circulating up the chain — headline stats, trend direction, and top events. Not a substitute for the full daily report below.
Admin
User accounts, taxonomy, and audit log
Account
Change your password
Password and two-factor authentication settings live in one place for every user now, rather than duplicated here.