VoltRL
How should battery-arbitrage policies be compared without information leakage?
Engineering approach
Finite-state control, information-protocol separation, chronological holdout and provenance/checksum audits.
Synthetic sequential-price and historical day-ahead protocols with commit-bound result bundles.
Evidence inspector
- Source reference
a2f7eed0886a5a4844e8db2764c0bfd88615d1d8· pinned historical snapshot- Reviewed at
- 2026-10-06T23:09:53.450Z
- Review scope
- Pinned repository documentation reviewed; upstream scientific tests not rerun here.
- Published checks
- The source documents unit tests and result-bundle integrity, contract and forecast-timing checks. The benchmark was not rerun here.
- Next action
- Read the information protocol, then audit the published result bundle before comparing policies.
Source snapshot · 2026-10-06
Pinned source a2f7eed Published checks
What this does not establish
Not a live bidding system or revenue forecast. Price-taking assumptions omit bid curves, fees, imbalance settlement, market impact and plant-level certification.
Evidence associated with a tagged release or historical CI run does not automatically validate later commits. Review the exact source, environment and assumptions used for any reproduced result.
Read the shared evidence vocabulary →
Evidence snapshot
Reviewed 2026-11-12; evidence records retain their own scope and dates.
- Documentation snapshot
- 2026-10-06 · a2f7eed ·
a2f7eed0886a5a4844e8db2764c0bfd88615d1d8 - Portfolio source record
- 13 results · executed-upstream · 70fa960 ·
70fa9609a1a122055f50f7897720eefc97cbb3e0 - Current release
- v1.1.0 · published 2026-07-16 · tag target
70fa9609a1a122055f50f7897720eefc97cbb3e0 - Current verification
- Successful hosted run · 2026-11-09 · target
b244bc36b512610092064b5f903ed5f08466dc7b - Repository head at 2026-10-17 inventory
a2f7eed0886a5a4844e8db2764c0bfd88615d1d8· inventory snapshot only