Published 05:30 AEST · Before US Open · Thursday, 9 July 2026Pipeline 05:30 AESTVol. I  No. 65
The Grid
Compute Supply Chain Intelligence · Daily Operational Telemetry
thegridco.ai
EST. 2026 · SYDNEY

Grid Standards v1.3

CC BY 4.0

Conduct & Methodology — Compute Supply Chain Intelligence

First published: May 2026 · Version: 1.3 (July 2026) · License: CC BY 4.0

Part IConduct

Purpose

Grid Standards is an open, versioned vocabulary for compute supply chain intelligence. It defines the terms, classifications, and methodologies The Grid uses to observe and report on AI compute market conditions.

These definitions exist so that compute buyers, analysts, and policymakers can discuss operational market dynamics in language that is stable over time. Grid Standards are public, free, and open for reuse with attribution.

Grid Standards v1.3, The Grid, July 2026. thegridco.ai/standards

Governance

Public Source Priority. No proprietary data, no insider information, no NDA-protected relationships. Value comes from structure, methodology, and daily discipline — not access.
No Investment Positions. The Grid does not hold investment positions in the companies it covers. Structural commitment.
Prediction Accountability. Every forecast is falsifiable, time-bound, and tracked to resolution. The calibration record — including failures — publishes as it accrues; no forecast quality is claimed before the record supports it.
Methodology Transparency. Weights, formulas, band definitions, and normalisation methods are published in this document. Changes are versioned. Historical values labelled with methodology version.
Permanence. Color conventions are permanent. Historical GPI values are labelled with their methodology version and maintain their original meaning indefinitely (see §2.6).

Part IIMethodology

Pillar 1: The Seven-Segment Spine

The Grid organises the compute supply chain into seven segments, presented in a fixed order every day. The reader learns the seven once and never re-learns them. This is the comprehension frame for the daily editorial (THE ASSESSMENT) and the structure every observation hangs on.

1.1 The Segments (fixed order)

#SegmentCoverageBuyer decision
1Fabrication[proxy]Diversify / demand-proof the silicon roadmap
2Packaging & Assembly[gap]Secure packaging-gated allocation, or wait for the CoWoS ramp
3Memory[proxy]Lock memory-dependent capacity, or hedge the exposure
4Power & Cooling[proxy]Factor power lead time into where and when to site capacity
5Networking & Interconnect[gap]Structural only — no forced buyer verb until an instrument earns one
6Compute Supply[instrumented]Lock, wait, or hedge the core procurement decision
7Demand & Deployment[proxy]Proof the need against efficiency gains, or time entry to a demand surge

1.2 Coverage Tags

Every segment is tagged by what it can honestly say today. The tag is load-bearing, not cosmetic.

  • [instrumented]— a direct daily series stands behind the state.
  • [proxy]— an adjacent series stands in (an equity, a derivative, or a monthly-cadence release).
  • [gap]— no live instrument; reported as a documented hole, never fabricated.

Packaging & Assembly is the single most binding segment in the chain and currently a [gap]. The Grid measures where pressure lands, not where it originates, and reports the hole honestly rather than inventing a reading. Networking & Interconnect is likewise structural-only: it carries no forced buyer verb until a supply-chain instrument earns one.

1.3 Per-Segment State

Each instrumented or proxied segment carries one supply-demand condition on a single axis, tightest to loosest:

tight · firm · balanced · soft · well-supplied

These are commodity-market condition terms (Platts / Argus / LME register). Direction of movement is reported separately in the segment's delta, never folded into the state. A [gap]-covered segment carries nostate — the documented hole is shown instead of a fabricated condition. “Tight” and “Balanced” also name two of the GPI bands (§2.4); the overload is deliberate — the same condition read at segment scope and whole-market scope.

1.4 Color Convention

Segment states use buyer-side color inversion. Green is favorable for the compute buyer. Red is unfavorable. This is the opposite of equity market convention.

ColorMeaningExample
GreenFavorable for buyerCompute Supply: well-supplied
AmberNeutralMemory: balanced / firm
RedUnfavorable for buyerMemory: tight

This color convention is permanent and will not change in future versions.

Pillar 2: Grid Pressure Index (GPI)

A 0–100 composite score measuring aggregate pressure on AI compute markets from the buyer's perspective. 50 = the 30-day mean (neutral). Higher values indicate tightening pressure; lower values indicate easing. Calculated daily at 05:30 AEST. Known as the Compute Pressure Index (CPI) in v1.0; renamed in v1.1 with no change to the calculation.

2.1 Contributing Factors (methodology v2.0)

The GPI is composed of four weighted contributing factors, each independently normalised against its own 30-day history.

Contributing FactorWeightMeasurement
GPU Rental Pricing Trend30%7-day rolling average of the all-H100-variant daily median rental price (sanity-bounded $0.20–30/hr, per-GPU), deviation from 30-day baseline
Memory Pressure Score25%DRAM chip spot pricing (DDR5 16Gb + DDR4 16Gb mainstream chip series, TrendForce), deviation from 30-day baseline
Supply Chain Forward Signal30%Composite: US interconnection queue capacity, TSMC monthly revenue momentum, hyperscaler/semiconductor capex trajectory (SEC quarterly filings)
Provider Incident Rate15%Severity-weighted incident count, spike-from-baseline. Severity: critical ×4, major ×3, minor ×1, maintenance ×0.5

The GPU Rental Pricing Trend factor is intentionally a different series from GAP-H100 (Pillar 3, §3.1). The index factor tracks the daily median across all H100 variants (SXM, NVL, PCIe) and is retained unchanged for index-history continuity; GAP-H100 is the assessed price of the SXM class specifically, provider-pooled, defined 12 June 2026. A methodology reader should not conflate the index input with the assessed price.

2.2 Normalisation (z-score)

normalised = 50 + z × 16.67, where z = (value − mean₃₀d) / σ₃₀d

Each factor is scored relative to its own 30-day mean and standard deviation (CNN Fear & Greed precedent). 50 = exactly at the 30-day mean. ±3σ maps to the 0–100 range, clamped to [5, 95]. When fewer than 2 observations exist: defaults to 50 (neutral). v1.0 used min/max scaling; the change to z-score is methodology v2.0.

2.3 Composite

GPI = Σ (normalised_factor × weight)

Weighted sum, rounded to two decimal places, clamped to [0, 100].

2.4 Interpretation (bands)

The published read of whole-market state is the GPI band. The scale has five permanent bands — the names are fixed and do not change across versions:

GPIBandWhat the market is doingBuyer posture
0–24AbundantSurplus capacity; provider competitionNegotiate aggressively
25–44BalancedStandard market conditionsCompare, evaluate, no urgency
45–65TightEmerging pressure; thin availabilityLock reservations, multi-provider
66–80ConstrainedSeller's market; premium pricingSecure capacity now, defer non-critical
81–100CriticalAcute stress; allocation rationingHold workloads, emergency procurement

The bands describe the composite; the per-segment states (Pillar 1, §1.3) describe individual segments. “Tight” and “Balanced” appear at both scopes — the same condition at different altitude.

2.5 Comparable Indices

The GPI follows the precedent of published composite indices: VIX (equity volatility), CNN Fear & Greed (market sentiment), PMI (manufacturing activity), BDI (shipping demand). No equivalent composite index exists for AI compute markets.

2.6 Index History & Revisions — added v1.1

Published GPI history is immutable. Methodology changes are annotated and versioned; historical values are never silently rewritten.

One annotated exception precedes this rule: on 12 June 2026, before any external subscriber existed, the May 11 – June 10 history was recomputed once to correct two corrupt factor inputs — a misparsed DRAM series that had fed the Memory Pressure factor since launch, and unbounded GPU price rows that had contaminated the GPU factor's baseline windows. The pre-recompute series is archived. From the first external subscriber onward, the published series stands as printed.

Second annotation: on 29 June 2026 a v1.0-formula defect affecting May 11–17 was identified and corrected forward. Thirty-one days of window-drift this defect introduced are left in the published series as honest history — annotated here, not rewritten — per the immutability rule above.

2.7 Retired Condition Vocabulary

Versions 1.0–1.1 published a daily market-condition word (the GMCC — clear / cloudy / rain / storm, a weather register). That vocabulary is retired from every published surfaceas of v1.2: it printed the same word for thirteen consecutive days while conditions underneath it moved, which is the opposite of signal. The whole-market read is the GPI band (§2.4); per-segment conditions use the single-axis states (§1.3). The internal classifier survives only as a computed input to the pipeline — it is never surfaced and never a headline. Historical editions that printed weather words stand as published.

Pillar 3: Grid Assessed Prices (GAP)

GAP is The Grid's assessed rental price per GPU class, published daily from the contributing-source panel. Assessments are named by GPU class: GAP-H100, GAP-H200, GAP-B200.

Instrument class — added v1.3. GAP is a posted-price composite: its contributing prices are providers' posted on-demand rates and marketplace asks — listings, not transaction prints. A posted price is sticky by construction, so an unchanged GAP means no contributor repriced; it does not mean the market is still. The Grid never describes GAP as a spot or cleared price. The cleared benchmark in this vocabulary is OCPI (§3.3).

Exact composition — added v1.3 (legs verified 3 July 2026). GAP-H100 currently pools two legs of different instrument kinds, one vote each:

LegInstrument kindWhat the vote isReading (3 Jul 2026)
RunPodPosted rateThe provider's administratively posted on-demand rate for the H100 SXM class$2.69/hr
Vast.aiLowest marketplace asksMedian of the lowest asks (cheapest offer per machine-size series) surfaced by the marketplace's default listing — a lowest-ask cluster, not a market median$1.47/hr

The published level is the median across the two provider votes — with two contributors, their midpoint (≈$2.08/hr at the readings above, against a ~$1.22/hr spread between the legs). Two consequences readers should carry: the composite averages a posted rate with a lowest-ask cluster, so its level sits between two instruments that measure different things; and therefore the Grid Basis LEVEL is construction-dependent— it would shift if the panel composition changed — while basis CHANGEreads as the cleared (OCPI) leg moving, since the posted legs are sticky by construction (§3.3).

3.1 GAP-H100 Definition — added v1.1

GAP-H100is the assessed on-demand rental price of the NVIDIA H100 SXM class (80GB), expressed in per-GPU $/hr. The level is the median across contributing providers — one vote per provider: each provider's offers are reduced to a median first, so a marketplace listing several machine configurations cannot outweigh a provider quoting one price. Multi-GPU machine offers are normalised to per-GPU prices and tracked as distinct configuration series. Only on-demand offers contribute; spot and interruptible listings are excluded. One lineage note: contributing rows captured before 12 June 2026 predate reliable tier labelling at one source (Vast.ai recorded a fixed “spot” label while its stored prices were the on-demand rate); those rows are included as on-demand and the labels stand as recorded rather than being rewritten.

The contributing panel currently comprises two H100 SXM providers (RunPod, Vast.ai), with ThunderCompute contributing to other H100 configurations (PCIe). The panel size is disclosed because it is thin; it will widen as sources are added. H200 is not yet assessment-grade: its offer series must first demonstrate stability under the configuration-normalised methodology introduced 12 June 2026.

3.2 Rates of Change — like-for-like only — added v1.1

A published percentage change is only ever computed between observations of the same series: the same (provider, SKU configuration) pair for GPU rental, the same chip series for DRAM spot. Day-over-day and multi-day deltas are the median of per-series changes across series present at both endpoint dates (a matched-pair index) — never the difference between two daily medians of a changing offer basket. Level and change are therefore reported separately: the level describes today's panel; the change describes repriced like-for-like series. Where fewer than the minimum matched pairs exist, no change is published.

3.3 OCPI Reference Benchmark & Grid Basis — added v1.1

OCPI (Ornn Compute Price Index) is the exchange-traded settlement benchmark for compute, published by Ornn and distributed on Bloomberg Terminal. The Grid cites OCPI as the reference benchmark; it is never Grid-originated data.

Qualification rule: The Grid surfaces only API-sourced OCPI settlements. A newly observed settlement series is provisionaluntil seven consecutive days of API-sourced settlement exist. While provisional, the OCPI value is displayed with its observation count and the Grid Basis — the spread between OCPI settlement and GAP-H100 — is suppressed entirely: a spread against an unqualified benchmark is not informative, and The Grid does not publish it informally. The first API-sourced observation was 10 June 2026; earlier homepage-scraped values were retired from display and are retained only as collection history.

What the basis is — revised v1.3: the Grid Basis reads cleared settlement versus posted list: OCPI is executed transactions; GAP is posted rates (§3.1). A positive basis means transactions are clearing at a premium to posted rates; a negative basis, at a discount. Because the posted leg is sticky by construction, day-to-day basis movement is attributed to the leg that actually moved — ordinarily the cleared leg. The basis is not, by itself, a buyer's-market or seller's-market verdict.

Pillar 4: Supply Chain Dynamics

The seven segments (Pillar 1) sit at characteristic distances from the buyer. Each carries a lead time determining how long an upstream change takes to reach buyer-side pricing — and a propagation lag the editorial always quantifies rather than asserts.

4.1 Segment Lead Times

#SegmentCharacteristic Lead Time
1Fabrication4–6 months
2Packaging & Assembly3–6 months
3Memory3–6 months
4Power & Cooling12–36 months
5Networking & Interconnect3–6 months
6Compute Supply1–4 weeks (where pressure lands; pricing is near real-time)
7Demand & DeploymentReal-time to 1 week

4.2 Causal Dependency Chains

Chain 1 — The HBM Bottleneck (dominant constraint, 2025–2027)
HBM allocation sold outGPU production capped (3–6mo)Cloud GPU availability constrained (1–3mo)GPU rental pricing firms (real-time)Token pricing floor established (1–3mo)
Chain 2 — The Packaging Constraint
CoWoS packaging at limitGPU lead times extend (3–6mo)Rental pricing spikes (1–3mo)Provider margin compression or price pass-through
Chain 3 — Power Infrastructure (structural, 3–6 year resolution)
Interconnection queue saturatedData center capacity delayed (12–36mo)Structural compute scarcity (6–12mo)Elevated pricing persists

4.3 Supply Chain Zones

ZoneSegmentsDescription
UpstreamFabrication · Packaging & Assembly · MemoryWhere physical constraints originate
MidstreamPower & Cooling · Networking & InterconnectWhere capacity is sited and integrated
DownstreamCompute Supply · Demand & DeploymentWhere buyers experience the effects

Pillar 5: Observation Classification

Grid editorial output distinguishes three epistemic classes of data point. Observed values carry inline source attribution; assessed and estimated values state their confidence and basis. The explicit OBS/AST/EST tags are the reference notation for this classification.

OBSObserved

Directly scraped from a public source with machine-readable provenance.

"H100 SXM median $2.08/hr [OBS] (Vast.ai, RunPod, 2026-06-17)"

ASTAssessed

Editorial synthesis with stated confidence and reasoning basis.

"Memory constraint likely to firm rental pricing Q3 [AST] (confidence: medium, basis: HBM sold-out + 3–6 month lag)"

ESTEstimated

Model-derived value where observed data is unavailable. Methodology stated.

"CoWoS monthly output approximately 35K wafers [EST] (basis: TSMC commentary + sell-side consensus)"

Pillar 6: Temporal Horizon Format

Format communicates confidence. As the time horizon extends, the format shifts from precise to probabilistic to directional. This prevents false precision.

HorizonFormatConfidence
Today (0–24h)Specific numbers with deltasVery high
This Week (1–7d)Ranges with directional indicatorHigh
This Month (1–4w)Directional probabilitiesMedium
This Quarter (1–3m)Above/below baseline with probability weightsLow–medium
Structural (3+m)Narrative with causal attributionLow on timing, high on direction

Changelog

v1.3 — July 2026
Consolidation & instrument honesty. The standalone methodology page merges into this document (Part I Conduct · Part II Methodology). GAP classified as a posted-price composite with its exact leg composition documented (§3.1: RunPod posted rate · Vast.ai lowest marketplace asks); Grid Basis restated as cleared settlement vs posted list (§3.3). Second index-history annotation recorded (§2.6, 29 June 2026 formula correction). Retired weather/GMCC condition vocabulary documented (§2.7). Prediction-accountability wording brought to honest tense (record publishes as it accrues).

v1.2 — June 2026
Surface & spine lock. The seven-segment spine (Pillar 1) becomes the comprehension frame, with a single per-segment state vocabulary (tight · firm · balanced · soft · well-supplied) and load-bearing [instrumented] / [proxy] / [gap] coverage tags. The legacy daily condition-classification table is retired; the GPI band scale (§2.4) is the published whole-market read. The supply-chain taxonomy moves from twelve layers to seven segments (Pillar 4). The editorial spine is THE CALL · THE ASSESSMENT · THE MOVE · THE SCORE.

v1.1 — June 2026
Terminology: CPI renamed GPI (Grid Pressure Index); “sub-indicators” are “contributing factors”. Methodology brought current: GPI v2.0 z-score normalisation with four contributing factors (30/25/30/15). Added: index-history immutability and the one-time 12 June 2026 recompute annotation (§2.6), GAP-H100 definition (§3.1), like-for-like velocity methodology (§3.2), OCPI qualification rule and Grid Basis suppression (§3.3).

v1.0 — May 2026
Initial publication of the open vocabulary.

Grid Standards v1.3. Published by The Grid (thegridco.ai).

Licensed under CC BY 4.0 — free for reuse with attribution.

Grid Standards v1.3, The Grid, July 2026. thegridco.ai/standards