Tutorial · cross-border basis
Basis is the gap between the Ukrainian hourly price and a neighboring EU benchmark. Alvo adds flow direction, JAO capacity and coupling context so a trader sees the corridor constraint, not one tempting price gap.
RO, HU or SK can act as a neighboring benchmark; PL carries separate friction/blocker context.
UA price minus gateway benchmark. The sign shows pressure, not an executable trade by itself.
ENTSO-E A11 shows what physically moved across the border; it is not the same as available capacity.
The auction layer shows offered/allocated MW and capacity price: corridor scarcity, not energy price.
RO is the primary/open context; HU is frictional; SK is open; PL needs a blocker caveat.
Compare UA price with the gateway benchmark, but keep FX, delivery hour and licence notes beside it.
Flow shows physical movement; JAO shows offered and allocated capacity plus scarcity.
Coupling timeline, CBAM/carbon wedge and human approval belong before any decision brief.
Even a wide spread does not guarantee capacity, execution, settlement or profit.
Some neighbouring-market prices serve Alvo only as internal model inputs; publicly, Alvo shows only data whose licence allows it, or derived signals.
The coupling path is legally open, but go-live depends on secondary rules, readiness and operator mechanics.
Fields that must not collapse into one spread number.
border.read = {
basis: uaPrice - gatewayBenchmark,
flowDirection: import | export | balanced,
allocatedMw: auction capacity that cleared,
headroomMw: capacity left after scheduled flow,
auctionCost: capacity reservation cost, not energy price
}
decision.guardrails = [
"licence-clean display only",
"human approval",
"no guaranteed arbitrage"
]No. Basis shows pressure between UA and the gateway, but the decision depends on capacity, rights, costs, risk limits and human approval.
Flows show what physically moved. JAO capacity shows what was offered/allocated and how scarcity was priced in the auction layer.
Many NEMO prices carry redistribution limits, so Alvo separates internal model inputs from licence-clean public display.
The workspace combines DAM/IDM, forecast band, cross-border regime and a deterministic decision brief without automatic order submission.