# Facility-readiness evidence method

## Purpose

This method tests a narrow question: **what does public evidence establish about whether a named Saudi or UAE compute project can physically receive power and operate at its reported scale?** It is designed for infrastructure investors, utilities, data-center developers, cloud operators, regulators, and technical advisers. It is not a market-size model.

The cutoff for the first ledger is **22 July 2026**. Every blank means *not publicly established by the cutoff*. A blank never means zero, “no,” or “does not exist.”

## Analytical units

The ledger prevents three unlike objects from being mixed:

1. **Physical assets** — facilities or campuses that can, in principle, be tied to a parcel, permit, grid asset, and operating record.
2. **Program watchlist** — clusters or multi-site announcements whose MW cannot yet be allocated to a named physical asset.
3. **Logical service layers** — cloud regions whose customer-facing service status may be known while the underlying facility set, MW, and power path remain undisclosed.

A live cloud region is therefore not coded as a physically operating facility unless the physical asset itself is identified and evidenced.

## No overall readiness score

MADAR does **not** add evidence dimensions into a scalar score or publish an overall ranking. The dimensions answer different questions, and a project can legitimately be advanced on one while opaque on another. An operating facility can have no public grid evidence; a construction site can have a well-defined IT load but no firm connection record.

### Physical delivery: D0–D6

| Code | Highest supported physical milestone |
|---|---|
| D0 | Announcement or current logical-service record only; no physical milestone |
| D1 | Site identified beyond country intent, without demonstrated site control |
| D2 | Land control, lease pathway, or site-specific permit supported |
| D3 | Dated construction start or progress supported |
| D4 | Firm power connection or contracted supply supported |
| D5 | Energization or commissioning supported |
| D6 | Current operation supported by owner, regulator, utility, certification, or procurement evidence |

The stage records the highest observed milestone, not a prediction. It does not imply that every lower-stage document is public.

### Site specificity: S0–S4

| Code | Public site evidence |
|---|---|
| S0 | Country only or undisclosed sites |
| S1 | City only |
| S2 | Named facility/development or documented land-control description |
| S3 | Primary-confirmed street address or coordinates |
| S4 | Parcel, permit, cadastral, or surveyed coordinates joined to the project |

Community databases are discovery evidence. They do not elevate a site to S3 unless a primary record confirms the location.

### Capacity definition: C0–C3

| Code | Public capacity evidence |
|---|---|
| C0 | No MW publicly established |
| C1 | Program, portfolio, cluster, or campus headline that is not phase-allocable |
| C2 | MW attached to a named physical unit, but the measure is undefined or ambiguous |
| C3 | MW attached to a named unit or phase with an explicit measure such as IT load, facility demand, or connection capacity |

IT load, facility load, connection MW, generator capacity, and campus targets are never silently converted or summed.

### Power path: P0–P4

| Code | Project-specific public power evidence |
|---|---|
| P0 | No named project-specific power path |
| P1 | Utility or supply counterparty named, without connection terms |
| P2 | Dedicated grid asset, queue, voltage, requested capacity, or reinforcement procurement identified |
| P3 | Firm connection/supply agreement with MW and material delivery terms identified |
| P4 | Utility energization or equivalent commissioned-power record identified |

National generation capacity, renewable-energy ambitions, and published retail tariffs do not count as a project power path.

### Site operability: O0–O3

| Code | Site-specific public operability evidence |
|---|---|
| O0 | None |
| O1 | Owner design or current-service claim |
| O2 | Independent design certification, permit, or named technical/vendor record |
| O3 | Measured operating evidence such as PUE/WUE, water volume, discharge, or verified route diversity |

Design certification is not constructed-facility certification. A carrier count is not physical route diversity. A cooling label is not a water-supply determination.

## Core deliverability fields

Coverage is calculated across 18 fields: owner, operator, public address, coordinates, MW, capacity definition, dated milestone, power counterparty, substation/grid asset, voltage, requested/firm MW, energization date, cooling, PUE, WUE, water source, fiber diversity, and permit/certification.

Coverage is a **disclosure diagnostic only**. It is not a score and is not used to rank projects.

## Source hierarchy and claim rules

Project owners and counterparties, regulators, utilities, government procurement systems, audited reports, and independent certification registers establish publishable facts. Community infrastructure databases and open maps are used for discovery and conflict checks; their locations and technical attributes require primary confirmation.

Each case stores a primary source, supporting sources, a locator, a dated event history, and material unknowns. When targets conflict, the later dated project update controls the current-status assessment while the original target remains in the event history.

## Important known conflicts

- QAJ01's initial Q3 2025 operating target is superseded for status assessment by Khazna's later December 2026 initial-phase completion target. Neither target is treated as operation.
- PeeringDB's DMM-A coordinate is inconsistent with the stated Dammam/SPARK geography and is rejected pending primary confirmation. The address remains discovery-only.
- Current Quantum Switch service pages support owner-reported operation, but public utility, voltage, firm MW, and energization records were not found.
- Etimad's Naqaa tender supports a dedicated primary-substation procurement record, not an awarded or energized connection.

## Reproduction

Run:

```bash
python3 scripts/acquire_facility_readiness_sources.py
python3 analysis/build_facility_readiness.py
python3 analysis/build_power_path_tracker.py
python3 analysis/audit_facility_readiness.py
python3 analysis/build_facility_report_artifact.py
python3 scripts/validate_project.py
```

The acquisition script archives accessible pages and records URL-only sources when access is limited. The build writes the ledger, event chronology, field-level gap register, machine-readable JSON, and individual dossiers. The audit produces data-quality findings. Validation enforces contracts, joins, dates, numeric fields, coverage arithmetic, and archive hashes.