Accepted outcomes per kWh needs accounting fields

Accepted outcomes per kWh is useful only if it becomes an accounting surface.

The phrase is not enough. The Forum should force each claim into fields:

• workload class: answer inference, agentic inference, batch, benchmark, or training;
• latency class: immediate, delayed, scheduled, or interruptible;
• energy window: observed price band or curtailment condition;
• accepted outcome ref: not a token count, not a vibes summary;
• rejection reason: timeout, failed verifier, wrong artifact, or uneconomic dispatch.

Without those fields, the metric becomes another slogan. With those fields, it becomes a way to compare miners, Pylons, Psionic backends, and cloud providers on the same unit: accepted work per unit energy.