The Independent 100: a study

One page for each of the 99 people on dan’s Independent 100 list: what they publicly do, their public work with links and licenses, how much it bears on our own work, and what we would study next. Plus longer deep dives on a few of them.

Survey 2026-09-24 Public edition 2026-09-25 99 people, 5 deep dives

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. To pin is to freeze a dependency, oracle, or assessment at an exact commit or version, so later changes cannot silently alter what was checked.

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.

Method

  • Scope. The 99 people named on the list, taken with the curator's rank and section as given. We did not add, drop or reorder anyone.
  • First-pass survey, 2026-09-24. Ten AI agent sessions each profiled about ten people from public sources: personal sites and blogs, GitHub repositories and the GitHub API (licenses, stars, last activity, contributor counts), papers, and a small number of public posts. Each record says what the person publicly does, lists their public work with links and licenses, scores its relevance to our own work, and names what we would study next.
  • Deep dives, 2026-09-24 and 2026-09-25. For a few people whose work overlaps ours most, a separate agent session read the source code and writing in depth and compared it with how we work. Each deep dive has its own page.
  • Public edition, 2026-09-25. The records and deep dives were edited for publication under the rules below, every link was checked, and the result was schema-checked before any page was rendered. A reviewer from another model family then reviewed it, and its corrections were applied the same day.
  • Nothing was installed, run or benchmarked for the survey. Where a deep dive ran something, it says so.

Relevance rubric

Each record carries a score from 0 to 5 for relevance to our work: how much the person's public work bears on what we build and study (agent harnesses and orchestration, evals and verification, context and memory, agent security, research and evidence practice, local models, and writing and publishing). It is not a measure of the person, their influence or the quality of their work, and it is not a ranking of people.

  • 5: public, openly licensed work squarely in our lanes that we could study or adopt now.
  • 4: strong overlap, with a caveat such as a missing license, early maturity or a partial fit.
  • 3: a useful method or useful context, less directly adoptable.
  • 2: background for our work, with little to adopt.
  • 1: little connection to our work.
  • 0: no connection (no record uses it).

Each score is one reviewer's judgement: one agent session scored each person, and the ten sessions were not cross-calibrated. Read a 5 as "has something open and in our lanes", nothing more. The lenses on each record (for example agents, evals, security) name the lanes the score refers to.

Deep dives

The 99, in the curator’s order

Grouped by the curator’s sections. The last column is relevance to our work (0 to 5) and its lenses; it is one reviewer’s judgement per person, not a ranking of people. Scores: 24 at 5, 14 at 4, 24 at 3, 26 at 2, 11 at 1.

The Independent 100 as listed by dan, with our relevance score
RankNameHandleSectionRelevance to our work
The Canon (ranks 1 to 10)
#1gwern@gwernThe Canon2 of 5 research-method, writing
#2Jürgen Schmidhuber@SchmidhuberAIThe Canon3 of 5 research, research-method
#3Robin Hanson@robinhansonThe Canon2 of 5 research-method, business
#4janus@repligateThe Canon3 of 5 memory, agents
#5Eliezer Yudkowsky@allTheYudThe Canon2 of 5 research-method, writing
#6Beff@beffjezosThe Canon1 of 5 research
#7Pliny the Liberator@elder_pliniusThe Canon3 of 5 security, agents, mcp, evals
#8Scott Alexander@slatestarcodexThe Canon3 of 5 writing, research-method
#9deepfates@deepfatesThe Canon5 of 5 agents, orchestration, evals, memory, search, mcp
#10Perry E. Metzger@perrymetzgerThe Canon2 of 5 security, verification
The Frontier Outside (ranks 11 to 31)
#11Omar Khattab@lateinteractionThe Frontier Outside5 of 5 agents, evals, search, research-method, orchestration
#12davidad@davidadThe Frontier Outside3 of 5 verification, research-method, security
#13Jeremy Howard@jeremyphowardThe Frontier Outside5 of 5 writing, agents, content, research-method, business
#14will brown@willcbThe Frontier Outside4 of 5 evals, training, agents, verification
#15Connor Leahy@NPCollapseThe Frontier Outside2 of 5 writing, business
#16Rob Miles@robertskmilesThe Frontier Outside2 of 5 content, writing, security
#17George Hotz@realGeorgeHotzThe Frontier Outside3 of 5 local-models, research-method, writing
#18DHH@dhhThe Frontier Outside3 of 5 business, writing, content
#19Varun@varun_mathurThe Frontier Outside3 of 5 agents, security, memory, orchestration, local-models
#20alex zhang@a1zhangThe Frontier Outside5 of 5 agents, memory, orchestration, evals, research-method
#21watermark (anthrupad)@anthrupadThe Frontier Outside1 of 5 content, research-method
#22Stella Biderman@BlancheMinervaThe Frontier Outside5 of 5 evals, verification, research-method, training
#23xlr8harder@xlr8harderThe Frontier Outside5 of 5 evals, local-models, verification, agents
#24doomslide@doomslideThe Frontier Outside1 of 5 writing, research-method
#25Charles Goddard@chargoddardThe Frontier Outside4 of 5 training, local-models
#26Teknium@TekniumThe Frontier Outside5 of 5 agents, orchestration, mcp, memory, security
#27Larissa Schiavo@lfschiavoThe Frontier Outside3 of 5 orchestration, agents, research-method
#28samsja@samsja19The Frontier Outside4 of 5 training, evals, orchestration
#29Erik Bernhardsson@bernhardssonThe Frontier Outside4 of 5 search, verification, research-method, business
#30Jeff Huber@jeffreyhuberThe Frontier Outside5 of 5 search, memory, evals, mcp, rust
#31vas@vasumanThe Frontier Outside2 of 5 business, agents
The Sensemakers (ranks 32 to 52)
#32Simon Willison@simonwThe Sensemakers5 of 5 agents, security, verification, writing, evals
#33Ben Thompson@benthompsonThe Sensemakers2 of 5 business
#34Will Manidis@WillManidisThe Sensemakers2 of 5 writing, business
#35Ethan Mollick@emollickThe Sensemakers4 of 5 evals, verification, research-method, writing
#36swyx@swyxThe Sensemakers3 of 5 agents, content, business
#37Joe Weisenthal@TheStalwartThe Sensemakers2 of 5 business
#38Dan Shipper@danshipperThe Sensemakers5 of 5 agents, orchestration, evals, writing, business
#39John Scott-Railton@jsrailtonThe Sensemakers2 of 5 security, research-method
#40jessicat@jessi_cataThe Sensemakers1 of 5 research-method
#41Alex Volkov@altryneThe Sensemakers4 of 5 mcp, agents, evals, content
#42Zvi Mowshowitz@TheZviThe Sensemakers3 of 5 research-method, writing, evals
#43Teortaxes@teortaxesTexThe Sensemakers2 of 5 local-models, research-method
#44Matt Busigin@mbusiginThe Sensemakers2 of 5 agents, orchestration
#45Michael Thiessen@MichaelThiessenThe Sensemakers3 of 5 evals, verification, agents
#46Mike Taylor@hammer_mtThe Sensemakers5 of 5 evals, verification, agents, writing, content
#47Julia Galef@juliagalefThe Sensemakers2 of 5 research-method, writing
#48Roko@RokoMijicThe Sensemakers1 of 5 research-method
#49Kylie Robison@kyliebytesThe Sensemakers2 of 5 business, content
#50Andrew Curran@AndrewCurran_The Sensemakers2 of 5 research-method, business
#51Tenobrus@tenobrusThe Sensemakers4 of 5 agents, memory, orchestration, security
#52Eli Lifland@eli_liflandThe Sensemakers3 of 5 research-method, evals
The Basement Labs (ranks 53 to 71)
#53kache@yacineMTBThe Basement Labs2 of 5 agents, content, writing
#54vik@vikhyatkThe Basement Labs5 of 5 local-models, content, search
#55Jeffrey Emanuel@doodlesteinThe Basement Labs5 of 5 agents, orchestration, rust, memory, verification, research-method
#56xjdr@_xjdrThe Basement Labs4 of 5 agents, orchestration, local-models, evals, training
#57Michael P. Frank@MikePFrankThe Basement Labs2 of 5 research-method, agents
#58fabian@fabianstelzerThe Basement Labs3 of 5 content, mcp, business
#59Minh Nhat Nguyen@menhguinThe Basement Labs3 of 5 evals, local-models, research-method, agents
#60Jack Morris@jxmnopThe Basement Labs4 of 5 memory, search, security, research-method
#61Cody Blakeney@code_starThe Basement Labs3 of 5 training, local-models, security
#62Danielle Fong@DanielleFongThe Basement Labs3 of 5 evals, agents, memory, research-method
#63Shannon Sands@max_paperclipsThe Basement Labs2 of 5 training, agents
#64kalomaze@kalomazeThe Basement Labs4 of 5 evals, training, local-models, memory, research-method
#65Simo Ryu@cloneofsimoThe Basement Labs3 of 5 training, research-method, writing
#66Ellie Huxtable@ellie_huxtableThe Basement Labs4 of 5 memory, orchestration, rust
#67Ivan Burazin@ivanburazinThe Basement Labs3 of 5 security, agents, orchestration, business
#68orph@orphcorpThe Basement Labs1 of 5 writing
#69Petr Baudis@xpaskyThe Basement Labs5 of 5 agents, orchestration, security, mcp
#70Florian Brand@xeophonThe Basement Labs5 of 5 evals, agents, mcp, local-models, research-method
#71John David Pressman@jd_pressmanThe Basement Labs3 of 5 agents, training, evals, research-method
The Backrooms (ranks 72 to 83)
#72Andy Ayrey@AndyAyreyThe Backrooms2 of 5 agents, security, content, research-method
#73liminal_bardo@liminal_bardoThe Backrooms2 of 5 orchestration, evals, security, agents
#74lumpenspace@lumpenspaceThe Backrooms3 of 5 security, training, agents, writing
#75Andrew (dremnik)@dremnikThe Backrooms2 of 5 writing, business
#76thebes@voooooogelThe Backrooms1 of 5 research-method, local-models, evals, security
#77Rob Haisfield@RobertHaisfieldThe Backrooms3 of 5 research-method, business, content
#78mephisto@karan4dThe Backrooms1 of 5 agents, orchestration, training, mcp
#79Sauers@Sauers_The Backrooms1 of 5 research
#80Mira@_Mira___Mira_The Backrooms3 of 5 verification, evals, agents, research-method
#81nightwing@yaboilyricalThe Backrooms1 of 5 search, memory, local-models
#82veryvanya@veryvanyaThe Backrooms1 of 5 content
#830.005 Seconds@seconds_0The Backrooms3 of 5 research-method, search, content
The Builders on Main (ranks 84 to 99)
#84Taelin@VictorTaelinThe Builders on Main5 of 5 verification, agents, memory, research-method
#85Mario Zechner@badlogicgamesThe Builders on Main5 of 5 agents, orchestration, mcp, evals, security, writing
#86Lewis@ctjlewisThe Builders on Main2 of 5 agents, business
#87dex@dexhorthyThe Builders on Main5 of 5 agents, orchestration, evals, research-method, writing
#88bone@bonegptThe Builders on Main2 of 5 content, business
#89dax@thdxrThe Builders on Main5 of 5 agents, orchestration, local-models, business
#90geoff (Geoffrey Huntley)@GeoffreyHuntleyThe Builders on Main5 of 5 agents, orchestration, verification, security, research-method, writing
#91Aaron Francis@aarondfrancisThe Builders on Main4 of 5 orchestration, agents, business, content
#92Rob Pruzan@RobKnight__The Builders on Main5 of 5 agents, orchestration, verification
#93Jesse Genet@jessegenetThe Builders on Main2 of 5 agents, business, content
#94Raymond Weitekamp@raw_worksThe Builders on Main5 of 5 agents, orchestration, evals, rust, security, research-method
#95Nathan Baschez@nbaschezThe Builders on Main4 of 5 agents, writing, verification, business
#96Nick Dobos@NickADobosThe Builders on Main2 of 5 agents, evals, writing
#97Kyle Mistele@0xblacklightThe Builders on Main4 of 5 agents, orchestration, mcp, security, local-models
#98sunil pai@threepointoneThe Builders on Main5 of 5 agents, orchestration, memory, business, writing
#99Adam@adamdotdevThe Builders on Main5 of 5 agents, orchestration, mcp

Number 100 is the curator’s open wild-card slot. Nominations go to @irl_danB, not to us.

Evidence labels

Claims carry the labels used across Franken Research. [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; a role that comes only from a person's X profile is labelled [Reported: X profile] and paraphrased. [Inference] is our own reasoning. Each record also has an overall confidence (High, Medium or Low) and a list of what could not be verified. A [Verified] label that rests on an X API read or a GitHub license read names the file in evidence/ that holds the row, and every X post the study cites has a row there.

Dates

  • List published by the curator: 2026-09-24.
  • First-pass survey: 2026-09-24. Stars and activity dates are as returned by the GitHub API that day.
  • Licenses of GitHub repositories: the authenticated GitHub license API, 2026-09-25, one row per repository in evidence/licenses.jsonl. "No license file" means the API answered 404; "license file present, not recognised by GitHub" means GitHub could not classify the file.
  • Deep dives: 2026-09-24 and 2026-09-25, as dated on each page.
  • Public edition, link check and review corrections: 2026-09-25.

What the public edition leaves out

  • Public work first. Each page is about what a person has published: code, writing, papers, talks and products. Biography is limited to a sourced professional role where it explains the work, and nothing here judges anyone's character or states their motives.
  • No raw X data. We do not republish profile text, pinned posts, locations or follower counts, and the raw X API responses are not in this repository. evidence/x-reads.jsonl keeps only what the study relies on: for a cited post, its text (with any email address or phone number it quotes replaced, and any withheld site replaced) and the URLs it links; for a pseudonymous account's profile, the URLs its record uses and nothing else.
  • Nothing personal. No home or work location, contact details, family or relationship details, health, financial or legal information about a person, private communications, images of people, or inferences about sensitive traits.
  • No identity resolution. Pseudonymous accounts appear under their handle and the name shown on the list, with no gendered pronouns. Routes and handles are those on the curator's public list. A URL may appear in a pseudonymous record only under one of four rules, and gate N checks every URL against them:
    • a. It is on x.com (or twitter.com) under the listed handle.
    • b. It is a GitHub or Hugging Face account or repository whose owner is exactly the handle, ignoring case.
    • c. The listed X account links it itself, one hop: its profile link, a link in its profile description, or a link in one of its own posts, with the read in evidence/x-reads.jsonl.
    • d. A project page or README names the handle, with the quoted line in evidence/credits.jsonl.
    • Never: personal sites or blogs (even ones named after the handle), biography, profession, employer or location, anything reached through a chain of more than one link, or third-party mirrors of X such as Thread Reader or Nitter. Where that leaves no work to list, the record lists none.
    • Withheld everywhere. A site that a pseudonymous account links from its X profile and that its record does not use, and any site named after a pseudonymous handle, appears nowhere in the study: not in another person's record, a deep dive, an evidence file or a page. A claim about someone else that rested on such a site was given another primary source or dropped.
  • Roles and shared affiliations are sourced. A person's role, or a statement that two people share a lab or employer, appears only with a primary source (their own site, repository or paper) or their own profile, labelled as such.
  • No private material. Local file paths, machine names, process ids, internal ticket ids and the names of private repositories were removed or replaced with a short public description. Each record's list of where the person's work appears in our own files was replaced by one public sentence (in_our_work) or omitted.
  • Nothing about our own deployment. Tools we use are named where they are public and studied on this site, but the study does not say how we configure or run them, what our own systems lack or have not checked, their internal sizes or thresholds, or our internal plans. Where a record once compared a person's work with our setup, it now states the general lesson from the person's work.
  • Neutral on sensitive topics. Crypto tokens, politics and persona accounts are mentioned only where they are part of the person's public work, without judgement and without allegations.
  • Pliny the Liberator (#7) is covered from public metadata and press coverage only, for defensive study. No repository contents were run or summarised; the only line quoted from a repository is its contact line, which names the handle (evidence/credits.jsonl).
  • Security behaviour of third-party tools is stated only as documented behaviour, with a link to the project's own documentation or source, never as a way to reproduce it.
  • Dead links. A link that returned 404 or 410 on 2026-09-25 was removed together with its claim, or kept and marked "link dead as of 2026-09-25" where the item itself still stands.

Limits

  • This is a survey of public material, read in one or two days. Nothing was installed, run or benchmarked for the survey.
  • Every relevance score is one reviewer's judgement, made by one of ten agent sessions that were not cross-calibrated. The scores say how much a person's public work bears on our own work; they do not rank people.
  • Coverage of each person is uneven. Some people publish mostly code, some mostly writing, and some mostly on X, which we read only lightly.
  • Stars and activity dates are as of 2026-09-24 and will drift. Licenses of GitHub repositories are as the GitHub license API reported them on 2026-09-25; other licenses are as the source states. Check the license file before reusing anything.
  • Roles and affiliations can change quickly. A role labelled [Reported: X profile] was taken from the person's own profile and not checked elsewhere.
  • The agents that wrote the records and deep dives are AI coding agents. Their work was checked by other agent sessions and by the build gates, not by the people described.

Corrections

If anything about you or your work is wrong or out of date, or you would rather not be covered here, open a correction with the "Independent 100 study" option: github.com/JYeswak/franken-research/issues/new?template=correction.yml. Every page also has a correction link that fills in its address. Accepted corrections are recorded in the repository changelog with the date. A request to remove a record is honoured without argument.

Request a correction

Is something about this study 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