2IA.org Strategic Audit and Overhaul Report

Full report

On this page

Executive Summary

2IA already has a strong editorial thesis. Across its homepage and core pages, it presents itself as an independent public-intelligence research project focused on surveillance, identity systems, metadata, AI inference, public records, anonymity, correction, and civil liberties. It repeatedly emphasizes lawful public intelligence for human freedom, rejects affiliation with government or surveillance vendors, and tells readers to pursue records requests, correction, oversight, and public accountability rather than harassment, technical intrusion, or “signal theater.”

The central problem is not a weak idea. It is that the public product is still closer to a manifesto-plus-theme-demo than to a mature publication. The archive explicitly says “No briefings have been published yet,” multiple category archives are empty, and at least one of those empty category pages exposes admin-facing copy telling the site owner to “Add posts or use the optional draft seed content tool from Appearance.” Meanwhile, search prompts users to “Search 2IA briefings,” even though there are no published briefings to search. Search-engine metadata also appears unstable: one live result for the site currently displays the mismatched title “ArcSecs.com – Rethinking Gravity and Light,” which is a serious SEO and brand-trust problem.

The overhaul should therefore not start by adding more slogans, more categories, or more pages. It should start by turning 2IA into a layered resource with a clear product model: a public-interest research publication, a practical civic-action toolkit, a carefully moderated expert/community layer, and a durable editorial process. The right future state is a site where a first-time reader can quickly understand the mission, an affected person can find a lawful next step, a journalist can verify sourcing and corrections, and an expert contributor can join a governed workflow without turning the project into a surveillance or harassment magnet. That conclusion follows both from the site’s own stated purpose and from the strengths of comparable platforms such as LessWrong, the AI Alignment Forum, Distill, and Discourse.

My highest-confidence recommendation is a hybrid rebuild: keep the privacy-first, text-first ethos, but move to a static-first editorial site + structured CMS + dedicated community layer. In practice, that means rebuilding the public site as a clean knowledge publication, separating community discussion into a purpose-built forum, formalizing the editorial workflow around confidence labels and correction logs, and launching with a small number of genuinely excellent hubs rather than a large number of empty routes. The site should aim to become the best public-facing, rights-forward resource on how surveillance, records, identity systems, algorithmic harm, and civic accountability intersect in ordinary life.

What 2IA is today

Core purpose and current positioning

2IA’s public materials consistently define the site as a civil-libertarian, privacy-forward, independent research project. The site says it exists because civil liberties need “clear records, plain explanations, correction paths, and lawful leverage” against surveillance, identity systems, metadata abuse, and algorithmic suspicion. It also frames itself as a “working map” for adults who want to understand surveillance, public records, anonymous speech, AI harm, and lawful public pressure without drifting into harassment or technical abuse.

That is a compelling strategic position. It is specific enough to stand out, and broad enough to support multiple publication formats. The site is strongest when it translates abstract liberty language into operational civic questions such as: who owns the system, what data enters it, what rights are affected, what records exist, and how correction can travel as far as the error did. The homepage’s “Who Cares Wizard” also shows an important product instinct: it tries to route readers from a vague concern to a concrete next step without requiring an account or submission, and says the choices stay in the browser rather than being sent to the server.

Assumptions and scope

This audit is based on the public website and public official/primary materials accessible at the time of review. I did not have access to admin settings, analytics, private roadmaps, source code, traffic logs, or a verified live infrastructure inventory. I could infer some aspects of the current stack from the site’s public behavior and text, but not confirm every detail. I also could not validate every live accessibility or security control from the outside. Where something is inferred rather than directly observed, I label it as an inference.

Current content inventory and quality

The public site has a respectable number of pages, but the visible content is heavily weighted toward mission, ethics, and process pages, not toward durable research artifacts. The strongest published materials today are the core trust pages: Start Here, About, Methodology, Ethics and Civil Liberties, Public Records and FOIA, Corrections and Right of Reply, Privacy Policy, Lawful Contact, Contact, Support, Newsletter, and Volunteer. The weakest area is the actual research corpus: the Research Archive says there are no published briefings yet, and the visible topic-category archives are empty.

The content quality is therefore high in intent, low in public proof. 2IA has already written the constitution of the project; it has not yet built the archive that would make that constitution matter.

Current technical posture

A cautious inference from the public pages is that 2IA is running on WordPress or a strongly WordPress-like CMS/theme stack. The evidence is unusually direct for a public inference: the site uses WordPress-style /category/ archives; it exposes monthly archives like /2026/05/; the Privacy Policy repeatedly refers to “the theme”; and an empty category page publicly displays admin-oriented copy saying, “Add posts or use the optional draft seed content tool from Appearance,” where “Appearance” is classic WordPress admin terminology.

That likely means the current site can be overhauled either by cleaning up and hardening WordPress or by migrating to a static-first architecture while preserving content URLs and editorial concepts. The public materials do not provide enough evidence to confirm the exact host, CDN configuration, or plugin inventory, so those remain open questions. The site’s own privacy copy does, however, claim a notable privacy posture: no analytics, no tracking pixels, no external fonts, no CDN assets, and no unnecessary cookies by default in the theme.

Audience, positioning, and product strategy

Likely target personas

The site’s own wording implies at least five core personas.

The evidence for these personas is unusually strong because the site explicitly describes its intended reader pathways: people who care about AI harm, anonymous speech, metadata, records, corrections, lawful contact, or volunteering. The homepage’s wizard also shows 2IA thinking in user-need terms rather than purely in topic-taxonomy terms.

Recommended positioning

2IA should not position itself as a generic “blog,” “archive,” or “OSINT resource.” The strongest position is:

A rights-forward public-intelligence publication and civic toolkit for understanding and contesting surveillance, identity systems, records opacity, and algorithmic harm.

That wording matches the site’s own emphases on lawful public intelligence, civil liberties, records, correction, minimization, and accountability. It is also strategically better than broader “privacy” branding, because 2IA’s practical advantage is not merely “privacy awareness”; it is translating abstract power systems into accountable questions and lawful next steps.

Product model

I would rebuild 2IA around four product layers:

This is the architecture 2IA currently gestures toward but does not yet implement. The Research Archive already distinguishes issue hubs, investigations, policy analyses, guides, toolkits, case studies, campaigns, and updates. The overhaul should operationalize that taxonomy instead of merely describing it.

Product and experience audit

Information architecture and navigation

The current IA is directionally correct but operationally weak. The top-level nav is small and sensible: Home, Start Here, Research Archive, Methodology, Support, About. The site also carries a consistent secondary set of legal/trust navigation links such as Privacy Policy, Ethics, Public Records, Corrections, Newsletter, Lawful Contact, and Contact. That is a good baseline because it foregrounds trust.

The problem is that the nav promises a publication system that the site has not yet earned. “Research Archive” suggests a body of published work; the archive itself says there are no briefings. Category routes imply navigable topic depth; the category pages are empty. Search suggests discoverability; there is little published research to discover. This creates a form of information debt: the IA is larger than the corpus.

The immediate fix is to move from structure-first IA to corpus-first IA. In practice, that means hiding or reframing empty category/archive routes until each has at least one canonical hub and two to five real supporting pieces.

User flows and onboarding

2IA has the raw ingredients for several high-value user journeys, but those journeys are not yet tightened into short, reliable flows.

The best current onboarding asset is Start Here, which breaks the audience into paths such as “If You Care About AI Harm,” “If You Want Something Useful Now,” and “If You Want To Trust The Work.” That is the right instinct. The homepage’s local-only wizard is also strategically smart because it turns broad concern into one of a few actionable civic routes, and explicitly says it is not a secure drop, legal advice, or reporting portal.

What is missing is progressive disclosure. New readers currently meet long blocks of high-density manifesto text before they reach a clear outcome. For launch, 2IA needs three fully-designed first-run journeys:

1. I need help now → identify system → records/correction/appeal path → printable checklist.
2. I want to learn the issue → topic hub → glossary → cases → further reading.
3. I want to trust or support the work → methodology → corrections → privacy promise → support/volunteer.

Right now those flows exist mostly as text, not as productized navigation.

Search and discovery

Search exists across the site, but search value is currently low because the archive contains no published briefings. The site repeatedly prompts readers to “Search 2IA briefings,” while the archive states that no briefings have been published yet. Discovery also suffers because the visible topic archives are empty.

This should be overhauled into a three-part discovery system:

• Structured search for all articles, guides, records templates, corrections, and laws/policies.
• Topic hubs and concept pages that work even before the archive is large.
• Related-content graph driven by entities such as vendor, agency, jurisdiction, data type, rights at issue, and action type.

The benchmark here is not generic blog search. It is the layered discoverability seen in LessWrong’s Concepts, Library, All Posts, Sequences, and community views, along with the AI Alignment Forum’s narrower topic-specific structure. LessWrong pairs broad feeds with concept pages and curated sequences; the AI Alignment Forum narrows that model for a more specialized audience.

Community features and moderation

Today, 2IA has almost no visible community layer. Its Privacy Policy says comments are closed by default; the site discusses hypothetical forms, newsletters, and plugins as future additions that would need privacy review; and the Volunteer page describes contribution roles without exposing an actual intake workflow.

That is a perfectly defensible pre-launch posture. But if 2IA wants to become a more powerful resource, it should add community in a deliberately bounded way rather than as a bolt-on comment box. The right model is separation of concerns:

• the canonical knowledge layer should remain editorially controlled;
• the discussion layer should live in a forum or Q&A space with moderation, reputation, and escalation tools;
• the contributor layer should use submission and review workflows, not free-form public comment threads.

LessWrong and the AI Alignment Forum show how a serious knowledge community can combine discussion, curation, event/community features, moderation, and reader reputation. LessWrong’s FAQ describes a split moderation system, karma thresholds, author-level moderation policies, team moderation, temporary bans, thread locks, and moderation logs; its site also supports sequences, concepts, events, and community views. Discourse adds a more general-purpose community operating system: trust levels, PMs, groups, plugins, AI-assisted moderation, admin health dashboards, and full data export/self-hosting options.

Accessibility, privacy, security, SEO, and metadata

2IA shows some promising accessibility and privacy signals. Public pages include a Skip to content link; the homepage exposes a no-script fallback for its local-only routing tool; and the site’s Privacy Policy states that the theme does not add analytics, tracking pixels, external fonts, CDN assets, or unnecessary cookies by default. Those are unusually strong signals for a small site.

Still, a true WCAG review cannot be inferred from those positives alone. WCAG 2.2 is the current W3C Recommendation, and it is organized around the principles that content be perceivable, operable, understandable, and robust. 2IA should therefore treat compliance as a formal workstream, not as a byproduct of being text-heavy. In practice, that means testing contrast, keyboard order, focus visibility, heading structure, link purpose, error states, form labels, motion/reduced-motion behavior, and reading load on long pages.

SEO is currently one of the clearest weak points. The public search result showing “ArcSecs.com – Rethinking Gravity and Light” for 2ia.org indicates either stale metadata, a domain-history residue, or a serious indexing/configuration problem. Combined with empty archive pages and no published briefings, that means 2IA is currently invisible or confusing at the exact moment when stronger discovery should matter most.

My recommended standard is:

• WCAG 2.2 AA as the launch accessibility target.
• Search-engine cleanup before growth: canonical titles, descriptions, Open Graph/Twitter cards, author/date metadata, article schema, correction/update markup, XML sitemap, and removal or noindex of empty routes.
• Security/privacy hardening by default: CSP, strict permissions policy, dependency review, backup/restore drills, disclosure policy, role-based access, and audit trails for editorial changes.

Benchmarking and recommended architecture

What good comparable platforms do that 2IA should learn from

Recommended technical direction

My recommendation is not a total reinvention. It is a hybrid architecture built around three principles that already match 2IA’s public values:

• privacy-first by default;
• editorial canon separate from chatter;
• structured, queryable knowledge rather than blog chronology alone.

The most effective target architecture is:

• a static-first public site for speed, privacy, and tight editorial control;
• a structured CMS for articles, hubs, guides, tools, laws, vendors, agencies, corrections, and entities;
• a dedicated discussion/community layer for comments, Q&A, contributor coordination, and moderation;
• privacy-preserving analytics and server-side search/discovery.

Discourse is especially attractive for the community layer because its official materials emphasize moderation tools, PMs, groups, plugins, admin monitoring, ownership of data, exportability, self-hosting, and open source, all of which fit 2IA’s civil-libertarian/privacy posture. For deployment and developer workflow, Vercel’s official pricing page shows a free Hobby tier and a Pro tier at $20/month, with preview deploys and managed infrastructure features; Supabase’s public product positioning centers on Postgres, Authentication, instant APIs, Edge Functions, Storage, and Realtime, which makes it a good fit for the structured-data and workflow side if the team wants a fast managed backend.

Stack options, tradeoffs, and estimated costs

The cost figures below are planning estimates, not quotes. They assume a modest early-stage footprint, under roughly low-to-mid six figures of monthly pageviews, a small contributor base, and no heavy video/media workloads.

My recommendation is the hybrid option. It is the only option that simultaneously supports: a clean public publication, a strong correction and records workflow, structured entities and taxonomies, a real contributor layer, and future forum/Q&A expansion without polluting the canonical resource library.

Proposed new site architecture

flowchart LR
    A[Readers] --> B[Public Site]
    C[Contributors] --> D[Contributor Intake]
    E[Editors] --> F[Editorial Workflow]

    subgraph Public Experience
        B --> G[Topic Hubs]
        B --> H[Guides and Toolkits]
        B --> I[Investigations and Case Studies]
        B --> J[Records Action Center]
        B --> K[Corrections and Updates]
        B --> L[Search and Entity Explorer]
    end

    subgraph Publishing Core
        F --> M[Structured CMS]
        M --> N[Content API]
        M --> O[Media and Document Store]
        F --> P[Fact-check and Minimization Review]
        P --> Q[Publish]
    end

    subgraph Community Layer
        R[Forum and Q&A]
        S[Moderation Queue]
        T[Contributor Workspace]
    end

    subgraph Shared Services
        U[Auth and SSO]
        V[Search Index]
        W[Privacy-first Analytics]
        X[Postgres]
    end

    D --> T
    T --> F
    Q --> B
    N --> V
    L --> V
    R --> S
    B --> U
    R --> U
    M --> X
    B --> W
    R --> W

The key architectural principle is separation: canonical knowledge is published through editorial workflow; discussion happens beside it, not inside it.

Governance, community, sustainability, and editorial operations

Governance and editorial process

2IA already has unusually mature governance language for a site at this stage. Methodology names source hierarchy, confidence labels, AI-use disclosure, minimization, correction, right of reply, and review before publication. Corrections and Right of Reply says a project like this should make repairs visible and summarized. Ethics and Civil Liberties makes privacy, truthfulness, minimization, due process, and lawful pressure central.

The next step is to turn those principles into an editorial operating system. I recommend the following minimum governance structure:

This is not imported ideology. It is the site’s own methodology made operational.

Moderation policy outline

The site currently rejects harassment, deception, intrusion, doxxing paths, automation floods, and misuse guidance, and says comments are closed by default. That gives 2IA a strong values baseline. What it lacks is a visible moderation framework for the community layer it says it wants to build.

I would adopt a moderation policy with these elements:

This follows the spirit of 2IA’s own ethics pages and borrows proven mechanisms from LessWrong and Discourse, both of which expose moderation powers, escalation tools, and explicit governance.

Contributor onboarding flow

The current Volunteer page names useful roles but stops before a real workflow. The rebuild should treat contributors as a governed pipeline, not an inbox.

A good onboarding flow is:

Interest form → privacy notice and role selection → trial contribution → editor feedback → scoped permissions → ongoing review cadence → publish/credit/correction accountability

Concretely:

1. Expression of interest with minimal data collection and role options such as research, editing, design, accessibility, translation, records tracking, legal review, or technical maintenance.
2. Contributor policy pack covering privacy, minimization, evidence handling, right of reply, and “no vigilante work.”
3. Trial task matched to role, such as source annotation, accessibility QA, timeline extraction, or template drafting.
4. Editorial review with rubric-based feedback.
5. Scoped access to CMS/forum/workspace based on trust and demonstrated competence.
6. Publishing and correction accountability, with attribution rules and change tracking.

Sample content templates

2IA’s best future advantage will come from making every article type structurally legible. The current archive already names useful publication lanes; the templates below translate those lanes into repeatable page architecture.

Monetization and sustainability

2IA’s Support and Newsletter pages are philosophically well aligned: they explicitly reject tracker-heavy growth hacks, list-selling, and fake urgency, and they define support as funding evidence-led work and privacy-respecting infrastructure. That is the right starting posture.

I would recommend a four-stream sustainability model with a clear editorial firewall:

• Reader support: recurring donations and one-time gifts.
• Member program: early briefings, contributor salons, behind-the-scenes research notes, not paywalled core civic resources.
• Institutional grants: journalism, civil-liberties, digital-rights, transparency, and public-interest-tech funders.
• Training/services: paid workshops on records requests, correction workflows, procurement literacy, privacy-aware publication, and source review.

Avoid ad-tech, sponsored surveillance-tech content, and any revenue model that compromises the privacy promise or creates pressure to sensationalize.

Analytics and KPIs

Because the privacy policy says the theme avoids analytics and trackers by default, 2IA likely has little or no actionable product telemetry today. That is understandable, but it means the team cannot manage what it cannot see.

The solution is privacy-preserving analytics, not surveillance analytics. Measure the publication, not the person. I recommend a KPI system around six domains:

Roadmap, ownership, and success metrics

Recommended sequencing

The most important sequencing rule is: do not launch community scale before editorial spine. First build the canon, then the forum.

gantt
    title 2IA overhaul roadmap
    dateFormat  YYYY-MM-DD
    axisFormat  %b %Y

    section Foundation
    Positioning, IA, and content model        :a1, 2026-06-01, 2026-07-31
    Design system and CMS setup               :a2, 2026-07-01, 2026-09-30
    Metadata cleanup and route consolidation  :a3, 2026-07-15, 2026-09-15
    Canonical hub and guide migration         :a4, 2026-08-01, 2026-10-31

    section Launch
    MVP public site launch                    :b1, 2026-10-01, 2026-11-30
    Search, taxonomy, and entity pages        :b2, 2026-10-15, 2027-01-31
    Analytics, corrections log, newsletter    :b3, 2026-10-15, 2026-12-15

    section Community
    Contributor onboarding and pilot forum    :c1, 2026-11-15, 2027-02-28
    Moderation tooling and governance         :c2, 2026-12-01, 2027-03-31

    section Growth
    Investigation cadence and case studies    :d1, 2027-02-01, 2027-06-30
    Records toolkit and jurisdiction packs    :d2, 2027-03-01, 2027-07-31
    Membership and grants program             :d3, 2027-05-01, 2027-09-30

    section Scale
    Advanced explainers and data/API layer    :e1, 2027-08-01, 2027-11-30

Prioritized action plan

Recommended team shape

At minimum, the overhaul needs these role owners:

• Editor-in-chief for editorial standards, correction policy, and publication cadence
• Product lead for IA, onboarding, KPIs, and roadmap coordination
• Tech lead for CMS/frontend/search/auth/hosting decisions
• Research editor for topic hubs, investigations, templates, and sourcing discipline
• Community lead for forum launch, moderation, contributor onboarding, and events
• Legal/privacy reviewer for minimization, right of reply, and high-risk pages

This does not require a large organization immediately, but it does require clear ownership.

Open questions and limitations

A few important items remain unverified from public materials alone:

• Exact hosting, DNS, CDN, and plugin inventory were not directly confirmed from primary official infrastructure records during this audit.
• Actual traffic and engagement are unknown because there is no visible analytics layer in the reviewed materials.
• Live performance metrics such as Core Web Vitals were not available from primary sources in the audited materials.
• Accessibility conformance cannot be certified without full manual and automated WCAG testing, even though the site shows several promising baseline signals.
• Donation/newsletter operations appear conceptually planned, but I could not verify an actively deployed production workflow from the public pages reviewed.

Those uncertainties do not change the central conclusion. The site’s strategic problem is already clear from the public corpus: 2IA has a strong doctrine and weak productization. The overhaul should focus on operationalizing what the site already claims to be.