TerraMatch NexusTerraMatchNexus

TerraMatch Nexus imagines the screen a relief coordinator would need: who is most at risk, which cities can take them, and what happens to both when a cyclone hits. Eight tabs, one engine, no framework.

Built at

On my own time

First commit

May 2026

File

08 of 18 project pages

1. 01

   A priority-queue matcher

   Risk is a weighted score — urgency × 0.5, health × 0.2, age × 0.2, family size × 0.1. People are queued highest risk first, every city is scored for each person, and the best available city is assigned greedily; then corridor IDs and allocations are generated.

2. 02

   A simulation theatre

   Cyclone, extreme drought, coastal flooding and heatwave scenarios project the affected population, a displacement timeline, recommended corridors and the stress on water, energy and housing.

3. 03

   Plain JavaScript, deployed by CI

   Command, risk engine, simulation, matching, smart cities, alerts, analytics and field ops — vanilla JavaScript modules and canvas visualisations, published to GitHub Pages by a GitHub Actions workflow.

• !Every person and city in it is sample data. It's a simulation of a system, not a system in use.
• !The 'AI' is a scoring and matching engine — rules, not a trained model.

No fake users, no invented numbers. If it's a demo, it says so.

App

JavaScript/HTML/CSS

Visuals

Canvas/SVG gauges

Deploy

GitHub Actions/GitHub Pages

• LiveOpen it ↗
• CodeView the code ↗