Project Governance & Digital Asset Control Platform
Dedicated Data Infrastructure for the 65 MW Myagdi Khola Hydropower Project
1. Executive Summary
The 65 MW Myagdi Khola Hydropower Project needs structured disclosure, procurement, governance, and operational oversight.
I have built a working platform that brings these together in a project portal plus a controlled admin system: structured publishing, maker-checker-approver controls, procurement workflows, document integrity checks, bilingual disclosures, risk tracking, and auditable records. It runs as a single Cloudflare Worker with low overhead.
This proposal defines a proven digital architecture framework. Deployment scope, timeline, and operational constraints are finalized during discovery to align precisely with Hydro Village Limited's corporate requirements.
Prototype and Deployment Scope
What you see here is a working prototype from a comparable hydropower context. A Hydro Village Limited deployment would be configured around its project structure, roles, procedures, and approved disclosures.
Proposed Next Step
A short walkthrough to check fit against project requirements. Scope, timeline, support, and commercial terms follow only if there is fit. The concept covers:
- Project disclosure: Public technical repository with approval before publication.
- Procurement: Browser-encrypted bidding with client-side AES-256-GCM.
- Records: Maker-checker-approver transitions with verifiable WORM audit history. See Technical Appendix for the state machine and enforcement.
2. Why a Dedicated Project Platform
When disclosures, procurement files, and governance records sit across websites, email, and spreadsheets, control and auditability get harder.
One controlled system fixes that:
- Reporting support: Drawdown histories, environmental records, and disclosure registers for lender, shareholder, and management review.
- Generation tracking: Logs paired with applicable seasonal PPA baselines.
- Procurement records: Sealed bidding with opening-date enforcement and audit trail of receipt, access, and opening.
3. What Is Proposed
One codebase, two layers:
A. Public Portal and Technical Repository
- Salient features: Geomorphic specs, catchment hydrology, structures from Kunaban headworks to Jeltun powerhouse.
- Bilingual archive: Linked English and Nepali notices, EIA updates, and Dhaulagiri Rural Municipality community notices. Next.js SSR.
- Generation dashboard: Logs paired with seasonal PPA baselines.
Public PortalProject Landing & Disclosure Surface
Figure 3.1: Public surface: parameters, telemetry, approved disclosures. Prototype illustration.
B. Protected Administrative Enclave
Restricted workspace behind a deployment-specific secret slug (ADMIN_SECRET_SLUG), not a guessable /admin path.
- Authentication: MFA with server-enforced 15-minute inactivity timeout.
- Separation of duties: Server and database enforced. No self review or self approval.
Admin EnclaveExecutive Management Workspace & Operational Queues
Figure 3.2: Enclave: reviews, risk posture, procurement pipeline. Prototype illustration.
Screenshots are from the working prototype. They show function and layout. Production would use Myagdi Khola data, roles, and bilingual content.
4. Governance and Operational Capabilities
Controlled Procurement Workflows
Sealed Two-Envelope Bidding for civil and hydro-mechanical packages. Financial envelopes are encrypted in the bidder browser with AES-256-GCM. The server stores ciphertext only and holds no decryption keys. Opening-date rules are enforced server side. Result: controlled, verifiable bidding with an audit trail and reduced early-access exposure.
ProcurementSealed Bid Envelopes
Figure 4.1: Sealed envelopes: ciphertext only, no server keys, opening-date locks. Prototype illustration.
5x5 Risk Register
Live 5x5 register. Examples below are illustrative only. Final catalogue is set during discovery:
- Geological (illustrative): Tunnel anomalies, squeezing rock near Dhaulagiri Rural Municipality.
- Logistical (illustrative): Landslides and washouts on the Bagar-Tatopani corridor.
- Interconnect (illustrative): Tailrace and flow allocation with Myagdi Khola-B.
Nightly Cron escalates overdue mitigations. Scoring anchors, control checks, KRI thresholds, and three-person rules: see Technical Appendix.
Risk Engine5x5 Enterprise Risk Posture
Figure 4.2: 5x5 heat map, control health, escalation. Prototype illustration.
Verifiable Audit History (WORM Ledger)
Governance events go into an append-only WORM chain. Each entry links to the prior one with SHA-256 and is checked against an external checkpoint. Alteration is detectable, not claimed impossible.
Audit LedgerCryptographic WORM Execution Ledger
Figure 4.3: Hash-chained ledger with external checkpoints. Prototype illustration.
5. Platform Architecture and Capability Comparison
Architecture Diagram
| Capability area | Common approach | What the platform demonstrates |
|---|---|---|
| Audit records | Email and spreadsheets, hard to verify. | WORM ledger with verifiable history and tamper detection. |
| Project identity | Buried in a corporate site. | Dedicated 65 MW portal with parameters and metrics. |
| Bidding | General channels. | Two-envelope bidding, AES-256-GCM, opening-date enforcement. |
| Risk tracking | Files, no escalation. | 5x5 register, 3-person separation at database layer. |
| Infrastructure | Varies by provider. | Serverless Worker. Illustrative estimate only (about $5 to $15/month low usage). Actual cost depends on traffic, storage, database, backups, logging, domains, and pricing. |
Engineering detail (five-layer enforcement, RLS, trigger-level Maker-Checker, sealed-bid crypto, fail-closed): see Technical Architecture Appendix.
6. Beni Bazaar Advantage
Based in Beni Bazaar. Direct coordination with Myagdi project offices and site teams when needed.
- Local coordination: Direct access to regional offices and stakeholders.
- Direct developer access: Built by me. No intermediaries for technical changes.
- Handover: Source config, migrations, and R2 setup transfer subject to agreed scope and terms.
7. Indicative Implementation
Prototype exists. Configuration follows discovery and scope agreement. Indicative plan:
| Phase | Delivered | Duration |
|---|---|---|
| Discovery | Reporting needs, PPA baselines, roles | 10 days |
| Configuration | 5x5 risk templates, AES bidding gateway | 22 days |
| Validation and cutover | Tamper tests, walkthroughs, DNS cutover prep | 28 days |
8. Closing and Walkthrough Request
I built something real: a working prototype with WORM audit chains, sealed bidder keys, and 5x5 heatmaps. You can see it and test it.
A brief 15-minute walkthrough, online or in Beni, allows us to verify operational fit. A fixed implementation plan, timeline, and commercial terms will be structured immediately following that scoping discussion.
Working prototype (not HVL production):
- Governance portal: https://durbang.aashikbaruwal.com.np/
- More work: https://www.aashikbaruwal.com.np/arc-and-civ
Video DemoWorking Prototype in Action
Video walkthrough: Comparable hydro deployment. Prototype only.
Submitted by
Aashik Baruwal Beni Bazaar, Myagdi
Email: workwithaa.sik@gmail.com