Technical Or Market DependencyPS-0011

Arizona computational-load flexibility demonstration candidate

Mentioned in official market review as a source lead; primary report not yet acquired

UNKNOWN — PUBLIC EVIDENCE NOT LOCATEDTechnical case candidate

Executive evidence ceiling

What a decision maker may safely take from this record

Permitted reading

The record supports only the bounded status shown here: UNKNOWN — PUBLIC EVIDENCE NOT LOCATED. Mentioned in official market review as a source lead; primary report not yet acquired

Not established

C0, failure, inactivity, confidentiality, cancellation, zero capacity, or any later state.

Owner attention

Primary report, protocol, measured performance, customer obligations

Geography
Arizona
Object subtype
Flexibility Demonstration Candidate
AI connection
Computational-load relevance; AI-specific transferability unverified
Recorded figure
Not normalized
Unit basis
No capacity counted
Countable operating capacity
NO

Conversion-chain position

C0–C21, without implied progression

Handling modeUNKNOWN PUBLIC EVIDENCE

Explicitly represented in this record Not established by this record

  1. C0–C6

    Entry and permission

    1. C0 Concept or rumor
    2. C1 Public announcement
    3. C2 Site identified
    4. C3 Land option or negotiation
    5. C4 Land controlled
    6. C5 Zoning or land-use application
    7. C6 Zoning or land-use approval

  2. C7–C10

    Service-model fork

    1. C7 Utility service or interconnection request
    2. C8 Study or review accepted
    3. C9 Tariff or service pathway identified
    4. C10 Agreement executed or obligation recorded

  3. C11–C17

    Build and operation

    1. C11 Network, generation, or facility upgrades funded
    2. C12 Construction started
    3. C13 Major electrical and cooling equipment delivered
    4. C14 Grid or onsite supply energized
    5. C15 Facility commissioned
    6. C16 IT capacity installed
    7. C17 Compute cluster operating

  4. C18–C20

    Dark Zone

    1. C18 Contracted customer use observed
    2. C19 Utilization or revenue effect observed
    3. C20 Sustained economic compute capacity

  5. C21

    Changed status

    1. C21 Delayed, cancelled, downsized, superseded, or repurposed

Recorded position: UNKNOWN — PUBLIC EVIDENCE NOT LOCATED

Mentioned in official market review as a source lead; primary report not yet acquired

No numbered C-state is assigned by this record. This preserves a forecast, framework, mixed, unknown or otherwise non-project boundary rather than forcing a false position.

State boundary

Scope-specific assertions

UNKNOWN — PUBLIC EVIDENCE NOT LOCATEDTechnical case candidate

No forced project state

Mentioned in official market review as a source lead; primary report not yet acquired

Control rule

C0, failure, inactivity, confidentiality, cancellation, zero capacity, or any later state.

Four-register control

Figures stay in the register that produced them

No cross-register conversion is performed without an explicit source-stated bridge.

  1. R01Load

    Not normalized

    No load-register figure is normalized in this tracker row.

    No load quantity is imputed from money, supply, accelerator count or project state.

  2. R02Supply

    No bridge inferred

    No supply-register quantity is normalized for this record.

    Project state is not treated as proof of deliverable, firm or operating supply.

  3. R03Money

    No bridge inferred

    No separate money-register metric is normalized for this record.

    Capex, contract value, backlog, RPO, revenue and utilization are not converted into capacity or operating state.

  4. R04AI-share

    Source-bounded description

    Computational-load relevance; AI-specific transferability unverified

    Total data-center, campus or portfolio measures remain broader than AI unless the source provides an explicit AI-share boundary.

Aggregation policy: Not summable in this edition. No total, rank or realization percentage is generated.

AI-share boundary

Broader infrastructure does not become AI-only by implication

Computational-load relevance; AI-specific transferability unverified

01

Broader measured scope

Campus, data-center, portfolio, utility, accelerator or financial quantity.

Explicit source bridge

Named AI workload or customer scope · denominator · period · allocation method.

02

AI-attributable subset

Reportable only to the extent directly defined by the source.

Source-bounded AI description

Without the bridge, retain the broader label and stop the attribution.

Control rule: GPU count, company narrative, total campus MW or portfolio capex does not supply an AI-share denominator on its own.

Atomic evidence stack

Claims retain their own ceiling, locator and sources

0 linked claims at the current cutoff.

No atomic claim is linked to this tracker row. Do not strengthen the row from surrounding context.

Record stewardship

What is known, missing and capable of changing the record

Contrary evidenceNo linked test at cutoff

Absence of a linked item is not proof that contrary evidence does not exist.

Negative findingsNo linked negative finding

Continue to treat unknown information as unknown, not zero.

Reopen triggers1 active rule

A qualifying evidence delta requires review and rebuild.

What could change this record

  • OIR-0009 · A public field demonstration or binding service agreement provides measured AI/computational-load flexibility evidence.

    Required update: Capture workload, baseline, response speed/duration, customer constraints, sample, and transferability limits.

Source register

Trace the public record

1 linked source; rights and locators remain attached.

Source records

  1. SRC-0012 — 2025 State of the Markets Report

    Federal Energy Regulatory Commission, Office of Enforcement · 2026-03-26 · Tier A

    Locator: PDF pp. 9–10 (report pp. 7–8), Figure 5 and note 14; other market-review figures as separately cited

    PUBLIC OFFICIAL RECORD — CITE/SUMMARIZE