Thermal yield double-counted in the SOMA coverage return — Finance querying

[People & Places]

The nightly SOMA coverage roll-up counted the same cohort's thermal yield twice — once off the channel telemetry and once off the node-coverage feed — inflating the billable 'coverage' figure against the KPI pack. Finance spotted that the reconciliation would not tie out and, quite rightly, will not sign a return that double-books the same yield. It is a join fault, not extra yield: the two feeds share cohorts and were being summed rather than de-duplicated.

[Finance]

The coverage return doesn't reconcile to the KPI pack — it's over by exactly the overlap between the two feeds. We're not booking the same yield twice on a commercial return. Please fix the count before month end.

[D. Pike]

Not DNS. It's arithmetic. Rather refreshing, honestly.

[M. Ross]

Two feeds carrying the same cohorts, summed instead of de-duplicated on the join. Added the missing distinct key, re-ran the roll-up, reconciliation ties out to the penny. Finance happy. Closing.