← Back to intel feed

Intel methodology

How the conservation intelligence feed is built, what each signal means, and where its limits are.

This page documents the live signal sources: the C-INTEL press feed and five satellite watches - fire, forest, vegetation, surface water, and night-time lights. The press taxonomy below is a working draft, open to revision - see the feedback note in the News section.

News (C-INTEL)Fire watchForestVegetationWaterNight-time lights
Press feed

News (C-INTEL)

The bottom line: Each week C-INTEL reads the African conservation press across 46 in-scope countries and surfaces only the few items that should change what a grant officer does next.

C-INTEL screens the African conservation press and surfaces the handful of items each week that should move a grant officer's hand. It is screening, not due diligence: items are neutral, attributed, and carry no editorial synthesis. Its in-scope set spans 46 African countries, and items surface as qualifying press appears.

How an item reaches the digest

  1. Ingest articles from a registered set of regional and national outlets (English and Portuguese).
  2. Classify each article with a language model against a fixed taxonomy: in-scope countries, themes, severity, and which protected areas are named.
  3. Score relevance and confirm protected-area matches.
  4. Translate non-English items to English.
  5. Summarise with a draft-then-critic pass, so each summary is checked against the source before it ships.
  6. Assemble the weekly digest, ordered by severity.

Screening philosophy

The filter is exclusion-based with a positive bar. It deliberately drops whole categories of noise (listed under Exclusions), and keeps only items that clear the bar of being materially useful to a funding decision. The model is told to be conservative: when unsure, it under-flags rather than over-flags, and prefers "informational" to "material".

Tiers drive priority

Every topic in the taxonomy carries a tier. The tier sets the default severity and where the item lands in the digest. This is the key point for proposing themes: a topic is not just a label - its tier decides how loudly it surfaces.

TierMeaningDefault severityDigest behaviour
T1Material to grant decisionsmaterialAlways surface in digest, lead position
T2Context for funding decisionswatchSurface in digest, body position
T3Background signalinformationalSurface in digest, footer position

Theme taxonomy

Twelve themes, each with tiered topics. This is a working draft, open to revision.

Politics and governance
  • T2 watchCabinet changes - Environment, Wildlife, Tourism, Mining, Land Affairs portfolios
  • T2 watchWildlife act, forest act, EIA regulation, hunting policy amendments
  • T1 materialCourt rulings on PA status, concession contracts, community land rights
  • T2 watchCITES delegation positions and CoP outcomes
  • T1 materialConstitutional challenges to PA boundaries or operator agreements
PA status and land tenure
  • T1 materialPADDD events: downgrading, downsizing, degazettement, boundary changes
  • T1 materialStatutory instruments altering PA legal status
  • T1 materialOperator-government management agreement signings, renewals, terminations
  • T1 materialConcession revocations, expropriation, nationalisation
  • T1 materialSudden tax or fee impositions on operators and lodges
  • T2 watchCommunity land claims, evictions, conservancy formation
Mining, oil and gas, infrastructure
  • T1 materialMining licence grants, transfers, renewals within 25km of keystone PAs
  • T1 materialOil and gas block awards in keystone landscapes
  • T1 materialHydropower dam and pipeline routing decisions
  • T2 watchIllegal mining incursions, artisanal encroachment
  • T2 watchMining cadastre updates
  • T2 watchMajor road, rail, port infrastructure adjacent to PAs
Wildlife crime
  • T1 materialRanger fatalities, attacks, ambushes
  • T1 materialElephant, rhino, big cat, pangolin poaching incidents with carcass counts
  • T2 watchTrafficking seizures - ivory, horn, scales, big cat parts, live trade
  • T2 watchKingpin arrests, court cases, sentencing
  • T2 watchCross-border trafficking route disclosures
Conflict and security
  • T1 materialArmed group activity within 50km of keystone PAs
  • T1 materialNamed-group operations - Ansar al-Sunna, ADF, JNIM, M23 and others
  • T2 watchRefugee and IDP camp formation near PAs
  • T2 watchACLED event clusters with conservation-relevant geography
  • T2 watchState security force operations affecting PA access or operator logistics
Conservation finance
  • T1 materialPeer foundation grant announcements - Bezos Earth Fund, Wyss, Wildcat, Bertarelli, Bloomberg, Oak, Mulago, Arcus, NatGeo, Packard, Moore
  • T2 watchBilateral and multilateral aid allocations - USAID, GIZ, AFD, FCDO, EU, World Bank, GEF, GCF
  • T1 materialDebt-for-nature swap announcements and term sheets
  • T2 watchCarbon project transactions in keystone landscapes - Verra, Gold Standard, ART-TREES listings, issuances, cancellations, buyer disclosures
  • T2 watchBiodiversity credit pilots and nature-based solutions deals
Operators
  • T1 materialLeadership changes at AP, PPF, WCS, FZS, AWF, Panthera, WWF at keystone sites - CEO, country director, park warden
  • T1 materialOperator financial disclosures, audits, governance issues
  • T2 watchNew operator partnerships, mandates, country exits
  • T3 backgroundOperator annual reports, park reports, impact data
  • T2 watchOperator board changes and major donor disclosures
Tourism and macroeconomy
  • T2 watchTourism arrivals data and hotel occupancy by country
  • T2 watchAirline route changes affecting keystone PA access
  • T2 watchLodge openings, closures, ownership changes at keystone sites
  • T2 watchTravel advisories from US, UK, EU, Australia
  • T1 materialSovereign credit downgrades, IMF programmes, FX moves affecting operator cost base
Wildlife population and ecology
  • T2 watchAerial census results and population estimates
  • T2 watchIUCN Red List changes for keystone-PA species
  • T1 materialMass mortality events - anthrax, poisoning, drought die-offs, disease outbreaks
  • T2 watchMajor translocations, reintroductions, founder-population events
  • T2 watchHuman-wildlife conflict hotspots, retaliatory killings, crop raiding
Climate and environment
  • T2 watchCyclones, floods, droughts affecting specific PAs
  • T2 watchFire season severity - FIRMS hotspot density
  • T3 backgroundMajor rainfall anomalies during key wildlife seasons
  • T2 watchForest cover change at landscape scale - JRC TMF, Hansen GFC
  • T2 watchRiver system flow changes affecting transboundary PAs
Cross-border and TFCAs
  • T2 watchKAZA, Greater Limpopo, Mid-Zambezi, Selous-Niassa corridor developments
  • T2 watchBilateral wildlife and conservation agreements
  • T2 watchTransfrontier ranger cooperation, joint patrols
  • T3 backgroundCross-border community conservancy initiatives
Community and local governance
  • T2 watchBenefit-sharing disputes - operators, communities, government
  • T3 backgroundCommunity conservancy elections and leadership changes
  • T3 backgroundLocal NGO and CBO formation, dissolution, funding changes
  • T3 backgroundTraditional authority engagement with PA management
  • T2 watchResettlement disputes around PA buffer zones

Entities tracked

Alongside the themes, the system actively watches named entities. These are also open to additions.

Operators
African Parks Peace Parks Foundation WCS FZS Frankfurt Zoological Society AWF African Wildlife Foundation WWF TNC The Nature Conservancy Panthera Wildlife Vets Conservation Lake Tanganyika Niassa Carnivore Project Gorongosa Project Greg Carr Foundation Game Rangers International Conservation Lower Zambezi Zambian Carnivore Programme Kasanka Trust Conservation South Luangwa
Funders
Rob Walton Foundation RWF Walton Family Foundation Bezos Earth Fund Wyss Foundation Wildcat Foundation Bertarelli Foundation Bloomberg Philanthropies Gates Foundation Oak Foundation Mulago Foundation Arcus Foundation National Geographic Society MacArthur Foundation Packard Foundation Moore Foundation Pew Charitable Trusts
Armed groups
Ansar al-Sunna ASWJ Cabo Delgado insurgency ADF Allied Democratic Forces M23 JNIM Jama'at Nasr al-Islam wal-Muslimin ISWAP Boko Haram al-Shabaab
Macro indicators
USD-MZN USD-ZMW Mozambique Eurobond spread Zambia Eurobond spread tourism arrivals IMF Mozambique IMF Zambia
Sector figures
Duko Hopman Werner Myburgh Greg Carr Peter Fearnhead

Exclusions

The following categories are deliberately filtered out:

A source blocklist additionally hard-excludes specific outlets and authors judged unreliable for evidentiary purposes, so their material is never treated as a signal.

Satellite watch

Fire

The trigger, in plain terms: a park is flagged when it burns hotter than its own normal range for the season and stays elevated for several days running. Because the bar is each park's own history rather than a fixed number, parks that burn every year are not flagged for burning - only for breaking their own pattern.

The rule, with numbers. The day needs at least 3 fires to count. Then it flags if the day's fire count or heat is in the park's top 10% of its last ~60 days, or 2 standard deviations above normal; high at the top 2% or 3 SD. One day is not a story - the flag has to persist several days. Under 10 days of history reads as provisional.

The fire watch surfaces anomalous fire activity at keystone protected areas, drawn from NASA satellite detections. It is a screening signal: it points to a protected area that may warrant a closer look, not a confirmation of cause or damage.

Where the data comes from

Detections come from NASA FIRMS (Fire Information for Resource Management System), the near-real-time active-fire product derived from the VIIRS and MODIS satellite instruments. The feed ingests these detections daily.

How an event is built

  1. Ingest the day's active-fire detections for every keystone with a known boundary.
  2. Aggregate and cluster detections to each protected area.
  3. Score the day against that park's own recent-history baseline (a rolling window of roughly the past 60 days), not against an absolute number.
  4. Track persistence: how many consecutive days a park stays elevated, and whether the streak is still running or has recently ended.
  5. Select the events worth surfacing and classify each against the press record.

What "anomalous" means

A park is flagged when its fire activity is high relative to its own normal range for the season, not when it simply has fire. Many African savanna parks burn every year, and a fixed threshold would flag them constantly. Scoring against each park's own baseline means a normally fire-prone park is only flagged when it departs from its own pattern.

A single elevated day is not a story. What makes an event newsworthy is persistence - a multi-day streak above the park's norm. Parks with no fire history on record carry an explicit no-history state rather than being scored as if quiet.

This-time-of-year context

The daily flag above measures each park against its own recent weeks. That is the right screen for "is something happening now", but it cannot say whether the fire is normal for the time of year. A separate layer answers that: roughly 24 years of MODIS fire history (2003 on) folded into a week-of-year climatology for each park, a typical range for every week of the calendar built from all the prior years. The current year is read against it and given a plain verdict, normal, above, or unusual for the season. It appears as the Fire seasonality chart on each park page and the vs the seasonal normal line in the fire alert. Because the norm is learned per park, hemisphere and biome are automatic: a southern savanna's August peak, a northern park's January one, and a rainforest's year-round near-zero all fall out with no hand-coded rule. An absolute floor keeps a normally near-quiet park from flagging on a few stray pixels. This layer is context only: like every satellite signal it never moves a PACE score, and it is a coarser 1km MODIS lens shown alongside, not in place of, the recent-history flag above.

The press tags

Every fire event is checked against the C-INTEL press corpus and carries one of three honest labels: press corroborated (a matching report exists, with the lead or lag in days recorded), scoop (inside the in-scope footprint but no matching press found), and no press baseline (outside the in-scope footprint, so there is no press to compare against - stated plainly because it is not a claim the event went unreported, and not a scoop).

Dates

A fire event is stamped with the day it was last flagged by the satellite (shown as flagged [date]). This is a detection date, not a publication time.

Coverage and limits

Provenance

The pipeline runs daily. Every event carries the version of the scoring logic that produced it, the time it was scored, and a short statement of the basis for the score.

Satellite watch

Forest

The trigger, in plain terms: a park is flagged when it loses canopy faster than its own recent pattern. The comparison is always against the park's own baseline, so a normally stable forest stands out the moment its loss accelerates.

The rule, with numbers. The day's loss alerts must clear 50 pixels (ignores stray noise). Then it flags if the count is in the park's top 10% of recent days, or 2 standard deviations above normal; high at the top 2% or 3 SD.

The forest watch tracks forest-cover loss at keystone protected areas - clearing, conversion, and degradation visible from space. Like the fire watch, it is a screening signal: it points to a protected area whose canopy is changing faster than its own recent pattern, not a confirmation of cause.

Status

Live. The daily job has accrued one baseline reading per park per day since the seed on 20 May 2026, and anomaly scoring now surfaces flagged parks into the unified feed as standalone satellite items. A flagged park carries a Satellite signal badge, or Provisional while its baseline window is still short.

Where the data comes from

The live signal is DIST-ALERT, the near-real-time land-disturbance alert layer derived from harmonised Sentinel-2 and Landsat optical imagery. It sits on the established global products - JRC Tropical Moist Forest and the Hansen Global Forest Change series - which provide the longer-run context named in the press taxonomy under landscape-scale forest-cover change.

Roadmap

The baseline, anomaly scoring, and feed band are live. The pipeline scores each park's loss signal against its own accrued baseline, tracks multi-day persistence rather than a fixed threshold (mirroring the fire watch), and renders flagged parks into the feed as standalone satellite items. Forest carries no press pairing - every item is a pure satellite signal, labelled as such rather than posed as a press-matched event.

  1. Radar complement (later build). Add a cloud-penetrating radar alerting layer to close the optical blind spot described below.
Cloud and canopy caveat. Optical forest sensing under-sees loss beneath persistent cloud and dense canopy. Wet cloud-forest parks such as Odzala and Salonga currently read near zero loss, which is a sensor limit, not a finding. A RADD-style radar complement - radar sees through cloud - is the planned fix, and is why a quiet optical reading over a cloud-forest park is never reported as proof of no loss.
Satellite watch

Vegetation

The trigger, in plain terms: a park is flagged when its greenness falls below what is normal for that park at that time of year. Scoring against each park's own seasonal curve means ordinary dry-season browning is ignored while a real drought or dieback still surfaces.

The rule, with numbers. Greenness must drop on two tests at once: at least 2x the park's usual seasonal wobble for this 16-day window of the year, and at least 0.05 NDVI in real terms. High at 3.5x. Judged against the same window in past years, so seasonal browning does not trip it.
What "wobble" means. In plain terms, wobble is how much a park's reading naturally jitters from one period to the next even when nothing is wrong - the normal scatter around its seasonal norm. The bar is set as a multiple of that scatter (2x the usual wobble to flag, 3.5x for a high flag), so a naturally noisy park needs a larger move to trip than a steady one. In quant terms it is the median absolute deviation (MAD) of the park's values in the matching seasonal bucket - the median of the absolute gaps from the median - chosen over standard deviation because it is robust to the odd outlier reading. The same idea drives the water watch, where the scatter is measured month-to-month rather than across the 16-day vegetation window.

The vegetation watch is intended to track greenness and vegetation-condition anomalies - the drought stress, browning, and seasonal shifts that bear on forage, water, and habitat at keystone protected areas. It is designed as a screening signal of the same family as fire and forest: a departure from a park's own seasonal norm, not an absolute reading.

Status

Live. The watch scores each park against its own seasonal greenness baseline and surfaces flagged parks into the unified feed as standalone satellite items. A flagged park carries a Satellite signal badge, or Provisional while its baseline is still shallow.

Where the data comes from

The live signal is MODIS NDVI - the Normalised Difference Vegetation Index, a satellite-derived measure of how green and healthy vegetation appears, with a long, stable record well suited to seasonal baselining. It is calculated from how plants reflect light: healthy, actively growing plants absorb red light for photosynthesis and reflect a lot of near-infrared, while sparse, stressed, dead, or absent vegetation reflects less near-infrared and so scores lower.

NDVI = (NIR - Red) / (NIR + Red)

where NIR is the near-infrared light reflected by the surface and Red is the red light reflected. The index runs from -1 to +1. Typical ranges: around 0.6 to 0.9 for dense, healthy vegetation; around 0.2 to 0.5 for grassland, shrubs, and sparse cover; and around 0 or below for bare soil, water, and built-up surfaces. An anomaly is a drop in NDVI against the park's own normal range for the time of year, so ordinary seasonal green-up and senescence are normalised out and a genuine browning or drought-driven decline still surfaces.

Roadmap

Source selection, seasonal baseline, anomaly scoring, and the feed band are live. The pipeline flags parks departing from their own seasonal range, tracks persistence, and renders them into the feed as standalone satellite items. As with forest, vegetation carries no press pairing - every item is a pure satellite signal, labelled as such.

  1. Higher-resolution complement (later build). Add a Sentinel-2 vegetation-index layer to sharpen the coarse MODIS footprint over smaller parks.
Honest framing. Vegetation greenness is a coarse proxy that moves with rainfall and season as much as with disturbance, so the bar for surfacing an item is deliberately high. The watch scores against each park's seasonal pattern rather than an absolute, and an item only sheds its provisional badge once the baseline has the depth to separate a real anomaly from ordinary seasonal change.
Drought cross-check (context only). A flagged vegetation or water drop is annotated with a drought read that fuses two feeds: rainfall (CHIRPS) as the drought-INPUT, meaning did the rain arrive, and root-zone soil moisture (NASA SMAP L4, roughly 9 to 11km) as the drought-STATE, meaning is the ground actually dry. Because SMAP assimilates precipitation, soil moisture is not independent of rainfall, so the two are fused into one verdict rather than cast as two separate votes: soil moisture is rainfall's drought-STATE companion, not a second opinion. Its one distinct catch is the lagged case, where rain has returned but the soil is still dry, so a drop that rainfall totals alone would call weather-neutral still carries a drought component. This layer only explains, or declines to explain, an existing flag; it is never its own alert and never a scoring or PACE input. The soil feed is now live, so the cross-check fuses rainfall and soil moisture, including that lagged-drought catch; where a soil reading is missing or a pull fails it falls back to rainfall alone, exactly as before.
Satellite watch

Water

The trigger, in plain terms: a park is flagged when its open water shrinks below the normal level for that calendar month. Measuring each month against its own history means the yearly flood-and-dry cycle is expected, and only a genuine shortfall is surfaced.

The rule, with numbers. First, at least 20% of the park must be cloud-free or the reading is dropped. Then open water must shrink on two tests at once: at least 2x the usual month-to-month wobble and at least 3 percentage points of area. High at 3.5x. Judged against the same calendar month across the three-year history.

The water watch tracks surface-water extent at keystone protected areas - the shrinking and filling of rivers, floodplains, pans, and reservoirs that drive wildlife movement and dry-season survival. As with the other satellite signals, it is designed to flag a departure from a park's own pattern, not a raw water level.

Status

Live. The watch scores each park against its own month-of-year surface-water baseline, built from a three-year backfill, and surfaces flagged parks into the unified feed as standalone satellite items. A flagged park carries a Satellite signal badge, or Provisional while that calendar month still holds a thin sample.

Where the data comes from

The live signal is Sentinel-2 surface reflectance. Open water is measured as the share of the park footprint flagged as water by the normalised difference water index, after a scene-classification cloud and shadow mask drops scenes too obscured to trust. An anomaly is a drop in that open-water fraction against the same calendar month across the backfill, so the ordinary wet-dry seasonal swing is normalised out and a drought-driven drying still surfaces.

Roadmap

The baseline, anomaly scoring, and feed band are live. The pipeline scores each park's open-water fraction against its own month-of-year median, surfaces departures below that seasonal normal, and renders flagged parks into the feed as standalone satellite items. Water carries no press pairing - every item is a pure satellite signal, labelled as such.

  1. Bidirectional anomalies (later build). The current watch surfaces unusual drying only. Unusual flooding and expansion is a real signal but seasonal flood pulses are normal, so a bidirectional version waits until the drops distribution is trusted.
Honest framing. Surface-water extent swings hugely between wet and dry seasons by design, so the watch scores against each park's own calendar-month pattern rather than an absolute. A scene too cloud-masked to trust is recorded but never flagged, and an item keeps its provisional badge until its month bucket is deep enough to separate a real anomaly from the ordinary annual cycle.
Drought cross-check (context only). A flagged water drop carries the same fused rainfall (CHIRPS) plus root-zone soil-moisture (NASA SMAP L4) drought read described under Vegetation: one verdict, not two votes, because soil moisture is not independent of rainfall. It only explains or declines to explain the flag and is never a scoring or PACE input. The soil feed is now live, so the read fuses both, falling back to rainfall alone only where a soil reading is missing.
Satellite watch · beta

Night-time lights

The trigger, in plain terms: a park is flagged when new light appears at night, brighter than its own normal for that calendar month. Stable existing lights - a lodge, a gate post, a nearby town's glow - are part of the baseline and are expected; only a genuine rise above that pattern is surfaced. New light where there was none is a proxy for human encroachment: settlement, camps, mining, or road lighting.

The rule, with numbers. The month's radiance must rise on two tests at once: at least 2x the park's usual month-to-month wobble (the MAD, as in the vegetation and water watches) and at least 0.3 nW/cm²/sr in absolute terms, so a dark park's statistical noise cannot trip the flag. High at 3.5x. Judged against the same calendar month in prior years, falling back to a recent window where history is thin - and a thin history reads as provisional.

Status

Live, in beta. The watch scores the full keystone cohort monthly and surfaces flagged parks into the unified feed as standalone satellite items. Because the source is a monthly composite that matures around five weeks after the month ends, each item states its composite month (the activity) alongside the date it surfaced (the detection) - a July item about April light says so.

Where the data comes from

The live signal is the NOAA VIIRS Day/Night Band monthly composite - calibrated low-light imaging designed to see faint artificial light at night. The watch reads the park's average radiance from each new composite and compares it against the park's own month-of-year baseline, so moonlight-corrected seasonal patterns and stable existing lighting are normalised out.

Honest framing. A rise in night light is not proof of new infrastructure. Fire glow is the classic false positive, so every flagged month is cross-checked against the fire watch: if the fire feed flagged burn activity at the same park in the same month, the item carries an explicit fire caution rather than being passed off as clean. The signal also cannot say what the new light is - a ranger post and an illegal mining camp look the same from orbit. It flags that something new is shining and worth examining, nothing more.