esyaGECMatching workspace
Internal demo

THE MATCHING LAB / ESYA GEC

Make every eligible
kWh count.

Follow the energy. See the decisions.
Understand why this is the maximum.

Synthetic scenarios · local calculation
Maximum eligible match COMPLETED RUN
2kWhVerified maximum

2 kWh demand · 100% covered

Eligible supply2 kWh

2 sources · same interval

Unmatched demand0 kWh

0 kWh supply unused

THE QUESTION

A good first match can hide a better total.

G1 can serve either customer. G2 can serve only A. Watch the algorithm revisit its first decision to match every eligible kWh.

INSIDE THE ALGORITHM

Energy finds a better path.

Actual operations · replay
ELIGIBLE SOURCESCUSTOMER DEMANDA, 1 kWhB, 1 kWh0 / 1 kWhG1 → A: 0 kWh allocated; endpoint capacities apply0 / 1 kWhG1 → B: 0 kWh allocated; endpoint capacities apply0 / 1 kWhG2 → A: 0 kWh allocated; endpoint capacities applySource G1G10 / 1 kWhEligible supply G1: 1 kWh; allocated 0 kWhSource G2G20 / 1 kWhEligible supply G2: 1 kWh; allocated 0 kWhCustomer AA0 / 1 kWhDemand A: 1 kWh; allocated 0 kWhCustomer BB0 / 1 kWhDemand B: 1 kWh; allocated 0 kWhSupplyMatchELIGIBLE SOURCESCUSTOMER DEMANDA, 1 kWhB, 1 kWh0 kWhcap 1G1 → A: 0 kWh allocated; endpoint capacities apply0 kWhcap 1G1 → B: 0 kWh allocated; endpoint capacities apply0 kWhcap 1G2 → A: 0 kWh allocated; endpoint capacities applySource G1G10 / 1 kWhEligible supply G1: 1 kWh; allocated 0 kWhSource G2G20 / 1 kWhEligible supply G2: 1 kWh; allocated 0 kWhCustomer AA0 / 1 kWhDemand A: 1 kWh; allocated 0 kWhCustomer BB0 / 1 kWhDemand B: 1 kWh; allocated 0 kWh
Allocated kWhEligible connectionPair labels show allocated energy and effective capacity in kWh. Marks use consistent scales. Attribution, not physical electricity flow.
CURRENT REPLAY STATE0 kWh matched
1 / 4

Animation explains the recorded calculation; its pace is not computation time.

SAME INPUTS. DIFFERENT DECISIONS.

See the difference.

+1 kWh

Completed results for the same eligible network.

Greedy first-fit1 kWh
Exact maximum2 kWh

Greedy takes the first available pair in ID order and never revisits it. It is an illustrative baseline. The existing common-pool workspace does not support these custom links.

WHY THIS IS THE MAXIMUM

A result with a proof.

✓

A feasible match is a lower bound. A cut through the network gives an upper bound.

2Feasible allocation
=
2Minimum-cut capacity

The bounds meet. No extra eligible kWh can be matched in this model.

Inspect proof & exact balances
  • PassEvery allocation uses an allowed pair within its cap
  • PassEvery source stays within eligible supply
  • PassEvery customer stays within demand
  • PassSource use = customer match = total flow
  • PassFeasible flow equals minimum-cut capacity
Original capacities crossing the cut

Supply → G11 kWh

Supply → G21 kWh

{
  "matched_exact": {
    "numerator": "2",
    "denominator": "1"
  },
  "bound_exact": {
    "numerator": "2",
    "denominator": "1"
  },
  "reachable": [
    "$start"
  ]
}

NOTHING DISAPPEARS

Follow every balance.

Current replay state · kWh. Display values round to four decimals; exact fractions remain below and in the evidence.

Source balance

Current replay state, quantities in kWh
ParticipantAllocatedUnused
G101
G201

Customer balance

Current replay state, quantities in kWh
ParticipantAllocatedUnmatched
A01
B01
Pair allocations & exact fractions
Source → CustomerAllocated kWhExact fraction · kWh
G1 → A00
G1 → B00
G2 → A00