US digital infrastructure (PPI data-processing + electricity generation)
Top drivers
⌁ mcp.call("adw-031") vADW-031-live-1.0 Enables IT leaders to forecast infrastructure capacity needs and prevent service outages during peak demand periods.
US digital infrastructure (PPI data-processing + electricity generation)
Top drivers
⌁ mcp.call("adw-031") vADW-031-live-1.0 A cloud infrastructure capacity-planning agent ingests ADW-031 monthly and uses the load_level label and composite_z_score to modulate auto-scaling budget thresholds. When the score rises toward 70 (the 'high stress' threshold defined in the methodology) with a rising trend, the agent pre-authorizes additional reserved-instance purchases 60 days ahead of anticipated demand spikes — the index's electricity generation YoY (60% weight) serves as a proxy for physical infrastructure build-out that leads cloud pricing pressure by a quarter. The current score of 46.3 (17th percentile, rising trend) signals moderate load, but the upward trajectory causes the agent to schedule a capacity review rather than full-scale expansion. The source_lineage (FRED PCU518210518210, IPG2211S) and methodology_version make the trigger condition reproducible and auditable across quarterly planning cycles.
A VP of Technology Infrastructure at a SaaS company uses ADW-031 as a leading macro signal to supplement internal utilization dashboards when making annual data-center and cloud contract negotiations. The index's composite of data-processing PPI growth (capturing pricing pressure from infrastructure vendors) and electricity generation growth (capturing physical capacity constraints) gives the VP a single external benchmark — currently at the 17th percentile but rising — that either reinforces or challenges internal utilization trends. In 2022, when this index was well above its historical mean, the VP would have had external data supporting a decision to lock in multi-year cloud commitments before spot prices rose; that same external signal now argues for flexibility over long-term lock-in.
YoY z-scores: electricity generation (60% weight) + data-processing PPI (40% weight); composite z → 0-100 (50=neutral, >70=high stress)
Version ADW-031-live-1.0 · validated to beat a naive baseline · benchmark: none
One call returns the answer with its reasoning attached — the live Intelligence Object for ADW-031.
{
"product_id": "ADW-031",
"entity": "US digital infrastructure (PPI data-processing + electricity generation)",
"score": 46.3,
"trend": "stable",
"confidence": 0.81,
"top_drivers": [
{
"factor": "elec_generation_yoy_pct",
"contribution": 1.77
},
{
"factor": "data_ppi_yoy_pct",
"contribution": 0.53
},
{
"factor": "composite_z_score",
"contribution": -0.367
}
],
"recommended_use": "Forecast digital capacity needs. Score > 70 = imminent bottleneck risk; plan infrastructure scaling. Descriptive, monthly lag applies.",
"methodology_version": "ADW-031-live-1.0",
"freshness": "2026-06-27T05:00:22.877Z",
"coverage": "US national (FRED PCU518210518210 + IPG2211S)",
"source_lineage": [
"FRED PCU518210518210 (Data-Processing PPI)",
"FRED IPG2211S (Electric Power Generation IP)"
],
"allowed_use": "informational",
"load_score": 46.3,
"load_level": "moderate-stress",
"data_ppi_yoy_pct": 0.53,
"elec_generation_yoy_pct": 1.77,
"ppi_z_score": -0.969,
"elec_z_score": 0.034,
"composite_z_score": -0.367,
"validation_status": "descriptive"
} Every product conforms to the Intelligence Object Model — typed, versioned, and discoverable.
Dashboard
Read the score + drivers in the console.
REST API
/v1/intelligence/adw-031
MCP tool
adw.adw_031
Marketplace
Discoverable by any MCP agent via the MCP registry.
White-label
Embed under your own brand (Platinum).
Organic growth or hype in AI/software?
Method: 10-repo AI/ML basket: stars proxy mindshare (0.6 weight), issue/star ratio proxy engagement (0.4 weight) → 0–100 health score
How strong is developer momentum in TypeScript, Python, Rust, and Go?
Method: Sum new repos across 4 languages in 30d → normalize to 0-100 vs ceiling of 100,000 total repos
Is the OSS software supply chain under elevated vulnerability pressure, and where?
Method: per-pkg sum(cvss3) over recent GA versions / max -> mean across basket -> 0-100