What to review now
The short list of things that actually need a human look, newest first.
What to review now
Newest first. Everything is on main — GitHub renders the Markdown and shows CSVs
as sortable tables, so no local checkout or DataHub account is needed.
2026-09-18 — v1: story and enrich activated
| Thing | Look at | Why it needs eyes |
|---|---|---|
| Story #3 prose | WTI Went Negative. Brent Didn't. | Your voice pass is outstanding. The argument was approved by an independent AI reviewer; the prose is an AI draft rendered from it. |
| Story #3 outline | outline | Approved after one round of corrections: the first draft explained why WTI went negative from price data alone and left out Brent's $9.12 the next day. The mechanism is now attributed to EIA and the CFTC. Agree with where the line was drawn? |
| The two new skills | skills/story/ · skills/enrich/ | Now active, with their guidance packaged in references/ so an installed copy doesn't need this repo. Each former open question has a written policy — do the defaults match your intent? |
2026-08-30 — autonomous session + follow-ups
One diff with everything: https://github.com/datasets/datapressr/compare/7eca8eb…main
| Thing | Look at | Why it needs eyes |
|---|---|---|
| Project Drawdown dataset | repo · README · solutions.csv | Is the tidy shape right? Is the licensing call (facts → PDDL-1.0 + attribution) one you're comfortable with? |
| Portable skills | skills/ · skills/README.md | Do the six skills read consistently? Is the npx skills layout what you expected? |
| This site | site/ | Is the landing page's framing of the product right? |
Open questions parked for you
- Project Drawdown now lives in its own repo at https://github.com/datasets/project-drawdown (moved out of
datapressron 2026-09-05); DataHub publish still pending. - Charting approach is decided for the near term: Observable Plot rendered to static SVG for stories, declarative
viewsfor dataset pages (docs/charting.md). A DataHub-native charting standard is still deferred.
Tracking
All work is tracked in Beads (bd ready); GitHub issues are kept only for the inbox and two open research questions, #6 cloud execution and #11 charting. The earlier issues are closed and preserve the discussion.
Start a working session with NEXT.md, which selects ready work from Beads.
