Project Campus Or PhasePS-0028

Google Jackson County existing data center campus

Company states campus has operated since 2019; current locations page lists it as active

C17Existing campus

Executive evidence ceiling

What a decision maker may safely take from this record

Permitted reading

The specified compute cluster is operating under the evidenced source and scope. Company states campus has operated since 2019; current locations page lists it as active

Not established

Measured operating MW, customer use, utilization, revenue, profitability, sustained economic capacity, or operation of every phase.

Owner attention

Operating MW, IT capacity, AI share, utilization and economic output

Geography
Jackson County, Alabama
Object subtype
Existing Campus Baseline
AI connection
Google compute infrastructure; AI-specific share not public
Recorded figure
UNKNOWN — PUBLIC EVIDENCE NOT LOCATED
Unit basis
No public measured operating MW
Countable operating capacity
UNKNOWN — PUBLIC EVIDENCE NOT LOCATED

Conversion-chain position

C0–C21, without implied progression

Handling modeEXACT PROJECT STATE

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: C17

Company states campus has operated since 2019; current locations page lists it as active

Signature model · C17–C20

The evidence boundary becomes less observable after operation

The gradient represents public-record visibility, not the existence or absence of private activity.

  1. C17Threshold observation

    Operating infrastructure

    A bounded operating statement or equivalent observation.

    Boundary: Does not establish customer use, utilization or project economics.

  2. C18Commercial bridge

    Contracted use

    A scoped arrangement linking operating capacity to customer use.

    Boundary: Contract scope, customer identity or capacity denominator may remain private.

  3. C19Measured downstream use

    Utilization or revenue

    A comparable measure with denominator, period and project scope.

    Boundary: Portfolio or company-wide metrics may not isolate the named project.

  4. C20Durable operating-economic bridge

    Sustained economic capacity

    Evidence connecting sustained operation, use and economic output.

    Boundary: Public project-level evidence is often absent or non-comparable.

Unknown is not zero. Missing public C18–C20 evidence is recorded as a scoped gap, not as proof of full utilization, failure or stranded capacity.

Reopen rule: advance only when a new source supplies the missing scoped contract, denominator, period, utilization observation or operating-economic bridge.

State boundary

Scope-specific assertions

C17Compute cluster operatingExisting campus

What this establishes

The specified compute cluster is operating under the evidenced source and scope.

What this does not prove

Measured operating MW, customer use, utilization, revenue, profitability, sustained economic capacity, or operation of every phase.

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

    UNKNOWN — PUBLIC EVIDENCE NOT LOCATED 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

    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

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-0020 · Public evidence provides measured operating load, commissioned IT capacity, customer-use, utilization, revenue/economic incidence, or independent verification for a C17 project.

    Required update: Verify unit, period, site boundary and source function; upgrade only the supported state; preserve contrary evidence and C18–C20 distinctions.

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-0076 — Google announces new investment in Jackson County, Alabama data center

    Google · 2026-06-15 · Tier A-minus

    Locator: Existing campus operating since 2019; $1.5 billion expansion announced for 2026–2027

    PUBLIC COMPANY/SEC RECORD — CITE/SUMMARIZE