Project Campus Or PhasePS-0019

Microsoft Mount Pleasant data center campus

Phase 1 near completion; Phase 2 construction; Phase 3 earthwork

C12Multi-phase campus

Executive evidence ceiling

What a decision maker may safely take from this record

Permitted reading

Physical construction has begun for the specified scope. Phase 1 near completion; Phase 2 construction; Phase 3 earthwork

Not established

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

Owner attention

Energization, commissioning, IT installation, site load and workload

Geography
Mount Pleasant, Racine County, Wisconsin
Object subtype
Multi Phase Campus
AI connection
AI connection documented at company portfolio level; site-specific workload not yet counted
Recorded figure
No normalized public power quantity in inspected source
Unit basis
No capacity counted
Countable operating capacity
NO

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

Phase 1 near completion; Phase 2 construction; Phase 3 earthwork

State boundary

Scope-specific assertions

C12Construction startedMulti-phase campus

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.

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 in inspected source 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

    AI connection documented at company portfolio level; site-specific workload not yet counted

    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

AI connection documented at company portfolio level; site-specific workload not yet counted

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-0019 · Any bounded project receives a material cancellation, downsizing, land/permit decision, construction milestone, service agreement, energization, commissioning, phase redefinition, or portfolio-capacity reconciliation.

    Required update: Create dated state observation; preserve prior state; record supersession/overlap; update affected capacity fields without borrowing later-state language.

Source register

Trace the public record

1 linked source; rights and locators remain attached.

Source records

  1. SRC-0068 — Mount Pleasant datacenter project update

    Microsoft · 2026-04-09 · Tier A-minus

    Locator: March 2026 update: Phase 1 nearing completion; Phase 2 construction; Phase 3 earthwork

    PUBLIC COMPANY/SEC RECORD — CITE/SUMMARIZE