ProjectPS-0026

Google Mesa data center

Current company locations page says in development after historical 2025 operational target

Multiple exact scoped state assertions; no flattened badgeNamed site

Executive evidence ceiling

What a decision maker may safely take from this record

Permitted reading

The record supports only the bounded status shown here: Multiple exact scoped state assertions; no flattened badge. Current company locations page says in development after historical 2025 operational target

Not established

A secured site, land control, zoning, utility request, approved service, agreement, funded upgrade, construction, energized power, operation, utilization, or economic capacity.

Owner attention

Cause, revised completion date, construction/energization milestones and site load

Geography
Mesa, Arizona
Object subtype
Named Site With Adverse Status
AI connection
Google compute infrastructure; AI-specific share not public in inspected sources
Recorded figure
No normalized public power quantity
Unit basis
No capacity counted
Countable operating capacity
NO

Conversion-chain position

C0–C21, without implied progression

Handling modeCOMPOSITE SCOPED

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: Multiple exact scoped state assertions; no flattened badge

Current company locations page says in development after historical 2025 operational target

State boundary

Scope-specific assertions

C12Construction startedNamed site

What this establishes

Physical construction has begun for the specified scope.

What this does not prove

Equipment delivery, completed facility, energization, commissioning, IT installation, cluster operation, customer use, utilization/revenue, or economic capacity.

C21Delayed, cancelled, downsized, superseded, or repurposedNamed site

What this establishes

An adverse or changed-status subtype is evidenced for the specified scope and date.

What this does not prove

A universal terminal state, erasure of historical states, final cancellation when only delay/appeal is shown, or failure of related phases/projects.

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 normalized public power quantity is retained as a non-normalized or non-load figure; no MW conversion is performed.

    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

    Google compute infrastructure; AI-specific share not public in inspected sources

    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

Google compute infrastructure; AI-specific share not public in inspected sources

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-0021 · Google updates Mesa to operating, cancels/downsides it, supplies a revised date, or a public primary record establishes the cause of delay.

    Required update: Add new dated state; distinguish objective, current implementation and cause; do not infer causation from chronology.

Source register

Trace the public record

2 linked sources; rights and locators remain attached.

Source records

  1. SRC-0073 — Locations of Google Data Centers

    Google · CONTINUOUSLY UPDATED — CURRENT PAGE · Tier A-minus

    Locator: North America list: Mesa, Arizona marked in development; Jackson County, Alabama listed without in-development marker

    PUBLIC COMPANY/SEC RECORD — CITE/SUMMARIZE

  2. SRC-0074 — Google announces carbon-free energy plan for Mesa data center

    Google · 2024-03-14 · Tier A-minus

    Locator: Historical objective that Mesa data center was expected to be operational in 2025

    PUBLIC COMPANY/SEC RECORD — CITE/SUMMARIZE