Explore
Flagship studies, sector briefs, and recurring reports, by topic.
Long-form data narratives that walk through an argument.
Recurring advisor series, from weekly reads to annual reviews.
The daily policy prescription, generated each morning.
Seven sector deep-dives: banking, trade, energy, agriculture, and more.
Ask the corpus: answers grounded in published work, with citations.
Grounding verified
Brahmaputra-Jamuna shift scenario over 50y horizon
The curated risk here is a major delta avulsion: a Brahmaputra-Jamuna shift scenario over a 50-year horizon. An avulsion is not gradual bank erosion that engineering can chase year by year. It is the abrupt relocation of a major river into a new course, abandoning the channel that today's embankments, towns, ports, irrigation intakes, and bridges were all built around. The Brahmaputra-Jamuna has switched its main course before in the historical record of this delta, so the scenario is geologically credible rather than speculative.
What makes this hard to govern is that the probability in any single year is low, but the consequence is structural and close to irreversible. A think tank cannot put a date on the next avulsion, and the context provides no such figure (current_state is null, and the only hard fact is the lead body). That uncertainty is precisely why it is neglected: every annual budget cycle rationally defers it. The cost of acting early is small (planning, monitoring, land reservation), while the cost of acting late is a stranded national investment in the wrong river corridor. The lead body is the Ministry of Environment, Forest and Climate Change (MoEFCC), with the Bangladesh Meteorological Department, the Department of Environment, and the Ministry of Disaster Management and Relief supporting.
Charter the scenario cell first (Action 1): it is cheap, needs no new river works, and produces the maps every later step depends on. In parallel, begin the monitoring build (Action 2), because trigger thresholds take time to calibrate. The scenario maps then unlock corridor reservation (Action 3) and the clearance rule (Action 4), since both require an agreed map of where the river might go. The contingency protocol (Action 5) follows once thresholds and corridors are defined.
The binding constraint is political attention: a 50-year, low-annual-probability hazard competes badly against visible near-term needs, so the cell risks being chartered and then starved. Corridor reservation is the most contested step, because restricting development on land the river has not yet taken imposes real local costs today against an uncertain future benefit. Fiscally, the early actions (planning, monitoring, reservation) are modest; the danger is that they get deferred until an avulsion is underway, when only emergency spending remains.
A Brahmaputra-Jamuna avulsion is a low-probability, civilization-scale risk where acting early is cheap and acting late is ruinous. MoEFCC should buy the option now: a scenario cell, a monitoring trigger, and a reserved corridor, so the country, not the river, decides where its next 50 years of infrastructure goes.
The figures and responsible bodies cited in this prescription are drawn from the platform's own data and the GovTwin registry listed below.
Drafted by an Opus writer grounded in the facts above. Where the prescription cites a figure, it is drawn from those facts. The diagnosis derives from the BDPolicyLab crisis taxonomy; the responsible body and budget from the GovTwin registry. Recommended actions are the think tank's policy judgment.