Skip to content

My Grid: state rank and the year the buildout arrives - #34

Draft
aurph wants to merge 3 commits into
mainfrom
feat/my-grid-bill
Draft

aurph wants to merge 3 commits into
mainfrom
feat/my-grid-bill

Conversation

@aurph

@aurph aurph commented Sep 15, 2026

Copy link
Copy Markdown
Owner

Bottom line: two real additions to My Grid, both straight from the facility registry, no API key, no computed consumer stats.

Where your state stands. The facilities header places the chosen state among states with tracked capacity: "5.1 GW tracked · #1 of 18 states" for Texas.

When it arrives. The Power Map's opening-year timeline gains an optional state scope and mounts inside the facilities card. Texas reads as three bars, 2025 to 2027, all amber targets, and tapping 2027 names the sites (Stargate Milam County 1,500 MW, Stargate Abilene Phase 2 500 MW) with the cumulative line. Same component and query key as the Power Map, so both pages share one cached fetch and one tested aggregation.

The earlier "typical monthly bill" derivation is out by owner call (a computed number EIA does not publish); the rates card is untouched from main.

Verification: tsc 0, 484/484 tests, build green. Driven in a real browser: state switching, year taps, panel contents checked for Texas and Virginia; renders keyless.

Merge note: pairs fine with #28 (live demand + fuel mix); overlap in my-grid.tsx is small.

🤖 Generated with Claude Code

https://claude.ai/code/session_019VHXaB2wsfodFneo1VvANN

The rates card gains the number people actually pay: typical monthly
usage (state residential sales divided by residential customers, from
the same EIA retail-sales call, which now also requests sales and
customers) and the bill that usage costs at the month's average rate,
with the year-over-year dollar change and the US-average bill beside
it. The derivation trusts only rows whose own units fields match the
arithmetic, so a silent upstream unit change drops the number instead
of shipping a wrong one.

The facilities card header now places the state among states with
tracked capacity (GW tracked, rank). Registry-derived, so it renders
before any API key is configured.

tsc 0, 487 tests, build green. Exercised in a real browser against
real captured EIA data (the public 861M spreadsheet); live payloads
still need the free EIA_API_KEY set on Replit.

Claude-Session: https://claude.ai/code/session_019VHXaB2wsfodFneo1VvANN
The typical-usage/typical-bill derivation is out: it computed a number
EIA does not publish directly, and the owner does not want computed
consumer stats on the page. The rates card returns to the published
series alone. What stays is real registry data: the facilities header
places the state among states with tracked capacity.

tsc 0, 484 tests, build green, rank verified keyless in a browser.

Claude-Session: https://claude.ai/code/session_019VHXaB2wsfodFneo1VvANN
@aurph aurph changed the title My Grid: the typical power bill, from the same EIA data My Grid: place the state among states with tracked capacity Sep 16, 2026
The Power Map's opening-year timeline gains an optional state scope and
mounts inside the facilities card: pick Texas and the strip shows
tracked capacity arriving 2025-2027, amber where every site that year
is still a schedule, with the tap-a-year panel naming the sites. Same
component, same query key, so the two pages share one cached fetch and
one set of aggregation tests.

tsc 0, 484 tests, build green. Driven in a real browser: state switch,
year tap, panel contents checked for Texas and Virginia.

Claude-Session: https://claude.ai/code/session_019VHXaB2wsfodFneo1VvANN
@aurph aurph changed the title My Grid: place the state among states with tracked capacity My Grid: state rank and the year the buildout arrives Sep 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant