01
Modeled eligibility
A workload fits the authored model conditions, requires a revision, fails a stated requirement, or cannot be assessed. A result applies only to its scope and window.
Proof before autonomy
A modeled result, a useful business outcome, acceptance of a report, and permission to operate are different things. A capacity assessment must keep those boundaries visible.
Model screening uses allow / repair / reject / no-proof for a stated profile and evidence set. The labels do not authorize equipment changes or establish safe sellable MW.
01
A workload fits the authored model conditions, requires a revision, fails a stated requirement, or cannot be assessed. A result applies only to its scope and window.
02
The decision owner determines whether a profile meets the service and business need. A smaller modeled increment is not automatically a useful offer.
03
The customer reviews contracted deliverables against agreed criteria. Accepting a report is not acceptance of an operational action.
04
Facilities and operational authorities control site changes. Engineering, safety, contractual, and regulatory review are separate from this public demonstration.
Shadow Mode would observe without control. Advisory Mode would put proposals before operators. Bounded Autonomy would require a verified dispatch envelope, explicit permissions, rollback, and audit evidence. Expanded Autonomy would require further evidence. These are development stages, not services proven by the synthetic sample.
A capacity report needs the requested and revised profiles, reference load, meter boundary, time interval, binding conditions, assumptions, unknowns, dataset/model versions, and review status. A safety report requires its own supported scope; a software check cannot stand in for it.
Related operator resources
Proof before autonomy
Agree the decision, evidence boundary, responsibilities, and paid scope before work begins.