Skip to content

Proof before autonomy

Evidence informs a decision. Authority stays explicit.

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.

What each result means

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.

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.

Commercial usefulness

The decision owner determines whether a profile meets the service and business need. A smaller modeled increment is not automatically a useful offer.

Report acceptance

The customer reviews contracted deliverables against agreed criteria. Accepting a report is not acceptance of an operational action.

Operating permission

Facilities and operational authorities control site changes. Engineering, safety, contractual, and regulatory review are separate from this public demonstration.

  1. 01

    Modeled result

    An authored profile, conditions and evidence set.

  2. 02

    Human and business review

    A decision owner determines usefulness.

  3. 03Separate authorization gate

    Operating permission

    Separate site authority and validation required.

Proof informs review. It does not open the operating gate. The current assessment has no live connection or equipment control.

A conditional path to more authority

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.

What evidence must travel with a number

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.

Inspect the proof-pack contents

Community benefits require separate evidence

A modeled facility result does not establish a community benefit. Claims about local electricity affordability, water use, or effects on shared grid infrastructure require their own scope, evidence, and review. The synthetic sample does not assess these outcomes.

Proof before autonomy

Start with one capacity question.

Agree the decision, evidence boundary, responsibilities, and paid scope before work begins.