Alvo reads UA corridors HU-UA, RO-UA, SK-UA and PL-UA as capacity-rights context for import/export decisions.
Tutorial · JAO auctions
JAO shows the price of border capacity rights, not the price of electricity.
The JAO auction layer answers how many capacity rights were offered, how many were requested, the EUR/MW clearing price and how oversubscribed the corridor was. It is corridor-scarcity context for UA-EU basis, not an energy price forecast and not guaranteed arbitrage.
Tutorial · JAO auctions
What JAO reads
Monthly auctions describe longer forward-basis context; daily auctions describe near-term capacity scarcity.
Cleared EUR/MW is the price of cross-border capacity, not the DAM/IDM energy price.
JAO daily clearing was tested on 189 live war-era days; first-diff r -0.075 means context only, not forecast lift.
HowTo: read JAO auctions
HU-UA, RO-UA, SK-UA and PL-UA have different liquidity and friction context; do not collapse them into one average.
A monthly row reads as forward-basis context; a daily row reads as near-term capacity allocation.
Oversubscription matters more than the price bar alone: it shows demand pressure for the border rights.
JAO shows the rights and capacity auction layer; A11 shows physical movement. They are not interchangeable.
JAO daily clearing is corridor-scarcity context. Do not call it a forecast feed, order recommendation or guaranteed arbitrage.
What not to claim
JAO cleared EUR/MW is a capacity-right price, not a DAM/IDM electricity price.
The 189-day ablation found no daily forecast lift; use JAO as corridor context and cap/band evidence only.
Capacity rights, nominations, flow, settlement and human risk limits still decide whether a spread is executable.
Explicit auctions may be replaced by implicit allocation after market coupling, but the go-live date remains gated.
Tutorial · JAO auctions
Checklist and fields
Minimal sequence before a corridor read.
1. Pick a UA border: HU-UA, RO-UA, SK-UA or PL-UA. 2. Choose the horizon: monthly or daily capacity auction. 3. Read offered MW and requested MW before reading cleared price. 4. Use oversubscription as corridor-scarcity context. 5. Keep JAO separate from A11 physical flows and from energy-price forecasts.
Fields that must not collapse into one capacity price.
jaoAuction.point = {
border: HU-UA | RO-UA | SK-UA | PL-UA,
auctionType: monthly | daily,
deliveryPeriod: YYYY-MM or YYYY-MM-DD,
offeredMw: capacity rights offered by the auction,
requestedMw: demand for those rights,
clearedPriceEur: capacity price in EUR/MW,
oversubscription: requestedMw / offeredMw
}
validation = 189 live war-era days, first-diff r -0.075 => context, not forecast feedTutorial · JAO auctions
JAO auctions FAQ
Why is JAO on /status?
Daily capture is operationally important: Alvo can show whether the cross-border auction feed was captured, even when the result is context rather than a forecast driver.
Does the JAO price forecast DAM?
No. The live 189-day test showed first-diff r -0.075, so the daily clearing price is not promoted as a price forecast feature.
How does this connect to cross-border basis?
Basis compares UA price pressure with neighbouring context. JAO adds the capacity-right scarcity layer: offered MW, requested MW, cleared EUR/MW and oversubscription.
Want JAO beside flows?
The workspace combines cross-border flows, basis, capacity context and forecast caveats without automatic order submission.