Evidence Review Notes
- Page status
- Registry record
- Updated
- 2026-04-14
Condensed notes on how the wiki's argument was assembled and checked. This page is a methodology aid for readers who want to understand which parts of the hub are source summaries, which parts are synthesis, and where confidence is strongest or weakest.
Evidence Streams
| Stream | Role | Strength | Limitation |
|---|---|---|---|
| Primary-source notes | Official reports, policy documents, and project records | Strongest basis for figures, dates, and institutional claims | Sources sometimes disagree or use different definitions |
| Data tables | Normalized figures and map-ready records | Makes comparisons searchable and reproducible | Some values remain model-derived or registry-dependent |
| Map layers | Spatial context for rivers, projects, transmission, trade, and solar | Reveals geography and bottleneck patterns quickly | Not engineering-grade design drawings |
| Synthesis pages | Cross-cutting interpretation | Connects hydrology, grid, trade, finance, and policy | Should be read with the linked source and data pages |
Thesis Convergence
The evidence converges on: Nepal Fails on Conversion of Hydrological Advantage Into Deliverable Power
Sub-theses also converge:
- Timing > volume (Nepal's Core Hydro Problem Is Timing, Not Annual Volume)
- Storage is the physical fix (Storage Is the Clearest Physical Answer to Seasonal Mismatch)
- Transmission is the immediate blocker (Transmission and Delivery Are Material Immediate Monetization Constraints)
- Domestic use > export worship (Nepal Should Prioritize Domestic-Led Hydro With Export Support)
- India is decisive (India Is the Decisive External Actor in Nepal's Hydro Future)
- Governance is binding (Governance Weakness Wastes Hydro Opportunity Through Delays and Misaligned Incentives)
Source Quality
| Evidence type | Best use | Caveat |
|---|---|---|
| Official annual reports | Installed capacity, generation, trade, project status | Tables can disagree internally by directorate or reporting purpose |
| Policy and planning documents | Strategy, corridor plans, regulatory constraints | Timelines may age quickly |
| Project records and licenses | Registry-backed project inventory | License status is not the same as construction progress |
| Derived map data | Spatial exploration and pattern-finding | Approximate geometries are labelled and should not be treated as survey drawings |
How To Read The Hub
- Start with synthesis pages for the argument.
- Open linked data pages when a number matters.
- Open source pages when provenance matters.
- Treat concise project records as map-backed registry entries unless the page contains fuller narrative analysis.
Related
- Master Thesis — the central public argument
- Unresolved Questions — remaining evidence gaps and data conflicts