LIVERESEARCH PREVIEW · REFERENCE RUNS #001 + #002

The Strategic Delta Feed

One dashboard across every domain we run — AI compute and AI policy & economy — each claim tagged by source, all adjudicated in public against open data.

Machine-generated strategic judgment: every claim is dated, falsifiable, and cryptographically sealed at birth, then adjudicated in public against open data — failures published alongside hits.

Data as of Jul 23, 2026 · 43 active claims, sealed · insight-level track record forming (n=0)

43
active claims
43
sealed artifacts
258
signpost checks registered
< 1 day
next window closes
4 for11 against11 timed out39 pending

Reality's checks so far: 4 for, 11 against, 11 timed out, 39 pending. We publish the against column.

Signpost checks adjudicate individual observations; the insight-level track record (below) publishes only when whole calls resolve — currently forming. Counts are unique questions (258 raw checks deduplicated).

The house view

The connective theses across 3 signals clusters — each joins multiple signals. House view sealed Jul 2, 2026 (older than the portfolio below; the theses carry their own stamp).

Strategy X-Ray (V3) — the resourced-vs-stated-posture operator — is code-complete but activates only at the next run boundary, so it contributes no insights to this window yet.

AI ComputeEmerging

AI infrastructure is experiencing a fundamental bottleneck migration from GPU allocation to power/interconnect capacity, creating systematic underpricing of energy-constrained compute.

Joins 4 signals · 4 substrate impacts
  • The assumption that GPU allocation remains the primary bottleneck for frontier training faces mounting contradictory signals
  • The assumption that interconnection queue times don't constrain datacenter siting faces mounting pressure from two contradictory signals
  • Grid capacity assumption supporting three portfolio decisions faces mounting contradictions without offsetting support
  • MISO demand baseline assumption faces pressure from 3.08σ spike to 121,514 MW
supportsPhysical power and interconnect — not GPU supply — is becoming the binding constraint on AI-compute buildout
contradictsGPU allocation remains the primary bottleneck for frontier training
contradictsUS grid can absorb datacenter load growth through 2027 without material curtailment
pressuresCloud GPU on-demand pricing stays within +/-15% of current levels through 2026
What to watch next
Watch: PJM and ERCOT capacity auction clearing prices for 2027/28 delivery years
Compute pricing will bifurcate into power-constrained premium tiers and power-available standard tiers, with energy-secured facilities commanding 30-50% premiums
AI ComputeNon-obvious

NVIDIA's training ecosystem is experiencing accelerated development velocity that signals preparation for post-GPU-scarcity competition dynamics.

Joins 2 signals · 3 substrate impacts
  • NVIDIA Megatron-LM release activity shows 6.27σ deviation from baseline, pressuring capacity and pricing assumptions tied to typical activity levels
  • Federal Register AI-compute publications accelerated 178% this week, contradicting the consensus view that regulatory pace won't materially shift near-term assumptions
pressuresNVIDIA maintains >80% training-accelerator share through 2026
supportsOpen-source framework dominance is contestable; the developer center of gravity is moving up-stack to agent orchestration
pressuresAI-compute export controls remain stable through Q3 2026
What to watch next
Watch: AMD MI300 and Intel Gaudi deployment announcements from hyperscalers for 2026 training workloads
NVIDIA is fortifying software lock-in ahead of hardware commoditization, suggesting they anticipate meaningful accelerator competition within 18 months
AI ComputeNon-obvious

Critical AI infrastructure exhibits the pre-failure signature of underfunded single points of failure across multiple dependency layers.

Joins 2 signals · 2 substrate impacts
  • reference infrastructure dependency configuration matches OpenSSL pre-Heartbleed: open standard with multiple commercial dependants relying on one underfunded maintainer team
  • The assumption that GPU allocation remains the primary bottleneck for frontier training faces mounting contradictory signals
pressuresHuggingFace transformers remains the default model-serving substrate
supportsOpen-source framework dominance is contestable; the developer center of gravity is moving up-stack to agent orchestration
What to watch next
Watch: HuggingFace transformers GitHub issue velocity and maintainer commit frequency relative to dependent project growth
A critical failure in foundational AI infrastructure dependencies will trigger rapid enterprise migration to commercially-supported alternatives

Explore the claims

Each card is a distinct claim, leading with what would prove it wrong. Pick your seat to re-lens the decision implications, or use the filters below.

Grammar
Status
Conviction
0 shown

Verified track record

Every insight is pre-registered with a falsification threshold and sealed at birth; resolutions are sealed too. Public tier reflects calls resolved ≥ 7 days ago.

The scorecard is earned, not written

1Pre-register each claim with an explicit falsifier before any outcome is known.
2Seal it — SHA-256 → daily Merkle root → public anchor — so its timestamp can't be back-dated.
3Adjudicate automatically against open-data signposts as their windows close.
4Publish the scorecard at a public delay, with misses alongside hits.

Signposts adjudicated so far

26 signpost checks have adjudicated (4 for, 11 against, 11 timed out). None of them yet meets our scoring standard, so the scored record is still empty. A trip counts only when it was adjudicated mechanically against the evidence spine or by an independent judge — these were matched by an earlier keyword-overlap method we no longer treat as sound. Insight-level resolutions publish here automatically once a verdict seals under the current rule and the 7-day public delay elapses.

Verify it yourself

Don't take the page's word for the portfolio. The claim, signpost, delta, and track-record files rendering this page are published below with SHA-256 digests; your browser can re-verify them right now. (The House View's synthesis file sits outside this manifest today — that's stated where it renders.)

In-browser verification needs a secure context (HTTPS). Download a file and hash it locally instead.

FileRowsSHA-256Verify
ai-compute/insights-active.jsonl133d721f0346f70ee5b
ai-compute/insights-active.csv1336e73563bf932ca85
ai-compute/insights-deltas.jsonl104f3483a36d1667647
ai-compute/insights-signposts.jsonl2320e30478ce9bc304d
ai-compute/insights-resolved.jsonl45c9cf785c8d2561d
ai-compute/track-record.json48beaff14a5ceba09
ai-compute/entity-crosswalk.jsonl2990f2b63c6b506a3c8
ai-compute/entity-crosswalk.csv299cc3e1ee97458ad19
ai-policy-econ/insights-active.jsonl182d3004e18f8d2a44
ai-policy-econ/insights-active.csv18e58f0a0a675144ab
ai-policy-econ/insights-deltas.jsonl0e3b0c44298fc1c14
ai-policy-econ/insights-signposts.jsonl2620d5aaa7d7e56007
ai-policy-econ/insights-resolved.jsonl0e3b0c44298fc1c14
ai-policy-econ/track-record.json03445b4c3766f2fe9
ai-policy-econ/entity-crosswalk.jsonl2990f2b63c6b506a3c8
ai-policy-econ/entity-crosswalk.csv299cc3e1ee97458ad19

A mismatch usually means a mid-deploy cache; retry in a minute, then inspect. The offline path for professionals:

npx tsx scripts/verify-insight-pack.ts <pack.json>

Each seal chains SHA-256 → daily Merkle root → public anchor.