AI 2027 Predictions Explained

Last updated

How Do You Turn a Story Into Predictions?

AI 2027 is a narrative scenario rather than a list of predictions. It tells a story, month by month, about how AI development unfolds. To track it, we need to extract discrete, testable claims from that narrative.

This is harder than it sounds, and we want to be transparent about how we do it.

Extraction Process

We read the full scenario and identify specific factual claims: things that are either true or false, happening or not happening. Each claim needs to be:

  1. Specific enough to evaluate: “AI gets better” doesn’t count. “SWE-bench-Verified reaches 85% by mid-2025” does.
  2. Attributable to a timeframe: The scenario is chronological, so most claims have implicit or explicit timing.
  3. Distinct from other claims: We separate claims where they have different observable tests. Related predictions can still overlap, so status counts are not independent votes on the scenario.

Some claims are quantitative (benchmark scores, revenue figures, compute targets) and relatively easy to evaluate. Others are qualitative (institutional dynamics, public sentiment, strategic decisions) and require more judgment.

We currently track 66 predictions across 8 categories. This is not exhaustive. The scenario contains hundreds of implicit claims, and the tracker focuses on the most important and trackable ones.

What We Don’t Track

Some elements of the scenario are inherently untestable or not yet meaningful to track:

  • Hypothetical decisions (e.g., “OpenBrain decides to continue racing”): these are scenario branches, not predictions
  • Extremely vague claims: narrative color that doesn’t make a testable assertion
  • Internal details with no observable test: we track lab dynamics where evidence can bear on a defined claim, while acknowledging gaps in public visibility

Our Status Taxonomy

Every prediction gets one of six statuses. Here’s what each means and how we assign it:

Confirmed

What it means: The predicted development has occurred.

Strong evidence establishes the specified development. Timing is assessed separately: a confirmed milestone can have arrived late, and a late result does not restore the original timing.

Example: “Unreliable but useful AI agents emerge”: ChatGPT agent launched July 2025, consistent with the scenario’s mid-2025 prediction.

What would change it: evidence that we misidentified the event, or a corrected interpretation of the original claim. Every such change is logged.

Ahead

What it means: Reality is outpacing the prediction.

The development is occurring earlier or more aggressively than the scenario described. This is a stronger claim than “on track”: it means the scenario was, if anything, conservative on this point. We use this sparingly and only with clear evidence of acceleration.

Example: Defense contracting with frontier AI labs: CDAO announced awards to four labs in July 2025, before the scenario’s late-2026 window. The early contracting milestone supports the Ahead assessment; it does not establish complete operational integration. CDAO announcement

What would change it: For an ongoing trend, a sustained slowdown could change the pace assessment. For a completed milestone, new evidence would need to change our understanding of what happened or when.

→ On Track

What it means: Current evidence is consistent with the prediction’s trajectory.

Comparable positive evidence supports the predicted trajectory within its original window. Absence of contrary evidence is not enough. This status does not mean the prediction will definitely come true.

Example: METR time horizons doubling roughly every four months: METR’s May 2026 report fits a 105-day doubling time to frontier public models released after January 1, 2024, at 50% task success. Our dossier judges this broadly consistent with the scenario’s trajectory. The fit depends on the model window and benchmark coverage. METR report, Appendix E

What would change it: Confirmation (upgrade to Confirmed) or evidence of a slowdown (downgrade to Behind).

Behind

What it means: Progress is real but slower than predicted.

Comparable evidence falls short of the predicted trajectory or a target has not been established by its original deadline. The accompanying explanation distinguishes measured shortfalls from limited public visibility; missing evidence alone does not prove absence.

Historical example: SWE-bench-Verified reaches 85% was behind its mid-2025 deadline. Its current assessment is Confirmed with late timing: later attainment changes the outcome, not the missed deadline.

What would change it: Catch-up can change an ongoing trajectory assessment. Later attainment of a dated milestone is recorded alongside its missed deadline.

Emerging

What it means: Early signals exist, but it’s too soon to score definitively.

Real indicators point in the predicted direction. The evidence is too thin, too recent, or too ambiguous for a confident status. Many predictions start here and graduate to a firmer status as evidence accumulates.

Example: Global active AI compute reaches $1 trillion in ownership value by late 2026: our September 7 reconstruction places central year-end estimates at $0.83-0.86 trillion, with higher scenarios exceeding $1 trillion. The buildout is close to the scenario’s scale, while the exact outcome remains unresolved. These are modeled values of operating hardware, including servers and networking; annual capex and announced commitments measure different things. Original compute forecast

What would change it: Stronger evidence (upgrade to On Track or Confirmed) or evidence the trend is stalling (downgrade to Behind).

◌ Not Yet Testable

What it means: The specified test is not yet available or its preconditions remain unestablished.

The available evidence cannot yet resolve the specified test. A future deadline does not prevent assessing a qualifying early result. We state whether the limitation is missing preconditions, measurement or public visibility.

Example: AI accelerates algorithmic progress by 4×: the scenario places this milestone in March 2027 and describes it as roughly 2× overall progress once compute constraints are included. Task-level productivity gains alone cannot establish that full research multiplier. AI 2027, March 2027 and its explanatory footnote

What would change it: Time passing and evidence arriving. These will eventually move to other statuses.

How to Read a Prediction Page

Each of our 66 prediction pages follows a consistent structure. Here’s what you’ll find:

  • Title: a clear label for the prediction
  • Status badge: current assessment with color coding
  • Category: which domain (Model Capability, Coding, Geopolitics, etc.)
  • Confidence score: how certain we are about our status assessment
  • Predicted date: when the scenario expects this to happen
  • Last updated: when the page last received a substantive update

At a glance (where specified)

  • Outcome: whether the claim is observed or unresolved.
  • Timing: early, within-window, late, original window passed with outcome unresolved, or pending resolution.
  • Evidence: direct evidence, proxies, disputed findings or insufficient evidence.

A passed deadline can remain unresolved when the outcome is not observable. These fields should be read with the explanation, not as an automatic scoring formula; see methodology §4.

Body Sections

  1. What AI 2027 Predicted: The original claim from the scenario, in context. We quote or closely paraphrase the source material.

  2. How We Track This: Our operationalization: what real-world indicators do we monitor? What benchmarks, data sources, or events count as evidence?

  3. Current Evidence: Sourced evidence supporting our current status assessment. Every claim here should have a link or citation.

  4. Counterevidence & Limitations: What argues against our assessment? What are we uncertain about? This section exists to keep us honest.

  5. What Would Change Our Assessment: Explicit criteria for upgrading or downgrading the status. This makes our reasoning auditable.

  6. Update History: A changelog of status changes with dates and reasoning.

What Confidence Scores Mean

Each prediction carries a confidence score (0-95%) reflecting how certain we are about our status assessment. This is distinct from whether the prediction is “right”: it’s about the strength of our evaluation.

  • 90-95%: Very high confidence. Multiple strong, independent evidence sources. Little room for reasonable disagreement about the status.
  • 70-89%: High confidence. Good evidence, but some ambiguity in interpretation or incomplete coverage.
  • 50-69%: Moderate confidence. Evidence is mixed, the prediction is hard to operationalize, or reasonable people could disagree on status.
  • Below 50%: Low confidence. Limited evidence, inherently difficult to verify, or the prediction is too vague for strong assessment.

A confidence score is not a forecast probability. See the methodology for interpretation examples.

Why This Matters

Tracking predictions from a narrative scenario is inherently messier than scoring a prediction market or a list of concrete bets. We’re making interpretive choices at every step:

  • Which claims count as “predictions”?
  • How do we operationalize qualitative claims?
  • What counts as sufficient evidence?
  • When does “on track” become “behind”?

We try to be transparent about these choices. Our methodology page goes deeper into the principles we follow. And every prediction page shows its evidence and reasoning, so you can disagree with our assessments if you see the evidence differently.

The goal isn’t to “grade” AI 2027 as right or wrong. It’s to build a structured, honest, ongoing record of how the AI 2027 scenario compares with reality. That record should be useful whether the scenario turns out to be prescient or overblown.

Read more: