← The Independent 100: a study

Eli Lifland

#52 in The Sensemakers, the curator’s rank and section @eli_lifland Relevance to our work: 3 of 5

Bracketed tags are evidence labels: [Verified] means we read the page, file or API response ourselves, [Reported] means a source says so and we did not check the underlying thing, and [Inference] is our own reasoning.

Credit

The Independent 100 list was curated by dan (@irl_danB) and published on 2026-09-24 at independent.prose.md (announcement). The ranks and section names are his, and number 100 is his open wild-card slot. This study is ours and is not endorsed by him or by anyone on the list.

What they publicly do

Cofounder and research lead at the AI Futures Project. He worked on the AI 2027 and AI 2040: Plan A scenarios, is a lead author of the AI Futures Model (timelines and takeoff), and co-leads the Samotsvety forecasting team [Verified: elilifland.com]. Earlier he co-created TextAttack and the RAFT benchmark and worked on Elicit at Ought [Verified: same].

Public work

  • AI Futures Model product no license stated

    An interactive model of AI timelines and takeoff speeds; he is a lead author.

  • AI 2027 / AI 2040: Plan A scenarios paper no license stated

    Detailed forecast scenarios of AI development and governance from the AI Futures Project.

  • timelines-takeoff-ai-2027 repo no license file last activity 2025-12-10 · 18 GitHub stars on 2026-09-24

    Python code behind the AI 2027 timelines and takeoff forecasts.

  • TextAttack repo MIT last activity 2026-08-15 · 3,471 GitHub stars on 2026-09-24

    A Python framework for adversarial attacks, data augmentation and training in NLP. He is a co-creator.

  • 2026 AI forecasting survey dataset no license stated

    A forecasting survey he led on 2026 AI milestones.

Licenses of GitHub repositories are from the authenticated GitHub license API on 2026-09-25, one row per repository in evidence/licenses.jsonl (“no license file” means the API found none; “license file present, not recognised by GitHub” means GitHub could not classify it). Other licenses are as the source states. Check the license file before reusing anything.

Relevance to our work

3 of 5 lenses: research-method, evals

Explicit, inspectable forecasting models and calibrated judgmental forecasting are methods we can borrow for franken-research's evidence grading. The timeline code has no license, and TextAttack is outside our current lanes.

Scored 0 to 5 against the study’s relevance rubric: 5 means public, openly licensed work squarely in our lanes that we could study or adopt now, and 1 means little connection to our work. The score is one reviewer’s judgement of how much this public work bears on our own work. It is not a ranking of people and says nothing about the person or the quality of their work.

What we would study next

  1. Read the AI Futures Model methodology and its parameter and uncertainty handling (aifuturesmodel.com). It shows how to make a forecast's assumptions explicit and adjustable, a pattern for our evidence-graded assessments. Effort: medium.
  2. Read his forecasting track-record retro (foxy-scout.com/retro). A worked example of scoring your own past predictions, which we could apply to franken-research calls. Effort: small.

Before reusing anything: timelines-takeoff-ai-2027 has no LICENSE file. TextAttack is MIT, but under the QData org. The scenario and model content is copyrighted by the AI Futures Project.

Sources

Overall confidence in this record: High. Sources were read on 2026-09-24 and every link was checked on 2026-09-25. The full record is line 52 of people.jsonl.

Limits

Not verified: The AI Futures Model page rendered no text when fetched; its methodology was not read. The license terms of the AI 2027 site content were not checked.

This record comes from a first-pass survey of public material by an AI agent session on 2026-09-24, edited for publication on 2026-09-25. Nothing was installed or run for it. Roles, stars and licenses change; see the study’s limits.

Request a correction

Is something about this record wrong or out of date, or would you rather not be covered? Open a correction (a GitHub issue form with this page’s address filled in). A request to remove a record is honoured without argument; accepted corrections are recorded in the changelog with the date.

Help fix it

Each opens a GitHub issue form with this page’s address filled in. You need a GitHub account.

Made by Joshua Nowak (ZestStream) with AI coding agents. Not affiliated with or funded by Jeffrey Emanuel; Joshua uses his public tools and is a paying subscriber to jeffreys-skills.md.

Source on GitHub MIT licensed