Making 2Ia The Definitive Directory Of Osint And Hacktivist Organizations - Source Excerpt 07 - Suggested timeline

Back to Making 2Ia The Definitive Directory Of Osint And Hacktivist Organizations

Summary

This source excerpt begins near Suggested timeline and preserves the surrounding evidence from 2IA.org/agent-file-handoff/Archive/2026-05-17-organizations-directory-overhaul/Making 2IA the Definitive Directory of OSINT and Hacktivist Organizations.md.

**Source path:** 2IA.org/agent-file-handoff/Archive/2026-05-17-organizations-directory-overhaul/Making 2IA the Definitive Directory of OSINT and Hacktivist Organizations.md

The second priority is content cleanup. Remove the `Hello world!` post, fix or suppress empty category archives until they contain meaningful entries, and turn the current issue hubs into directory gateways by adding “Related organizations” modules to pages such as Open-Source Intelligence, Public Records And FOIA, Surveillance Systems, and Anonymous Hacktivist Collective. Right now those pages are excellent editorial frameworks but poor wayfinding tools for an organizations directory. Internal links are generic; directory links should be explicit. citeturn13view0turn12view5turn19view0turn19view1turn19view2turn19view3

The third priority is governance. Use 2IA’s existing legal and ethical pages to define **three review levels**. Green entries: formal organizations with official sites and straightforward public-interest value. Amber entries: politically contested or activist-hacker groups with official homes but requiring contextual notes. Red entries: leaderless banners, leak brands, or disruption-associated groups where 2IA should publish explanatory, non-promotional profiles and refuse operational detail, invite links, or transient account boosting. This is where 2IA’s current methodology is already stronger than many directories; it simply needs to be translated into profile moderation rules. citeturn12view2turn11view0turn11view1turn12view3

### Suggested timeline

The timeline below mirrors 2IA’s own public ninety-day editorial logic but reorients it around a directory launch. citeturn24view9turn10view0

' ' ' mermaid
gantt
    title 2IA directory launch plan
    dateFormat  YYYY-MM-DD
    section Foundations
    Create org content type, URL pattern, fields, and templates :a1, 2026-05-18, 14d
    Add Organizations nav, collection pages, breadcrumbs, corrections hooks :a2, 2026-05-18, 14d
    Remove placeholder post and suppress empty archives :a3, 2026-05-18, 10d

    section Seed content
    Build first 20 high-priority profiles :b1, 2026-06-01, 14d
    Build remaining 30 seed profiles :b2, 2026-06-08, 21d
    Add issue-hub “Related organizations” blocks :b3, 2026-06-08, 14d

    section SEO and structured data
    Add ItemList JSON-LD to directory indexes :c1, 2026-06-10, 7d
    Add Organization/ProfilePage JSON-LD to org pages :c2, 2026-06-10, 14d
    Canonicals, meta descriptions, XML sitemap, internal-link QA :c3, 2026-06-17, 10d

    section Governance
    Publish moderation policy and risk tiers :d1, 2026-06-20, 7d
    Create monthly re-verification schedule :d2, 2026-06-27, 7d
    Launch correction workflow and review queue :d3, 2026-06-27, 7d

    section Launch
    Public launch of Organizations directory :e1, 2026-07-05, 1d
    Post-launch verification and gap fill :e2, 2026-07-06, 21d
' ' ' 

### Exact technical and editorial actions

Use this as the implementation checklist:

| Priority | Action | Why it matters |
|---|---|---|
| Highest | Add `organization` content type and `/org/{slug}/` URL pattern | Gives 2IA a true directory primitive |
| Highest | Add `/organizations/` index and category indexes | Makes the directory browseable and internally linkable |
| Highest | Add fields for `official_url`, `sameAs`, `last_verified`, `risk_tier`, `confidence_label`, `correction_url` | Makes trust visible |
| Highest | Remove `Hello world!` and hide empty archives | Prevents low-trust first impressions |
| High | Add “Related organizations” panels to issue hubs | Converts current topic pages into discovery pages |
| High | Add `ProfilePage` + `Organization` JSON-LD to every org profile | Improves machine readability and search understanding |
| High | Add `ItemList` JSON-LD to index pages | Helps search engines understand the directory structure |
| High | Write exact, non-generic anchors | “Bellingcat” beats “official site”; “MuckRock” beats “open records toolkit” |
| High | Add correction timestamps and change logs | Essential for controversial or fast-changing groups |
| Medium | Add policy labels: Green / Amber / Red | Makes moderation auditable |
| Medium | Verify contact/social fields monthly, not annually | Social endpoints are volatile |
| Medium | Add GitHub / Mastodon / X only if tied to the official site | Prevents impersonation and stale account pollution |

## Open questions and limitations

The linked-page crawl was strong enough to assess the site’s live architecture, governance pages, child dossiers, and current lack of a true organization directory. It was **not** a full XML-sitemap crawl, because direct sitemap / robots access was unspecified in this environment. Some Start Here child links surfaced exact target URLs but returned fetch restrictions here, so those are best treated as crawl-discovered URLs pending direct QA in the CMS. The biggest remaining implementation risk is not taxonomy—it is **verification discipline** for volatile contact and social URLs. Those fields should be rechecked at publish time even when the official homepage is already known.