Skip to main content
A/KAI Kills What?

Methodology

score v1.0 · release 2026-09-a

Methodology

Score version v1.0 · methodology release 2026-09-a. Weights are stored in the app_config table and can be changed without a deploy; changing them requires issuing a new score version so historical results are never silently rewritten.

Definition

What AI Exposure means - and what it does not

It does mean

  • • A large share of an occupation's tasks overlap with what current AI systems can do or substantially assist.
  • • Weighted by task importance, so peripheral tasks count less than core ones.
  • • Adjusted downward when little attributed evidence exists.
  • • Separated into capability, task automation, observed adoption, labour-market signal and evidence strength.

It does not mean

  • • A prediction of unemployment or headcount change.
  • • A measure of economic value or importance of the occupation.
  • • A claim that employers are actually using AI for the work.
  • • A moral or political judgement about the work.

Exposure indexes built from task descriptions (including this one) measure technical overlap. Whether overlap becomes automation depends on cost, reliability, verification, liability, regulation, procurement cycles and complementary investment - none of which are modelled here.

Components

The five components

  1. 1. AI capability exposure

    30% weight

    For each task linked to the occupation, the strongest current model rating on the capabilities that task requires, weighted by task importance. Derived from the model registry, where every capability rating is tied to a provider announcement.

  2. 2. Task automation potential

    30% weight

    Task-level exposure, weighted by task importance. IMPORTANT: this is currently a shared baseline per task (see below) - the same exposure value is used wherever that task appears until per-occupation curation is complete. Only core tasks are displayed as occupation-specific.

  3. 3. Observed AI adoption

    20% weight

    Evidence that organisations are actually using AI for this work - measured usage data and production deployments. Deliberately kept separate from capability.

  4. 4. Labour-market signal

    10% weight

    Observed changes in job postings, employment or earnings. Projections are stored but weighted far below measured outcomes.

  5. 5. Evidence strength

    10% weight

    How much attributed evidence exists and how reliable its sources are. Sources are rated high, medium or low.

Worked example

An occupation with capability 80, task automation 75, adoption 60, labour-market 40 and evidence 85 blends to 71 - and 71 is published, however many evidence items exist. Thin evidence no longer deflates the number; it is reported separately as confidence (see below).

Published score71/100

Weighted mean of the five components, never deflated.

Confidence with 2 evidence items25/100

2 of 8 saturating items - shown as a Low confidence badge.

Confidence with 8+ evidence items100/100

Saturated - no badge.

The confidence rule (replaces shrinkage)

published = round( blended ) · evidence-confidence = round( 100 × min(evidence_count / 8, 1) )

For occupations whose tasks carry two-pass LLM ratings, confidence comes from rating coverage (rated / linked tasks) minus mean rater disagreement - see scripts/score-tasks.ts. Everywhere else, scores with fewer than 4 evidence items carry a Low confidence badge. The badge shows below a task-confidence of 70. Occupations with uncurated task data are additionally marked noindex so they cannot surface in search.

Exposure bands (labels only): Very High ≥ 65 · High 50–64 · Moderate 35–49 · Lower below 35.

Evidence

How evidence is handled

  • • Every evidence item stores its own origin, publication date, evidence type, confidence, direction and magnitude.
  • • Confidence reflects study design: randomised and production deployments (80–95), platform-level observational studies (65–80), cross-country official analysis and scenario estimates (55–75), vendor and survey claims (50–70).
  • • Counter-evidence is stored and used. Studies that find limits to AI effects reduce components rather than being discarded.
  • • Duplicate events are deduplicated rather than counted twice.
  • • Only titles, dates and short summaries are stored from external feeds. Full third-party articles are never republished.

The baseline corpus currently contains 149 evidence rows. Feed inventories and collection details are proprietary and not published.

Versioning

Reproducibility and versioning

Every score row stores the score version, methodology version and an input hash derived from its component inputs and the weights used. Snapshots are append-only: the score_snapshots table is written once per occupation per day per version and never updated in place. If the methodology changes from v1.0 to a new version, historical values stay as they were.

Historical charts show a backcast: the current methodology applied at quarterly checkpoints using only the models and evidence that had been published by each date. This is a reconstruction, not an observation, and is labelled as such wherever it appears. Observed daily snapshots accumulate from the date the index started running (8452 recorded so far).

Sources

Data sources and update frequency

Headline everywhere is exposure_score (labeled “AI Exposure”).

published = round( blended ), where blended is the weight-normalised mean of capability (30%), task automation potential (30%), observed adoption (20%), labour-market signal (10%) and evidence strength (10%). The score is never deflated for thin evidence - instead scores with fewer than 4 evidence items carry a Low confidence badge. Task exposure edges currently reuse the shared v1 editorial baseline per task - they are not per-occupation measurements until marked curated. Occupations flagged hasCuratedTasks=false show core tasks only, carry a “Limited task data” notice, and are noindex + excluded from the sitemap.

  • • O*NET 31.0 Database - occupation titles, SOC codes, task statements with importance/relevance ratings (Task Type Core/Supplemental) and work activities. Contains information from O*NET OnLine by the U.S. Department of Labor, Employment and Training Administration (USDOL/ETA), used under CC BY 4.0. Task statements are being imported per occupation (replacing the shared v1 baseline) and rated individually for AI exposure.
  • • BLS Occupational Employment and Wage Statistics (OES) - employment and median wage reference values (approx, annual). Shown with “≈” and “approx. BLS OES” everywhere.
  • • O*NET-SOC taxonomy - occupation titles, SOC codes, categories and task statements. Each job page links its O*NET record and shows a “Last updated” date from the score row.
  • • Frontier model announcements - capability releases tracked as they are published.
  • • Automation tool launches - agent frameworks and production tooling.
  • • Macro labor context (FRED, BLS projections) - official economic series used as background, not as AI signals.
  • • Empirical research corpus - causal and observational studies on AI and work, each with its own URL, date, confidence and direction.

Collection schedules, feed inventories and polling infrastructure are proprietary and intentionally not published - they are the part of this project that would make it trivially clonable. What's public is the output: scores, verdicts and the live radar.

Limitations

Known limitations

  • • The occupation set is a curated subset of O*NET-SOC, not the full taxonomy. Small and emerging occupations are under-represented.
  • • Task-level exposure values are currently a shared editorial baseline per task, not per-occupation measurements. Secondary edges are hidden from display until curated; occupations with filler tasks are flagged hasCuratedTasks=false.
  • • Capability ratings reflect provider claims and public benchmarks, not independent testing by this project.
  • • Observed adoption data over-represents digital and technical occupations, because usage data comes from AI products whose user base is not representative.
  • • Labour-market outcomes are mostly platform-specific and US-centred. There is little causal evidence at occupation level, and this index does not manufacture any.
  • • Region is not currently modelled. Exposure varies substantially by country and this index does not claim to describe labour markets outside the United States.
  • • Employment and wage values are approximate reference figures and are flagged as such everywhere they appear.

Uncertainty

Uncertainty

No single number describes what AI does to a job. Two occupations with identical exposure scores can face completely different outcomes depending on demand growth, bargaining power, regulation and whether the occupation's value lies in output volume or in accountability. Use the score as a starting point for reading the evidence, not as a conclusion.