Every map point now links to the people, companies, agreements, claims and research papers behind it, and Ask MGC answers questions with cited sources. This page runs in the order of the walkthrough: how it fits together, the live demo, where it stands, and what each person picks up.
Three repositories, one direction of flow. The graph is built once and served; the website only reads it.
Pulls MFA press releases, research papers and the platform's own map datasets, extracts entities, relations and claims, and checks each claim against its source sentence.
Adds /kg/* endpoints: resolve a map point, fetch an entity's relationships, claims and events, search, and Ask.
The relationships sidebar on the maps, the network view, and the Ask MGC search box.
The join is deterministic: each map feature already carries its dataset row id (port:34, plant:<hash>, investment:<n>). A map_link table maps that id to its graph node, so no fuzzy name matching happens on click.
The real MGC website on port 3001, with the investment and energy maps loading from snapshots in this folder and the graph served from a local service on port 18010 that reads the database in this folder. To run it on your own laptop, follow Run the demo (about 10 minutes, from a clone of the frontend repo plus this folder).
Click Pakistan, then the hub icon at the top right. The sidebar shows who invests, which projects, the state visits and the impacts, each with its sources.
Click any plant point. The panel resolves that exact plant to its graph node and lists its operator, financiers and related projects.
Try what is the research for gwadar port in pakistan. Answers lead with papers and cite the sentence each fact came from.
The same data the sidebar renders, straight from the graph service.
| Task | Owner | Unblocks |
|---|---|---|
Load the graph into the kg schema of mgc_hub_db, and choose Option A (standalone text ids) or Option B (keyed to entity_registry)Schema, loader notes and the data dump are in the backend and database guide | Data / DB owner | Real data on the live site |
Deploy the /kg endpoints (PR #43), then port /kg/ask and the noise filter from the local service | API owner | Live sidebar and live Ask MGC |
| Wire each remaining map's click to the sidebar, and place Ask MGC in the navTwo copy-ready examples: the investment map (country) and the energy map (per point). See the frontend wiring guide | Maps engineer | Graph on every map |
| Install the daily extraction timer on the mgc-hub serverSteps in the server runbook | Server owner | Collection without the laptop |
Add surbhikapoor19 to the MGC Vercel team | Vercel admin | PR preview builds |
| Provide a Directus token for Research Briefs | CMS owner | Briefs in the graph |
Everything below is in this folder. Open index.html and every page links locally; only the GitHub links go out.
| What | Open | For |
|---|---|---|
| Run the demo on your laptopClone, apply the demo patch, start two services; uses the data in this folder | run-the-demo.html | Everyone |
| Engineering handoffArchitecture, data model, cron, and how the site integrates | engineering-handoff.html | Everyone |
| Frontend wiring guideWhere to call the graph, and how to wire map clicks and search | frontend-integration.html | Maps engineer |
| Backend and database guideSchema, loading the graph, the endpoints, Option A vs B | integration-guide.html | Data / API owner |
| Daily extraction server runbookInstalling the systemd timer on mgc-hub | server-cron-runbook.html | Server owner |
| Graph data dictionaryWhat each node, edge and claim type means, and where it came from | data-dictionary.html | Everyone |
| DataThe demo graph database (139 MB SQLite), the investment and energy map snapshots, Postgres and SQLite schemas, map links, and the full Postgres dump (21 MB) | mgc_kg.demo.sqlite viz_cache/investments.json viz_cache/energy-projects.json postgres_kg_schema.sql sqlite_schema.sql map_link.sql mgc_kg_data.sql.gzWhat each file is | Data owner |
mgc-api pull requestbranch feat/kg-endpoints, merge first | mgc-api #43 | API owner |
mgc-frontend pull requestbranch feat/kg-relationships-panel into staging, merge second | mgc-frontend #175 | Maps engineer |
research-kg repositoryPipeline, notebook, and this folder under handoff/ | research-kg | Data owner |
All three repositories are private to the mapping-global-china GitHub org, so each person needs org access. The demo buttons in section 02 work once the demo is running locally (see Run the demo).