Governed AI for Nepali institutions,
built for the powerhouse, the border metering point, the bank and the municipal office

Cross-border electricity trade: metering, scheduling and settlement between two systems

Nepal's hydropower is increasingly exported to the Indian grid, moving through cross-border transmission at Dhalkebar–Muzaffarpur and other interconnections, sold under bilateral arrangements and into the Indian day-ahead market. Access is not general: approvals granted on the Indian side specify which plants may sell, to whom and on what terms, and a long-term understanding between the two governments frames the volumes contemplated over the coming years. Power has also begun to reach Bangladesh across Indian territory, which adds a third party to the same set of records. Every unit that crosses is metered, scheduled, settled and reconciled between two national systems with different regulators, different market rules and different clocks.

Payment follows the record. Interchange metering at the border, day-ahead and real-time schedules, deviation and imbalance accounting, transmission charges, energy accounts and the invoices reconciled against them are commercial instruments, and a discrepancy in any of them is a commercial dispute rather than an engineering footnote. Where AI assists — forecasting inflow and generation, reconciling metering and scheduling series, detecting anomalies in an interchange trace, preparing an energy account or a regulatory submission — the platform validates the input before the model runs, validates what comes back against the utility's own rules, writes one immutable ledger row for every call with actor, action, inputs, outputs, model version and verdict, and escalates to a named person wherever the output would change a settled quantity. Role-scoped access lets the generator, the system operator, the regulator, the trading counterparty and independent auditors each see exactly what their mandate permits and no more.

Three tiers of government: which layer holds authority is an access-control question

Since the constitution of 2015 Nepal has operated federal, provincial and local governments with distinct responsibilities. Seven provinces and more than seven hundred and fifty rural municipalities and municipalities hold real functions — registration, permitting, local infrastructure, primary health and education, revenue of their own — alongside the federal ministries. The same citizen, business or project therefore generates records at all three levels, and the allocation of authority over a specific decision is still being worked out in practice in several areas rather than settled once and for all.

That makes it an access-control problem before it is an administrative one. A municipal officer, a provincial ministry, a federal department and an auditor should not see the same fields, and a record created at one tier and relied on at another has to carry its provenance with it. Wherever AI assists in classifying an application, drafting a determination, matching a registration or reconciling a transfer, the platform enforces role-scoped access at the point of capture, validates the output against the rules of the tier that actually holds the authority, escalates to a person wherever a determination affects an individual's entitlement, and writes an audit row for every call. A decision that cannot show which layer of government made it, on what basis and with what evidence, is difficult to defend to the citizen it affected or to the Auditor General.

Remittances, correspondent banking and anti-money-laundering records

Remittances from Nepali workers abroad — in the Gulf states, Malaysia, Korea, India and beyond — represent among the highest shares of GDP of any country in the world. That is not a statistic about households alone; it is the structure of the external sector. The corridor runs on licensed remittance companies, bank channels and correspondent relationships with institutions that carry their own supervisory obligations, and it connects to a foreign employment system of labour approvals, recruitment agency licensing and worker records administered by the federal government.

A correspondent bank that loses confidence in the evidence behind a corridor does not argue about it; it withdraws, and a very large flow has to find another route. Anti-money-laundering and sanctions screening, customer due diligence, transaction monitoring, suspicious transaction reporting to the financial information unit and supervisory returns to Nepal Rastra Bank therefore have to produce evidence that reads the same to a domestic supervisor and to a foreign correspondent. Screening is enforced rather than advisory: a hit blocks the call, an override escalates to a named person, and the override decision is itself written to the ledger with its reason. Where AI assists in monitoring, risk scoring or narrative drafting, the input is validated before the model runs, the output is validated against the institution's own rules, and every call leaves a row. The obligation stays with the institution; better evidence makes it tractable.

Digital payments, cooperatives and microfinance under one supervisor

Nepal Rastra Bank supervises commercial banks, development banks, finance companies and microfinance institutions, and licenses the payment service providers and operators behind a digital payments sector that has grown quickly — wallets, interbank clearing and retail switching, and interoperable QR acceptance now ordinary in shops in Kathmandu and well beyond it. Alongside the licensed banking system sits a very large cooperative layer, with savings and credit cooperatives registered and supervised across federal, provincial and local levels, and a microfinance sector serving borrowers for whom a lending decision is consequential.

Difficulties in parts of the savings and credit cooperative sector, and concerns about borrower over-indebtedness in microfinance, have made the quality of member and borrower records a matter of public attention rather than an internal one. Wherever AI touches credit scoring, collections prioritisation, fraud detection, member deduplication or transaction monitoring, the governed chokepoint validates the input before the model runs, validates the output against the institution's own lending and conduct rules, escalates to a named person wherever the answer would deny credit, restrict an account or trigger recovery action, and writes an immutable row for every call. A model that cannot show why it declined a member is not a model an institution can defend to that member, to its supervisor or to a court.

Tourism and mountaineering: permits, licensing, certification and incident records

Tourism is a major employer and foreign exchange earner, and the records it runs on carry real safety weight. Expedition and trekking permits and royalties, protected area entry, trekker information records, trekking and expedition agency licensing, guide and instructor certification, liaison arrangements and insurance cover are administered between the Department of Tourism, the Nepal Tourism Board, protected area authorities, local governments and the mountaineering and trekking associations. Rules on independent trekking and guide requirements have changed in recent years and continue to be adjusted, so the current position is better checked than assumed.

When something goes wrong at altitude, those records become the basis for a rescue, an insurance claim and, sometimes, an investigation. A helicopter evacuation, a medical repatriation and the claim that follows rest on who was permitted to be where, with which operator, under whose guiding, with what cover — and the integrity of that chain has itself been the subject of scrutiny. Where AI assists in verifying a permit, matching an itinerary to a manifest, triaging a claim or assessing a supplier, validation executes before the model call and on what comes back, an audit row is written for every call, and escalation to a person is required wherever the output would authorise a rescue, approve or refuse a claim, or affect an operator's licence. These are records people's safety and livelihoods rest on, and the protections around them execute in code rather than depending on a policy being followed.

Hydropower development: licensing, environmental flow and lender safeguards

Nepal's generation build-out runs through storage, run-of-river and peaking-run-of-river projects on the Koshi, Gandaki, Karnali and their tributaries, developed by the state utility, by domestic and foreign private developers and by public share offerings that have given a broad domestic shareholder base an interest in the numbers. Large projects pass through generation licensing, environmental assessment under the environment protection legislation, land acquisition and resettlement, local benefit-sharing arrangements and, where international financing is involved, lender safeguard frameworks with their own reporting cycles.

Those obligations continue for the life of the asset. Environmental flow releases, hydrological and sediment monitoring, resettlement and livelihood restoration records, grievance logs, local benefit and shareholding records and periodic safeguard reports are read by a regulator, a lender, an auditor and an affected community, each with a different interest in the same figures. Where AI assists in hydrological forecasting, sediment or outage analysis, safeguard report drafting or grievance classification, every call passes through one governed chokepoint that validates the input, validates the output against the project's own commitments, records the model version that produced the answer and writes an audit row — so a contested figure can be re-derived exactly as it stood rather than argued about from memory, and a compliance claim made to a lender can be shown rather than asserted.

Reconstruction records, personal data and Nepali-language governance

The programme that followed the 2015 earthquake produced an enormous body of records: damage and building assessments, beneficiary enrolment, grant tranches paid against inspected construction stages, retrofit designs and code-compliance determinations for houses, schools and health posts. The dedicated reconstruction authority completed its mandate and its functions passed to regular ministries and to local governments, but the records themselves remain live. They are still consulted when a property is sold, a claim is made, a structure is extended or a later assessment has to be reconciled with an earlier one, and in a seismically active country a building record is a safety record.

That same discipline applies to personal data generally. The Individual Privacy Act of 2018 and its rules govern personal information, national identity registration and digitised public services continue to expand, and further data protection legislation has been under consideration rather than enacted — so the obligation today sits squarely with the organization holding the data. The platform enforces minimization and role-scoped access at the point of capture, content-logging modes that store a verifiable fingerprint instead of the content itself, certified deletion with a tamper-evident certificate where a dataset must genuinely be gone, and an immutable record of every access. Governance in Nepali is part of this rather than a localization detail: policy definitions, refusal messages, escalation notices and audit records have to be readable in Nepali by the people accountable for them, and in provinces that adopt an additional official language, in that language too.

On-premise deployment inside Nepali facilities

Enforcement, inference and audit logging run inside the institution's own environment — a data centre in Kathmandu, a powerhouse or load dispatch centre, a bank's operations floor, a hospital, a provincial or municipal office. Data does not leave the perimeter in order to be processed, which is the only version of data residency that actually holds.

Air-gapped operation as a supported configuration

For supervisory returns, customer and remittance files, national identity data, settlement records or safety investigation material, deploy with no outbound path at all. The platform does not phone home for telemetry, licence checks or model routing, so an air gap is a supported configuration rather than a degraded one.

Offline-capable enforcement across mountain terrain

Governance does not pause when connectivity does. At a powerhouse in a river gorge, a rural municipality office, a border customs point, a health post in the hills or an assessment carried out on a trail, validation still executes and the ledger still writes, and records created while disconnected reconcile cleanly when the link returns.

Jurisdictional residency for cross-border energy and financial operations

Cross-border power trade, correspondent banking and lender safeguard reporting each touch more than one legal regime. Deploy so that data governed by one country's rules stays where those rules require, with jurisdiction-specific policy enforced at the same chokepoint rather than in separate systems that drift apart.