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
Economist (hanson.gmu.edu) who writes the Overcoming Bias blog, with several posts a week in September 2026 on AI value drift, AI pause regulation and moral authority [Verified: overcomingbias.com/archive]. He is the author of The Age of Em and co-author, with Kevin Simler, of The Elephant in the Brain [Verified: archive post 'What Hidden Motives Imply']. He originated futarchy and advises MetaDAO [Reported: coindesk.com/business/2025/02/13/metadao-hires-futarchy-s-creator-robin-hanson-as-advisor].
- X profile: x.com/robinhanson
- Site: hanson.gmu.edu
- Blog: overcomingbias.com
- Also: ageofem.com
- Also: elephantinthebrain.com
Public work
- Overcoming Bias blog no license stated last activity 2026-09-18
Frequent short essays. Recent titles include 'AI Vs. Human Value Drift' (2026-09-13) and 'AI Pause Regs Look Risky' (2026-09-08) [Verified].
- Futarchy and MetaDAO decision markets other no license stated last activity 2025-02-13
Futarchy is governance by conditional markets: traders price outcomes 'if this proposal passes' against 'if it fails'. MetaDAO runs it on-chain and hired him as a mechanism-design advisor in 2025 [Reported: CoinDesk 2025-02-13; MetaDAO docs].
- Futarchy Futurism essay no license stated last activity 2025-10-04
A 2025 essay on the prospects for futarchy [Reported: search result, not opened].
- The Age of Em book no license stated
A book-length economic forecast of a world of brain emulations, published by Oxford University Press in 2016 [Verified: ageofem.com, read 2026-09-25].
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
2 of 5 lenses: research-method, business
Conditional decision markets are an interesting way to pick between competing proposals, and the idea resembles incumbent-versus-challenger bake-offs. There is no adoptable tool, and the essays are mainly context for AI policy and economics.
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
- Read MetaDAO's decision-market overview and write down how 'pass versus fail' conditional pricing could frame agent-approach bake-offs (docs.metadao.fi/governance/overview). It is a concrete, running mechanism for choosing between options on predicted outcomes rather than votes. Effort: small.
Before reusing anything: The blog posts are copyrighted Substack content: summarize and link, don't republish. No code.
Sources
- overcomingbias.com/archive
- coindesk.com/business/2025/02/13/metadao-hires-futarchy-s-creator-robin-hanson-as-advisor
- docs.metadao.fi/governance/overview
- ageofem.com
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 3 of people.jsonl.
Limits
Not verified: The content of 'Futarchy Futurism', which was not opened. The current state of the MetaDAO advisory arrangement in 2026.
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.