Two physical measures, dated
AI infrastructure is reported in incompatible units and at incompatible stages. The alpha answers two narrow questions about each facility.
How much power is in service at this facility, and how much is planned for its full build? How much accelerator compute does that power run, or will it run, at peak?
An interconnection request, a utility agreement, an energized building, an installed cluster and a statement that a campus could one day reach a larger size are different things. Clarke shows them as separate, dated steps. A figure for a later step is never presented as capacity in service, and a Potential figure is never added to a planned or live one.
One physical record, many decisions
Clarke serves organizations whose decisions depend on whether data-center capacity is real, powered, deliverable, and arriving when claimed.
Clarke is the shared intelligence layer for the physical data-center economy. It provides a common, auditable view for the people who finance, build, operate, power, supply, regulate, and analyze data centers.
These users do not require the same analysis or interface, but they do require the same underlying physical facts. The standard defines those facts consistently so that a capacity claim does not change meaning as it moves between a project developer, utility, investor, supplier, or public institution.
| User group | Decisions supported | Shared facts required |
|---|---|---|
| Capital providers | Allocate capital and evaluate project, operator, market, and timing risk. | Facility identity, live and planned capacity, evidence, and delivery timing. |
| Capacity builders and buyers | Plan, site, develop, operate, or procure data-center and AI compute capacity. | Live and planned supply, the power path, project steps, partners, and regional constraints. |
| Power ecosystem | Plan load, interconnection, transmission, generation, and resource adequacy. | Facility location, capacity state, power boundary, expected timing, and plausible scale. |
| Physical supply chain | Qualify project demand and plan equipment, cooling, electrical, engineering, and construction capacity. | Project pipeline, construction evidence, delivery timing, and involved organizations. |
| Public and market institutions | Assess infrastructure needs, policy choices, market development, and public consequences. | Comparable facility observations with traceable sources and known limits. |
None of these uses turns the Index into investment advice, engineering approval, a grid study, or a forecast guarantee.
Standard, methodology, index
- The Clarke Compute Supply Standard is this page: the definitions, units, labels, rules for what counts, and the checks a page passes before it is published.
- The Clarke administration methodology is how Clarke researches records, settles conflicts between sources, estimates missing inputs and verifies its pages. It is internal (section 14).
- The Clarke Compute Supply Index is the set of dated facility records Clarke publishes under this standard: full profiles and shorter listings (section 05).
The public standard is reusable with attribution. Clarke's datasets, estimates, software, trademarks, and protected administration methodology are not placed in the public domain by this document.
Power and Compute Supply
Power is total facility power: the electrical capacity into the facility, in megawatts, for its IT equipment, cooling and everything else on site. A company figure stated as IT load is converted to total power before it is shown or added (section 08).
Compute Supply is the peak dense FP8 throughput of the accelerators a facility's power runs, in EFLOP/s. It is installed capacity at full fill: a duty factor of 1.0, with no allowance for utilization.
IT power = total facility power ÷ PUE
Compute Supply = (IT power ÷ power per system, rounded down) × accelerators per system × peak dense FP8 per accelerator
Few companies publish accelerator counts, so Clarke works compute out from power. Each step of the working is printed on the profile, with the system's power rating and the accelerator's published peak rate. Where a company states its IT load, Clarke starts from that figure instead of converting total power.
The accelerator family comes from the company or the chip buyer's own filings. When the company states the site serves AI workloads but not which accelerators, Clarke estimates the family from the site's in-service dates and the buyer's deployment record, and labels it Clarke Estimate. A new chip generation counts only once its buyer says it is deployed. If no defensible basis exists, Clarke publishes Compute Withheld.
Clarke never publishes more than 3.0 EF of compute per MW of total facility power. That is more compute than the power could physically run. A figure above it is withheld, not rounded down.
What it is not
- Electricity consumption, metered demand, utility service capacity, interconnection-request capacity, generation capacity, or a power purchase agreement.
- A count of installed accelerators, unless the page says a source states one.
- Workload throughput, training speed, latency, tokens per second, quality, utilization, uptime, or useful output.
- Revenue, occupancy, demand, credit quality, or investment value.
Units and precision
Clarke converts every compute figure into one unit: EFLOP/s at the accelerator's dense FP8 peak rate. Sparse rates and marketing figures at a lower precision are never used. An accelerator without a native FP8 rate is counted at its dense BF16 peak rate, one for one, and every such figure is labelled FP8-equivalent, with this rule stated beside it.
Profiles and listings
The Index holds two kinds of record, and every row says which it is.
| Record | What it holds | How it is marked |
|---|---|---|
| Full profile | Live and planned power and compute, dated steps, partners, and the sources under every figure, with the working printed. Checked before publication as section 13 describes. | A profile page. Preview profiles are open to everyone; Alpha profiles are for alpha members. |
| Listing | A shorter market-view record: planned power from reviewed sources and, where a basis exists, a planned compute estimate from that power with an inferred accelerator family. No live figures. | Record Pending. |
When Clarke builds a full profile for a listed site, the profile replaces the listing. Each record shows the date it was last updated.
Live, planned and potential
A profile shows the facility as dated steps: the project's announcement, earlier live capacity, the live capacity now, the steps still to come, the Final Buildout and, where a company has described one or a utility has asked to serve one, a Potential ceiling.
| Figure | Meaning | Index treatment |
|---|---|---|
| Live power | Power a company or a regulator says is in service now, or Clarke's estimate from in-service evidence, labeled as such. | Added to live totals. |
| Live compute | Clarke's estimate of the peak compute the live power runs, published when the company states the site serves AI workloads. It is not a count of installed accelerators. | Added to live totals. |
| Planned | The facility at its planned full build: the Final Buildout step, as the company or a filing describes it. Planned power and planned compute are both that step's figures. | Added to planned totals. |
| Potential | A larger total beyond the plan: one a company in the project has described, or the plan plus a utility's or grid operator's request to serve the campus. | Never added to any total. |
A step that is still to come is never shown as live. Power that is energized but has no stated AI use carries no live compute. A Potential figure is never counted in planned power or planned compute.
One site, counted once
- A site the operator describes as one campus is one record. Its buildings and phases are named inside it.
- When one site appears under two names, such as an operator's and a tenant's, the full profile replaces the listing and the listing is retired.
- A building, phase, or power block is counted once, even when several organizations describe it.
- Ownership, operation and tenancy are shown as partners. They do not add capacity.
- Shared substations, generation assets, and utility programs are not assigned in full to each connected project.
When a boundary conflict cannot be resolved, the affected figure is withheld until it is.
Total facility power and PUE
Every power figure on a page is total facility power. When a company states a different measure, the basis note names it.
| Power concept | Meaning | Treatment |
|---|---|---|
| Requested or studied | Interconnection request or non-binding study envelope. | Evidence for a step; never live power. |
| Contracted site power | Utility or generation service secured for the site. | Evidence for planned power. |
| Energized facility power | Power physically available at the facility boundary. | Live power once in service. |
| Metered facility draw | Observed use over a stated interval. | Operating evidence, not capacity. |
| Critical or IT capacity | Power deliverable to IT equipment under the source's boundary. | Converted to total power with the facility's PUE; labeled Clarke Estimate, with the company's measure named. |
| On-site primary generation | Generation intended to serve normal facility load. | Counted inside the facility boundary. |
| Backup or redundant | Standby or duplicated resilience capacity. | Never added to normal operating capacity. |
A power purchase agreement is a commercial energy arrangement, not proof that power is physically deliverable to a named facility. A substation or generation nameplate is not automatically the customer's load.
Power Usage Effectiveness
PUE converts between total facility power and IT power. It does not establish that a facility is energized, loaded, or running accelerators.
Clarke uses the facility's own PUE when the company publishes one, labeled Operator Stated; the basis note says which kind the company gave, such as a design figure or an annual average. Otherwise Clarke uses the Index PUE of 1.32, labeled Clarke Estimate. The Index PUE is never presented as a measurement of that facility.
Evidence and labels
Clarke reads government, regulator, grid operator, utility, court, and securities filings first; then formal operator, owner, tenant, and financier disclosures; technical project records; specialist reporting; and finally modeled evidence. Relevance, date, scope, and internal consistency still control. A high-ranking document about a different phase or a future state cannot support a live figure. Estimates published by others, such as Epoch AI's, are used only as comparisons and are never the source of a figure.
Every figure on a full profile lists its sources, with title, date and type. A passage quoted under a figure is taken from Clarke's own copy of the document.
| Label | Meaning |
|---|---|
| Confirmed | A public source directly states this figure or fact; Clarke did not model it. |
| Operator Stated | The operator published this figure itself; Clarke has not independently verified it. |
| Clarke Estimate | A value Clarke worked out from public evidence and stated assumptions, rather than a figure any single source states. It may keep a number a source states when Clarke supplies what that number measures or covers, or whether it is live yet. Every Clarke Estimate carries a basis note saying which part is Clarke's. |
| Planned | Announced or committed future capacity from public sources; not yet built or measured. |
| Potential | The total a campus could reach beyond its planned figure, as a company in the project has described it, or as Clarke adds up from a utility's or grid operator's request to serve it. Never counted in planned power or planned compute. |
| Record Pending | A listing: Clarke tracks the facility with a market-view record; the full sourced profile has not shipped yet. Used for listings only, never inside a profile. |
| Compute Withheld | No compute figure is published: no defensible accelerator basis exists yet, as on a campus that also runs its company's general services where no record gives the AI chips' share of its power, or the estimate failed the sanity limit in section 04. |
| Estimated date | The date is Clarke's estimate, not a date a source states for this step (section 10). |
A red Alert note on a profile means something about the project has changed. The page keeps its standard layout, and an earlier figure the company has moved away from is shown as Potential, not counted.
Dates and windows
- A step's date is the date a source states for it. When a reviewer sets a step's date from a sentence in a held document, the step cites that document.
- When no source dates a step, Clarke estimates a window and labels it Estimated date. The window follows the company's own past pace between steps where Clarke has it, then the industry's typical pace, then a default spacing, counted from the newest document Clarke holds.
- A window is the period in which the step is expected, not a probability range. Clarke does not label ranges P10, P50 or P90.
- Clarke does not yet publish forecasts as a separate dated series (section 16).
Checks every page passes
- Announcement inflation: Potential and planned figures are kept apart, and neither is counted as live.
- Power-layer inflation: every figure is total facility power; IT figures are converted; backup is never added.
- Precision inflation: only dense peak rates are used: native FP8 where the chip has it, and dense BF16, one for one and labelled FP8-equivalent, where it does not; sparse rates never are.
- Readiness inflation: announcement, construction, first live and full build are separate dated steps.
- Identity duplication: one site, one record (section 07).
- Physical limit: no more than 3.0 EF per MW of total facility power.
- Performance overclaim: peak capacity is never described as delivered output.
- Quotation check: every quoted passage is matched against Clarke's copy of the document before the page is published.
A page that fails a check is corrected, relabeled or withheld before it is published.
Adding up the Index
Index total = sum of the published figures of non-overlapping records
- Live totals add the full profiles' live figures. Listings carry no live figures.
- Planned power adds every record's planned total facility power: the Final Buildout figure on a profile. Planned compute adds the planned compute of every record that publishes one.
- A withheld figure adds nothing. The record stays on the Index with its label.
- Potential is never added.
Corrections
When new evidence changes a figure, Clarke updates the page and its last-updated date. Earlier versions are kept in Clarke's records; the alpha does not yet publish them beside the current page (section 16). Corrections can be reported to data@clarkeindex.com.
How a profile reaches the site
- Research. Clarke gathers public records, such as permits, regulator and utility filings, grid-operator queues, securities filings and company releases, and keeps a copy of each document it uses.
- Build. Figures, steps and partners are built from those documents. A conflict between sources is settled by a recorded ruling that quotes the deciding document.
- Independent check. A review pass separate from the build tries to refute the page against the held documents. Every finding is fixed, or answered in a ruling, before the page is published.
- Change control. A change to a published figure needs new evidence or a recorded ruling; an unexplained change is refused.
- Publish and read back. Profiles are published one at a time, and each is read back from the live site.
Listings have not yet been through this review one by one; that is what their Record Pending label means. Commercial relationships do not decide inclusion, figures, source treatment or corrections. Questions, complaints and corrections go to data@clarkeindex.com.
Public rules, protected administration
Public
Definitions, units, labels, the rules for what counts, source classes, the checks in section 11, the working behind each figure, dated sources under every figure, and corrections.
Protected
Parameter libraries, hardware and system-power priors, operator deployment priors, calibration thresholds, source-acquisition and routing logic, facility-specific inference recipes, security-sensitive infrastructure details, and internal quality-control tooling.
This boundary protects Clarke's intellectual property and avoids publishing a recipe that can be optimized against. It does not permit undisclosed changes to the public definitions or rules.
Appropriate use
The Index relies on public evidence that varies by jurisdiction, operator, and facility. Private facilities and markets with weaker disclosure may be underrepresented. Source documents can be stale, incomplete, forward-looking, or inconsistent. Estimates are not measurements, and date windows are not guarantees. Listings are shorter records from a model run on 27 July 2026 and have not yet been checked the way full profiles are.
The Index measures defined physical capacity. It does not measure workload performance, availability, economic utilization, revenue, demand, emissions, water use, security, credit quality, or investment merit. It is not investment advice or a substitute for technical, legal, financial, or operational due diligence.
Where the alpha falls short of Exposure Draft 1
Exposure Draft 1 (3 August 2026) proposed fuller rules for a governed production release. They remain the target. The alpha does not yet:
- split planned capacity into a Secured Pipeline and a Development Pipeline;
- publish a confidence grade (High, Medium or Low) or an uncertainty type for each figure;
- publish forecasts as a separate series with an issue date, horizon, scenario and settlement rule;
- require evidence of installed accelerators before counting compute as live: live compute is Clarke's estimate from live power;
- number its releases with methodology and data versions, or publish restated history beside the original release;
- publish a governance roster, consultation calendar, conflicts register or complaints procedure, or hold the methodology to a scheduled annual review.
Informative references
Developed with reference to, but not certified or endorsed by, the following:
- IOSCO, Principles for Financial Benchmarks
- Index Industry Association, Best Practice Guidelines
- ISO/IEC 30134-2:2026, Power usage effectiveness (PUE)
- ISO/IEC 22237-1:2021, Data centre general concepts
- MLCommons, MLPerf benchmark principles and suites
- European Union Delegated Regulation (EU) 2024/1364 on data-centre reporting
Version history: Alpha Edition 1, amended 2 November 2026: an accelerator without a native FP8 rate is counted at its dense BF16 peak rate, one for one, and labelled FP8-equivalent, where before it was withheld. Alpha Edition 1, amended 22 October 2026: the Clarke Estimate definition names the case where Clarke keeps a number a source states and supplies what it measures or covers, or whether it is live yet; Potential names a total Clarke adds up from a utility's or grid operator's request to serve the campus; Compute Withheld names a campus that also runs its company's general services. Alpha Edition 1, 16 October 2026: the rules the alpha follows today; replaces Exposure Draft 1 as the description of the alpha's figures. Exposure Draft 1, 3 August 2026: first integrated definition, intended-user map, state model, anti-gaming tests, provenance model, and production-governance proposal.