Energy Crisis Tracker

Energy Crisis Tracker — Quick Guide

A rapid-response editorial pipeline for the Asia Energy Shock. Forked from the Climate & Capital pipeline on April 13, 2026.

What this is

The Asia Energy Shock Newsfeed — a public log of concrete policy moves (subsidies, emergency packages, grid and fuel decisions). Every entry is scored on a traffic-light signal and asks: who gains, who loses, and what clean alternative exists right now.

Focus region: Southeast Asia, China's role, concrete investments. Sharper positions than legacy media, faster turnaround.

The pipeline

Two stages, each a standalone script:

Script What it does
monitor.py Pulls 14 RSS feeds, classifies relevance and importance, assigns a red/amber/green fossil-lock-in signal, writes a summary. ~28 articles per cycle after source-tiered caps and deduplication.
writer.py For every high-confidence article, drafts a newsfeed entry and a socials post.

Drafts land in monitor.db and surface in the dashboard's editorial queue.

The two output formats

newsfeed → public /newsfeed page Structured: DECISION, COUNTRY, DATE, FOSSIL LOCK-IN ASSESSMENT (RED / AMBER / GREEN), HOUSEHOLD IMPACT, CLEAN ALTERNATIVE.

socials → Bluesky (@pinenook.bsky.social) HEADLINE, BODY, HASHTAGS, plus a link back to the newsfeed.

The red/amber/green signal

Every classified article gets a fossil-lock-in call:

The signal is the editorial spine: it's how each piece takes a position without hedging.

Workflow

The pipeline runs automatically every 12 hours via cron — monitor.py at 10:00 + 22:00 UTC (06:00 + 18:00 NYC), writer.py 15 minutes later. Each cycle wipes the old queue and loads fresh content.

  1. Cron pulls feeds, classifies, and drafts. You don't need to do anything.
  2. You open the dashboard (Review tab) once or twice a day. Articles are sorted by confidence — best stuff at the top.
  3. Approve & Publish — one click does everything: publishes the newsfeed entry, posts to Bluesky with a link back, and generates a video script.
  4. Skip — removes the article. The queue clears each cycle anyway.

Speed matters

Pre-built templates so each event turns around in hours, not days. If a decision doesn't have a clear lock-in call within the first pass, flag it AMBER and move on — don't over-hedge.