LCCAP Climate Planning Workspace

What this project proves

• Four technology layers across .NET 8, PostgreSQL, Next.js and TypeScript, and Python with FastAPI
• Two completed product phases covering six core planning functions
• Eight Phase 2 capabilities spanning evidence, reviews, funding readiness, monitoring, dashboards, GeoJSON, and notifications
• Seven enterprise controls and a bounded four-stage facility exposure workflow

The problem

Climate-action planning is often coordinated through disconnected Word documents, spreadsheets, PDFs, shared folders, email threads, and manual review notes.

Teams need a structured internal workspace without misrepresenting it as an official submission, approval, funding, reporting, or risk-assessment platform.

My approach

Deliver six core functions covering plan sections, evidence, climate actions, monitoring, audit history, and export-ready draft packages.

Add eight Phase 2 capabilities spanning evidence indexing, review comments, funding readiness, monitoring history, dashboards, GeoJSON map layers, and notifications.

Implement a four-stage facility exposure workflow covering hazard registration, background processing, point-in-polygon evaluation, and persisted results.

Architecture and engineering choices

• .NET 8 Clean Architecture API and domain layers
• Entity Framework Core with PostgreSQL
• Next.js and TypeScript operator workspace
• Feature-flagged FastAPI exposure-computation service
• Seven enterprise controls including RBAC, tenant isolation, audit snapshots, concurrency, pagination, archives, and refresh-token rotation

Truthful scope and boundaries

• Independent portfolio product; not an official Philippine government platform.
• Not an official submission, approval, national reporting, funding, certification, or risk-assessment system.
• The source repository remains private and public demonstrations use synthetic data.