Making 2Ia The Definitive Directory Of AI Organizations - Source Excerpt 01 - Making 2IA the definitive directory of AI organizations
Back to Making 2Ia The Definitive Directory Of AI Organizations
Summary
This source excerpt begins near Making 2IA the definitive directory of AI organizations and preserves the surrounding evidence from 2IA.org/agent-file-handoff/Archive/2026-05-17-organizations-directory-overhaul/Making 2IA the definitive directory of AI organizations.md.
**Source path:** 2IA.org/agent-file-handoff/Archive/2026-05-17-organizations-directory-overhaul/Making 2IA the definitive directory of AI organizations.md
# Making 2IA the definitive directory of AI organizations
## Executive summary
As of May 17, 2026, the public site at `https://2ia.org` is **not yet an AI organization directory**. It currently presents itself as “2IA – Two Identities Of Anonymous,” with top-level navigation for Home, Start Here, Research Archive, Methodology, Support, and About, and it describes itself as an independent public-intelligence and civil-liberties research project. The archive is organized around issue hubs, dossiers, investigations, guides, toolkits, and corrections, not organization profiles. One public archive page still exposes the default WordPress “Hello world!” post in May 2026, and searches on the homepage for terms such as “directory,” “LinkedIn,” and “GitHub” did not surface organization-listing functionality. citeturn0view0turn7view0turn7view1turn7view2turn2view1turn2view3turn2view4
That means the opportunity is not to refine an existing directory, but to **launch one on top of a useful editorial foundation**. The strongest parts of the current site are exactly the pieces a trustworthy “who’s who” directory needs: a stated source hierarchy, visible confidence labels, a right-of-reply and corrections pathway, and a privacy-first posture that rejects unnecessary tracking. Those policies already distinguish 2IA from low-trust link farms and generic SEO directories. citeturn8view0turn8view1turn8view2
The highest-leverage move is to make 2IA **entity-centric**. Each organization should get a stable canonical profile page with normalized fields, exact official links, a verification ledger, tags, and change history. Around those profiles, 2IA should publish faceted browse pages by focus area, country, organization type, and update status, along with a public dataset export. The first public launch should target roughly **100–150 anchor organizations** across frontier labs, safety and evaluation groups, governance and civil-society institutions, standards bodies, academic institutes, and open-source communities. citeturn7view1turn8view0turn23search2turn23search3
The first-priority organizations to add are the institutions that define the field’s structure: major frontier labs such as OpenAI, Anthropic, Google DeepMind, and Ai2; measurement and benchmark institutions such as MLCommons and METR; safety and governance nonprofits such as CAIS, Partnership on AI, GovAI, Ada Lovelace Institute, and IAPS; public-sector nodes such as the UK AI Security Institute and NIST’s CAISI; and standard-setting bodies such as GPAI and ISO/IEC JTC 1/SC 42. These will give 2IA immediate credibility across research, deployment, governance, and standards. citeturn11search0turn27view1turn27view2turn27view3turn28view2turn12search3turn28view0turn28view1turn30view2turn30view0turn30view1turn31view0turn31view1turn31view2turn32view1
A crucial implementation detail is to **treat the directory as a dataset as well as a website**. Schema.org supports exactly the structures needed here: `Organization` for each profile, `sameAs` for canonical social identities, `ContactPoint` for member/contact paths, `foundingDate` for provenance, `CollectionPage` and `ItemList` for browse pages, `BreadcrumbList` for navigation, and `Dataset` for downloadable exports. Google’s documentation also recommends using structured data, clear canonical URLs, crawlable URL structures, and sitemaps submitted through Search Console. citeturn23search6turn23search3turn22search0turn22search1turn9search1turn9search2turn22search2turn23search0turn23search2turn25search0turn25search1turn25search2turn26search0turn25search10
Finally, do **not** build the ongoing verification workflow around deprecated APIs or generic search hacks. GitHub’s REST API and DBLP’s search API are appropriate durable inputs for repository and publication verification. By contrast, Google’s Custom Search JSON API is already on a deprecation path for existing customers, with a migration deadline of January 1, 2027, so it should not become a core dependency. citeturn24search0turn24search1turn24search3
## What 2IA is today
The public site today is best understood as a **research publication framework**, not a directory. Home, Start Here, About, and Methodology all describe a civil-liberties/public-intelligence project concerned with surveillance, metadata, algorithmic risk, public records, and corrections. The Research Archive explicitly says it is organized into issue hubs, dossiers, investigations, field guides, toolkits, case studies, trackers, briefings, corrections, and public-records libraries. citeturn0view0turn3view0turn7view0turn7view1turn8view0
The current public crawl therefore yields **no AI/IA organization profiles** to normalize. The public archive also still contains a default WordPress archive entry for May 2026, which is a strong signal that the site is still early in its build-out. citeturn7view2
| Organization | 2IA page URL | Official site | Social links | Contact or membership | Description | Founding year | HQ country | Tags | Projects or publications | Discrepancies |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
| *No public AI/IA organization listings found on 2ia.org as of May 17, 2026.* | — | — | — | — | The public site is currently an editorial/static research site, not an organization directory. citeturn0view0turn7view1turn2view1turn2view3turn2view4 | — | — | — | — | Public branding and search presentation are inconsistent, including a Google result that surfaced `https://2ia.org/` with the mismatched title “ArcSecs.com – Rethinking Gravity and Light,” plus an internal page that uses the alternate brand string “Two Identities Of Anonymous International Intelligence Apparatus.” citeturn1search0turn8view1 |
That inconsistency matters. Before 2IA tries to become the canonical directory for a field, it needs to become **canonical about itself**. The domain currently communicates one editorial identity on-page, a different one in at least one search result, and a third string on a corrections page. At minimum, this calls for title normalization, consistent `<title>`/H1/brand usage, stable canonicals, and Search Console monitoring before the organization directory goes live. citeturn0view0turn8view1turn1search0turn26search0turn25search10
The good news is that 2IA’s current editorial infrastructure is unusually strong for a future directory. Its Methodology page already lays out primary-source preference, confidence labels, public-records handling, AI-use disclosure, minimization, correction workflows, and right of reply. Its Corrections page makes visible correction handling and reply rights explicit, and its Privacy Policy states that the theme does not add analytics, tracking pixels, external fonts, CDN assets, or unnecessary cookies by default. Those policies should be kept and repurposed, not discarded. citeturn8view0turn8view1turn8view2
## The directory model 2IA should adopt
The strongest way to make 2IA definitive is to adopt a **profile-plus-ledger** model rather than a simple link list. Each organization should have one canonical profile URL, one normalized identity record, one short authoritative description, and one visible verification state. The page should answer a small set of durable questions: who the organization is, what it does, where it is based, when it was founded, how to contact or join it, what its official web/social identities are, what it is known for, and what evidence was used to verify those claims. That approach matches 2IA’s current methodology far better than a generic roundup page would. citeturn8view0turn8view1
A good inclusion rule is: include **durable institutions with a material role in AI research, development, safety, governance, standards, infrastructure, or field-building**. Exclude one-off events, conference editions, temporary working groups without stable identity, unaffiliated product pages, and personal blogs. When naming is ambiguous, prefer the organization’s own official brand as link text and store aliases as alternate names. That matters already for entities such as Ai2, GovAI, the UK AI Security Institute, and NIST’s CAISI, all of which have meaningful short names or recent naming changes that users will search for. citeturn27view3turn30view2turn31view0turn31view1
A useful publication and browsing taxonomy would look like this:
' ' ' mermaid
graph TD
A[AI organizations] --> B[Frontier labs]
A --> C[Safety and evaluations]
A --> D[Governance and policy]
A --> E[Standards and benchmarks]
A --> F[Academic institutes]
A --> G[Open-source communities]
A --> H[Public-sector bodies]
B --> B1[OpenAI]
B --> B2[Anthropic]
B --> B3[Google DeepMind]
B --> B4[Ai2]
B --> B5[xAI]
B --> B6[Mistral AI]