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
ad5a7e509feafb57b1ed7bf69c306b5a3a286b1d· current-main snapshot- Reviewed at
- 2026-09-16T20:13:45Z
- 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-09-16
Pinned source ad5a7e5 ↗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.