mountain-governance-adaptation-utac
GenesisAeon Package 104 — the governance/institutional closing chapter of the P99–P103 series. Deliberately has no UTAC/CREP/AFET bridge — see DISCLAIMER.md.
What this is, and what it deliberately is not
This package documents real, dated institutional facts — treaties, funds, negotiation status — as citable data. It does not simulate governance dynamics (no actor-network models, no allocation-rule solvers, no predicted outcomes). That distinction was a deliberate scope decision: P99–P103's whole methodology works because a stress value or a sedimentation rate can be independently verified against a paper. Political process can't be reduced to that kind of code honestly — so this package sticks to documenting what is real and dated, not modeling how governance "works."
It also deliberately excludes personal and indigenous testimony about non-economic losses (e.g. statements made at COP29 by affected community members) from its data. Encoding grief and lived experience as a Python constant next to a funding figure would be a category error, not a simplification. If you want that testimony, go to its original source — the COP29 proceedings and UNFCCC WIM ExCom documentation — where it is properly attributed and contextualized, not flattened into a citation string.
Two confidence tiers
- Core (
transboundary_governance,loss_and_damage, most ofnational_adaptation): real, dated institutional facts independently re-verified 2026-08-14/15. - Documented (two NDC/NAP percentages in
national_adaptation): carried over from the source dialogue without the same independent re-verification this session — flagged viaDOCUMENTED_TIER_WARNING.
What's real here
- Indus Waters Treaty (1960) — suspended by India on 2025-04-23, still suspended as of mid-2026. A 65-year, war-surviving treaty, suspended for non-hydrological reasons.
- Colorado River Compact (1922) — 16.5 MAF/yr nominal allocation against a real natural flow that's declined ~19% from the 20th-century average, with Upper Basin, Lower Basin and (for the first time) Tribal Nations in active 2025 renegotiation.
- Mekong Agreement (1995) — Cambodia/Laos/Thailand/Vietnam bound by real obligations; China and Myanmar (the two upper-basin states) are only dialogue partners, not bound — a real structural asymmetry.
- The mountain-specific adaptation finance gap, corrected from the source dialogue's generalized global figure: mountainous developing countries need an estimated ~$187bn/yr but received only ~$13.8bn in 2022 — about 7% coverage.
- The Fund for responding to Loss and Damage (FRLD) — real, operational since COP29 (2025), hosted by the World Bank, Philippines as host country, $822.06M pledged by 27 partners as of 2026-03-15 (24 of whom have actually signed contribution agreements).
- UNFCCC WIM ExCom's second Non-Economic Losses Plan of Action (Oct 2025–Oct 2027) and its real institutional NEL categories (loss of life, health, mobility, territory, cultural heritage, local/ indigenous knowledge) — corroborated by Islar et al. (2025)'s socio-glaciology framework, already cited in this ecosystem's P103.
Quickstart
pip install mountain-governance-adaptation-utac
from mountain_governance_adaptation_utac import (
INDUS_WATERS_TREATY,
colorado_river_current_deficit_maf,
mountain_adaptation_finance_gap_usd_billions_per_yr,
FRLD_CURRENT_STATUS,
nel_categories,
TESTIMONY_EXCLUSION_NOTE,
)
print(INDUS_WATERS_TREATY.status_note)
print(colorado_river_current_deficit_maf()) # ~5.7 MAF/yr
print(mountain_adaptation_finance_gap_usd_billions_per_yr()) # ~173.2
print(FRLD_CURRENT_STATUS.pledged_usd_millions) # 822.06
print(nel_categories())
print(TESTIMONY_EXCLUSION_NOTE)
Development
pip install -e ".[dev]"
pre-commit install
ruff check src tests
mypy src
pytest
Citation
See CITATION.cff and .zenodo.json.
Metadata
Release files for mountain-governance-adaptation-utac 1.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| mountain_governance_adaptation_utac-1.0.0.tar.gz | 16.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mountain_governance_adaptation_utac-1.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 30.6 kB
Release files / mountain_governance_adaptation_utac-1.0.0.tar.gz
| Download URL | mountain_governance_adaptation_utac-1.0.0.tar.gz |
|---|---|
| Size | 16.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c93efbe2c087779dcf7fac5eb361c3275469acad23532113a558421e4d8712df
|
|
BLAKE2b-256 checksum How to use checksums |
07ce16a2e66018219acad7279da54fb1afcc755a687d9f1488c0ba8979fa27a7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Release files / mountain_governance_adaptation_utac-1.0.0-py3-none-any.whl
| Download URL | mountain_governance_adaptation_utac-1.0.0-py3-none-any.whl |
|---|---|
| Size | 14.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
bba289e450c888883b68c7d5e4cadee7e61fc73dc83d7a16757c745d779c2881
|
|
BLAKE2b-256 checksum How to use checksums |
7271fbe1332df3e266630e63e1d092531be58f61f521487836ffdcbf82dbd7d4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Security for mountain-governance-adaptation-utac 1.0.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.