Making 2Ia The Definitive Directory Of AI Organizations - Source Excerpt 04 - Update and verification plan
Back to Making 2Ia The Definitive Directory Of AI Organizations
Summary
This source excerpt begins near Update and verification plan 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
Browse pages should use `CollectionPage` and `ItemList`, not blog-like archives. For example, a page such as `https://2ia.org/focus/ai-safety/` should explicitly declare itself as a collection page whose main entity is a list of organizations. citeturn9search2turn22search2
' ' ' json
{
"@context": "https://schema.org",
"@type": "CollectionPage",
"@id": "https://2ia.org/focus/ai-safety/",
"url": "https://2ia.org/focus/ai-safety/",
"name": "AI safety organizations",
"mainEntity": {
"@type": "ItemList",
"itemListOrder": "https://schema.org/ItemListOrderAscending",
"numberOfItems": "{count}",
"itemListElement": [
{
"@type": "ListItem",
"position": 1,
"url": "https://2ia.org/org/center-for-ai-safety/"
},
{
"@type": "ListItem",
"position": 2,
"url": "https://2ia.org/org/metr/"
}
]
}
}
' ' '
For a site that wants to be citable by researchers and reusable by others, 2IA should also publish a machine-readable directory export and mark it up as a `Dataset`. citeturn23search2turn9search15turn23search8
' ' ' json
{
"@context": "https://schema.org",
"@type": "Dataset",
"name": "2IA AI organization directory",
"description": "Structured directory of AI, AI safety, governance, standards, academic, public-sector, and open-source organizations.",
"url": "https://2ia.org/data/organizations/",
"license": "{dataset_license_url}",
"distribution": [
{
"@type": "DataDownload",
"encodingFormat": "application/json",
"contentUrl": "https://2ia.org/data/organizations.json"
},
{
"@type": "DataDownload",
"encodingFormat": "text/csv",
"contentUrl": "https://2ia.org/data/organizations.csv"
}
]
}
' ' '
On navigation, the current site should add a first-class organizations layer rather than forcing users through editorial chronology. The top navigation should become something like **Organizations, Tags, Countries, Types, Projects, Publications, Updates, Methodology, Corrections**. Every org page should show “related organizations,” “same-country organizations,” and “same-tag organizations,” because strong internal linking helps users and helps search engines discover the pages that matter. Google’s own documentation emphasizes concise, relevant internal linking and crawlable site structures, along with sitemap submission and Search Console monitoring. citeturn9search3turn25search0turn25search7turn25search10
## Update and verification plan
The current 2IA methodology is already the right philosophical model for ongoing directory maintenance. The key move is to turn it into a **repeatable verification pipeline**. Each organization record should have a visible status such as **Confirmed**, **Likely**, **Needs review**, **Disputed**, **Updated**, or **Corrected**, mirroring the confidence-label logic described on the current Methodology page. Each material edit should be logged the same way the site already envisions corrections and right-of-reply handling. citeturn8view0turn8view1
The best production workflow is straightforward. Use official sites as the default source of truth for name, website, description, contact path, and membership path. Use the organization’s own footer, about page, or existing `sameAs` markup to find canonical social URLs. Use GitHub’s REST API to verify whether an official GitHub organization exists and which repositories are current. Use DBLP’s search API to verify publications, venues, and author affiliations for research-oriented institutions. Use LinkedIn and Google Scholar as human QA layers, not as the system of record. That keeps the pipeline aligned with official sources while still being resilient when official pages are sparse. citeturn24search0turn24search8turn24search1turn24search2
A practical discrepancy policy should flag, at minimum, these cases: official website URL mismatch; redirect chains that point to a different canonical site; organization name mismatch between site and social accounts; founding year mismatch across official site and profile pages; headquarters country mismatch; archived or dormant social links; renamed or absorbed organizations; and publications whose current affiliations no longer match the organization profile. The directory should show these as transparent notes rather than silently “fixing” them. That fits 2IA’s existing commitment to visible uncertainty and public correction. citeturn8view0turn8view1
The crawl cadence should be risk-based. Frontier labs, government AI institutes, and standard-setting bodies change quickly enough that they should be rechecked every **two weeks**. Well-funded nonprofits, benchmark groups, and active open-source institutions should be rechecked **monthly**. Academic centers and slower-moving institutes can usually be rechecked **quarterly** unless a rename, merger, or major publication release is detected. XML sitemaps, sitemap indexes, and Search Console should be part of the operating loop so that fresh updates are discoverable and indexing issues are visible. citeturn25search0turn25search1turn25search10
The 90-day launch sequence should look like this:
' ' ' mermaid
gantt
title Recommended 90-day launch sequence for 2IA directory
dateFormat YYYY-MM-DD
section Foundation
Scope and inclusion rules :a1, 2026-05-20, 10d
Brand and canonical cleanup :a2, 2026-05-20, 14d
Data model and taxonomy :a3, 2026-05-24, 14d
section Build
Profile template and JSON-LD :b1, 2026-06-03, 14d
Browse pages and faceted nav :b2, 2026-06-10, 21d
Dataset export and sitemap setup :b3, 2026-06-20, 14d
section Content
Seed 100-150 anchor orgs :c1, 2026-06-01, 35d
Verification ledger and QA :c2, 2026-06-15, 28d
section Launch
Search Console, validation, fixes :d1, 2026-07-10, 10d
Public launch :d2, 2026-07-22, 1d
section Ongoing
Biweekly and monthly recrawls :e1, 2026-07-23, 60d
' ' '
One last implementation warning is important: if you want a programmatic search layer for discovery or QA, do **not** make Google’s Custom Search JSON API a foundational dependency. Google’s documentation says existing customers have until January 1, 2027, to migrate to an alternative solution. In contrast, GitHub REST and DBLP search remain appropriate durable interfaces for core verification tasks. citeturn24search3turn24search0turn24search1
## Open questions and limitations
The most important limitation is the starting point itself: the public `2ia.org` site does **not** currently expose AI/IA organization listings, so the “table of current listings” is an empty-state audit rather than a normalized inventory. That conclusion is high-confidence based on the public pages reviewed, but it means the real work begins with scope definition and data-model design, not cleanup of existing entries. citeturn0view0turn7view1turn7view2turn2view1turn2view3turn2view4
The prioritized list above is intentionally a **high-confidence seed set**, not a claim that these are the only organizations worth including. A definitive directory will eventually need a broader second and third layer, especially for regional institutes, standards-adjacent groups, open-source collectives, and public-interest organizations that work on AI without being AI-only institutions. The right long-term answer is a transparent inclusion policy plus public corrections and nominations, not a fixed one-time list. citeturn8view0turn8view1
The other open strategic question is branding. Today, the root site is unmistakably framed as “Two Identities Of Anonymous,” with a civil-liberties mission. If the goal is to turn `2ia.org` itself into the definitive AI organizations directory, that is a significant brand pivot. A lower-risk option is to keep the current editorial/research identity intact and launch the directory at a clearly separated top-level path such as `https://2ia.org/org/` with its own landing page and navigation system. citeturn0view0turn7view0turn8view0