Status.

Live operational state of the Amanoki API — the read-only HTTP service that publishes volatility-regime labels, spike probabilities and forecast distributions for wholesale electricity markets. This is what the service says about itself when asked, re-read every 30 seconds.

Data refreshed from api.amanoki.com/v1/status every 30 seconds — whatever the service reports at poll time.

Reading the fields

Most of the tile reads plainly. These are the ones that do not — and one of them looks like a fault when it is working correctly.

• markets live vs markets catalog — the catalog is every market the URL scheme routes; live is the subset with an ingest adapter actually pulling data. JEPX today. The rest accept requests and answer that they are in warmup. Both lists are named in full in the tile above.
• series with data — one series is one (market, area) pair, counted across the whole catalog. JEPX's share of it is the regional prices plus the nationwide system price.
• latest bar — the newest 30-minute settlement interval held, shown in JST. This normally sits ahead of the current time, because JEPX is a day-ahead market: prices for tomorrow's intervals are published today. A timestamp in the past is the thing worth worrying about here, not one in the future. New JEPX prices arrive once a day.
• persistence — whether a database is attached. With it off, the bar history lives in memory and is rebuilt from the deployment image at each restart, which is why uptime is worth reading alongside it.
• model and model trained — which forecast model is serving and when its weights were fitted. The scores that model earned are on /stats.
• build — the commit the running image was built from, so a report about behaviour can be tied to a specific version.