Do not add a proposed utility credit to cash already paid
Separate payment classes and year ranges before evaluating a data-center energy proposal.
Different money, different conditions
A data-center energy proposal can contain several kinds of money with different conditions. A minimum purchase commitment, an annual credit and an approved payment are not interchangeable cash flows. Truthound can check an analyst-prepared model for its declared categories and conditions. It cannot value the agreement, determine utility rates or establish that a proposal has been approved.
The Project Jupiter proposal
Oracle announced a proposed Project Jupiter energy-service agreement on October 13, 2026. It described expected annual power payments over 10 years and a separate proposed customer credit for up to 3 years. These have different horizons and conditions. Treating them as one amount already paid would erase the distinctions the decision needs.
Classify each year separately
Build a row for each agreement, payment class and year. Retain whether an amount is a minimum, a cap or a realized payment, together with approval evidence. A capped benefit must not become a guaranteed annual cash flow simply because a spreadsheet requires a number. Keep an unresolved amount unresolved until the responsible reviewer supplies the interpretation.
Check the supplied grouped summary
For the annual cost summary prepared as a Polars DataFrame, Truthound Core Python SDK 3.3.4's QueryGroupAggregateValidator can inspect supplied SQL group aggregates against declared ranges and expected groups. It can help reveal a missing year or an unexpected payment class in the prepared summary. The SQL, expected groups and amounts are the analyst's responsibility. A correct aggregate does not establish that the underlying agreement is binding or economically beneficial.
Complementary contract checks
Soda Core 4.30.0 documents contract checks such as row count, schema and missing values. Those can complement a governed source table, but are not asserted here as the same group-aggregate rule. A local Truthound analysis and an existing connector-based Soda contract can sit at different boundaries. Respect the v4 configuration and Elastic License 2.0 terms rather than inventing a feature or speed ranking.
Test the effect of an unapproved credit
Run a sensitivity view that excludes unapproved credits and another that includes only the explicitly stated cap, preserving their labels. This is a proposed analytical comparison, not a forecast of payments. Ask the finance and legal owners to explain any year where the model changes from a commitment to an assumed benefit.
Decide within the approved horizon
Use the model for today's decision only after those owners approve its classification and horizon. Recompute when approval or contractual terms change, retaining the original assumptions. Present promised, conditional and realized values separately. That provides a defensible input to the cost discussion without turning a public proposal into a completed financial outcome.
Evidence
- Event checked
- Subject checked
- Modified
