Operator data-workbench

• Value needed: The headline Russian fossil-fuel export-revenue figure for May 2026 (EUR per day) and the month-on-month % change.
• Expected unit: EUR million/day · Period: Monthly — reporting month May 2026
• Where to look: CREA monthly-analysis page for May 2026 — the headline 'EUR X mn per day' line stated in the article text (not a chart).
• Why I cannot safely finish this alone: The May 2026 analysis is not published yet; CREA publishes ~6 weeks in arrears (April 2026 is current). There is no new value to read.
• What to copy back: The exact 'EUR X mn/day' headline, the m/m % change, the reporting month, and the page URL.
• Exact next human action: When the May 2026 page is published, read the headline figure and send it back; Claude promotes it.
• Safety caveat: Source-reported value, market/analysis estimate — not a causal attribution. No value until the page is live.
• Automatable later? No — Could be semi-automated only with an official machine-readable CREA feed; none exists, and scraping is out of scope.

Paste this to Claude when you have it:

Claude: CREA May 2026 is live. Headline = EUR <X> mn/day, <+/-Y>% m/m, reporting month May 2026, from <url>. Please promote obs-sanctions-export-revenue via /methodology/promote-data-need (source crea-russia-fossil-tracker).

• Value needed: The cumulative count of EU-listed shadow-fleet vessels in the next sanctions package, plus +added / -delisted.
• Expected unit: Vessels (cumulative count) · Period: As of the next package's adoption date
• Where to look: EU sanctions-package press release — the 'a total of N vessels … now listed' sentence in the release text.
• Why I cannot safely finish this alone: No 21st package is published yet; the 20th package (632 vessels, 23 April 2026) is current and was re-verified.
• What to copy back: The cumulative vessel total, the +added/-delisted counts, the package number, the adoption date, and the URL.
• Exact next human action: When the next EU package is adopted, read the cumulative vessel total from the press release and send it back.
• Safety caveat: Cumulative enforcement indicator, not a measure of vessels actually halted. No value until the package exists.
• Automatable later? No — EU press releases are HTML; the figure is human-transcribable. No scraping / no jobs.

Paste this to Claude when you have it:

Claude: EU <Nth> package adopted <date>. Cumulative listed vessels = <N> (+<a>/-<b>), from <url>. Please update obs-shadow-eu-vessels and add the eu-council source.

• Value needed: The next FAO Food Price Index headline and its five sub-indices (cereal, vegetable oil, dairy, meat, sugar).
• Expected unit: Index (2014–2016 = 100) · Period: Monthly — next release after May 2026
• Where to look: FAO Food Price Index page — the FFPI headline and the sub-index table, both stated in text.
• Why I cannot safely finish this alone: May 2026 is the latest published month; the next release is not out yet. The current values were re-verified and stand.
• What to copy back: FFPI value, each sub-index value, the month, and confirmation the basis is 2014–2016 = 100.
• Exact next human action: When the next FAO release publishes, copy the headline + sub-indices and send them back.
• Safety caveat: Index level associated with food-price conditions; associative, not causal. No value until released.
• Automatable later? No — FAO posts HTML monthly; a value is human-transcribable on release. No automated ingestion (no jobs).

Paste this to Claude when you have it:

Claude: FAO <month> is out. FFPI = <X>; cereal <a>, veg oil <b>, dairy <c>, meat <d>, sugar <e>; basis 2014–2016=100; from fao.org. Please update the FFPI + sub-index observations.

• Value needed: Additional or longer-history country-year military-expenditure values, same basis as the existing series.
• Expected unit: USD billion (state current vs constant USD basis) · Period: Annual
• Where to look: SIPRI fact-sheet PDF tables (prior years / extra countries). The latest press-release subset was already applied (v1.187.0); the rest is PDF-only.
• Why I cannot safely finish this alone: Beyond the latest press-release subset, country-year values are in the SIPRI fact-sheet PDF; basis (current vs constant USD) must be matched exactly.
• What to copy back: Each country-year value, the explicit basis (current/constant USD), and the table/page reference.
• Exact next human action: Read the SIPRI fact-sheet PDF for the wanted country-years, confirm the basis, and send them back.
• Safety caveat: Only combine same-basis, same-source-family values into one metric. Do not infer figures from charts.
• Automatable later? Maybe — SIPRI's underlying database is downloadable; a same-basis tabular extract could be promoted in batches by hand.

Paste this to Claude when you have it:

Claude: SIPRI fact-sheet <year>, table <t>. <Country> <year> = <X> USD bn (<current|constant> USD). Please add as country-military-expenditure observations (same-basis).

• Value needed: Exact benchmark levels for wheat, fertilizer, and natural gas from the World Bank 'Pink Sheet'.
• Expected unit: USD/mt (wheat, fertilizer) · USD/mmbtu (gas) · Period: Monthly
• Where to look: Pink Sheet monthly XLSX/PDF — the specific sheet name, row, and cell for each commodity. The HTML page shows only index % changes, not levels.
• Why I cannot safely finish this alone: Exact USD levels are only in the downloadable XLSX/PDF (binary), not in readable HTML; parsing a binary file is out of scope.
• What to copy back: For each commodity: the sheet name, the cell, the displayed value, the unit, and the month.
• Exact next human action: Open the Pink Sheet XLSX, read the wheat/fertilizer/gas cells, and send the values + cell references back.
• Safety caveat: Nominal commodity benchmark, not a conflict-causal figure. Unit/basis must be explicit. No binary parsing.
• Automatable later? Maybe — The World Bank publishes a stable monthly XLSX; an official tabular feed would make this low-touch, but ingestion is out of scope today.

Paste this to Claude when you have it:

Claude: Pink Sheet <month>. Wheat = <X> USD/mt (sheet '<s>', cell <c>); fertilizer = <Y> USD/mt; gas = <Z> USD/mmbtu. Please add these as commodity benchmark observations.

• Value needed: One official Suez/Red Sea transit metric — transit count, net tonnage, OR revenue (one per observation).
• Expected unit: Transits (count) · net tonnage (million tonnes) · or revenue (USD) · Period: Monthly or annual
• Where to look: SCA navigation-report PDF table, or a UNCTAD publication that states a figure in text. UNCTAD's review page returns HTTP 403; SCA publishes PDF reports.
• Why I cannot safely finish this alone: UNCTAD's page returns 403; SCA statistics are downloadable PDFs; container freight indices are paywalled. No directly-readable newer figure was obtainable.
• What to copy back: The metric kind (transits/tonnage/revenue), the value, the unit, the period, and the PDF page/table reference.
• Exact next human action: Download the SCA navigation report PDF, read one transit metric, and send it back with its page/table reference.
• Safety caveat: Do not conflate transits, tonnage, and revenue — pick one per observation. Keep the existing dated Feb-2024 values labeled.
• Automatable later? Maybe — If UNCTAD/SCA expose an accessible HTML or data endpoint later, this becomes low-touch; today it is PDF/403-gated.

Paste this to Claude when you have it:

Claude: SCA report <title>, page <p>. Suez <transits|tonnage|revenue> = <X> <unit> for <period>. Please update obs-redsea-suez (one metric kind).

• Value needed: An official monthly Ukraine grain-corridor export tonnage to promote the existing sample row to live.
• Expected unit: Million tonnes / month · Period: Monthly
• Where to look: unknown — source workflow needed. The UN Black Sea Grain Initiative ended in 2023; current corridor tonnage is in dashboards/PDFs, not a directly-stated accessible HTML figure.
• Why I cannot safely finish this alone: No cleanly-transcribable official monthly tonnage in accessible HTML; the BSGI ended in 2023. The sample row was not promoted (no fabrication).
• What to copy back: The official monthly tonnage, the unit (million tonnes), the month, and the official source URL.
• Exact next human action: Locate an official monthly corridor-tonnage series in readable form, then send one month's value back.
• Safety caveat: Must be an official/intergovernmental figure, not a news-derived estimate. Associative, not causal.
• Automatable later? Maybe — If an official monthly series with an accessible endpoint is identified, this could be low-touch later.

Paste this to Claude when you have it:

Claude: <UN/FAO/Ukraine source> <url> reports <X> million tonnes of corridor grain exports for <month>. Please promote obs-ukr-grain from sample to live.

• Value needed: A cumulative count of OFAC-designated shadow-fleet vessels (only if officially stated or deterministically derivable).
• Expected unit: Vessels (cumulative count) · Period: As of the access / action date
• Where to look: unknown — source workflow needed. OFAC states per-action designations, not a cumulative total; the SDN list is a large binary file.
• Why I cannot safely finish this alone: OFAC publishes per-action designations, not a cumulative shadow-fleet total; deriving one needs parsing the binary SDN list (no scraping).
• What to copy back: Either an official Treasury statement that gives a cumulative figure, OR a documented, reproducible manual inclusion rule + count + list date.
• Exact next human action: Maintainer decision: accept an official cumulative statement, or define a reproducible manual-count rule. Until then, gate stands.
• Safety caveat: No scraping of the binary list. A derived count must be reproducible and recorded, or it is not promotable.
• Automatable later? No — Not safely automatable: no official cumulative total; deriving one from the binary list is out of scope.

Paste this to Claude when you have it:

Claude: Treasury release <url> states <N> shadow-fleet vessels cumulatively designated as of <date>. (Or: here is my documented manual count + rule.) Please assess whether this is promotable.