Skip to content
wiki.fftac.org

Progress - Source Excerpt 01 - Progress

Back to Progress

Summary

This source excerpt begins near Progress and preserves the surrounding evidence from 2IA.org/.uai/progress.uai.

**Source path:** 2IA.org/.uai/progress.uai

---
uai: "1.0"
type: progress
title: "2IA.org Progress"
created: "2026-05-16"
updated: "2026-05-18"
status: active
source: "https://uaix.org/en-us/tools/ai-memory-package-wizard/"
---

# Progress

## Mature Public-Interest Editorial Posture

2IA.org is built for mature readers who can handle controversial public-interest material. The site should not soften, euphemize, or hide hard topics merely because they involve state power, surveillance, propaganda, coercion, war, intelligence culture, organized abuse, corruption, censorship, civil disorder, or institutional failure.

Use a libertarian, civil-liberties-first standard: publish lawful, source-aware analysis by default. Withhold or route away only content that would meaningfully help a reader commit abuse, evade accountability, target real people, or intrude on systems. Controversial subject matter is not a reason to suppress a topic. The preferred response is context, evidence, confidence labels, right of reply, redaction when needed, and clear separation between analysis and operational instruction.


## Current State

- WordPress Studio site is present under `2IA.org/`.
- Custom theme `twoia-intelligence` is present with templates, assets, Customizer settings, seed-content helper, SEO/schema support, and package README.
- UAIX Project Handoff, Agent File Handoff buckets, and Wiki.FFTAC.org long-memory routing were initialized on 2026-05-16.
- The theme README states that the project is privacy-first and does not load Bootstrap, jQuery, external fonts, CDN assets, analytics scripts, tracking pixels, or external embeds by default.
- The public editorial boundary is education, law, ethics, history, oversight, public accountability, and controversial civil-liberties analysis for mature readers, while not publishing step-by-step abuse playbooks.
- The 2026-05-16 ten-file Improvement batch was reviewed. Publishable concepts were promoted into hot memory and Wiki.FFTAC.org; operational, manipulative, mass-contact, and sensor-triggering material was routed away from step-by-step public guidance and archived.
- The 2026-05-16 two-file lawful-intelligence Improvement batch was reviewed. Safe governance concepts informed source-controlled fallback pages for core public routes, seed-tool repair for missing starter drafts, README updates, and hot/long memory; operational OSINT/tooling and unlicensed-investigation detail was routed away from step-by-step public guidance and archived.
- Core routes such as `/what-they-look-for/`, `/two-identities/`, `/research-archive/`, `/about/`, `/ethics-and-civil-liberties/`, and `/lawful-contact/` now render theme fallback pages when no published WordPress page exists, preventing default-navigation 404s on fresh or unseeded installs.
- The 2026-05-16 six-file OSINT and Anonymous Improvement batch was reviewed. Safe high-level OSINT governance and Anonymous/hacktivism identity analysis informed new homepage sections, fallback routes `/open-source-intelligence/` and `/anonymous-hacktivist-collective/`, seed draft pages/categories, README updates, and hot/long memory; operational OSINT playbooks, OPSEC/counter-detection, attack methods, doxxing, disruption, evasion, and unlawful participation guidance was routed away from step-by-step public guidance and archived.
- Virtual fallback routes now return 200 without pretending to be real singular WordPress posts, avoiding core `post-template.php` warnings when no published page object exists.
- The 2026-05-16 homepage and psychological-warfare batch was reviewed. The selected hazard-sign image was copied into deployable theme assets and used in the homepage hero; a safe psychological-warfare/influence-literacy homepage section, `/psychological-warfare/` fallback route, seed page/category/post, README updates, and hot/long memory were added. Influence-campaign planning, targeting, deception, astroturfing, bot coordination, coercive microtargeting, hacking/scanning/exploit/evasion detail, and unlawful participation guidance was routed away from step-by-step public guidance and archived.
- Source-controlled fallback pages were expanded with much more reviewed report material while preserving the public safety boundary: OSINT discipline/source volatility, Anonymous history and attribution caution, psychological-warfare literacy, metadata/AI governance, false-positive redress, lawful public contact, public-records accountability, and proud civil-libertarian framing.
- Added `tools/Test-2IAContentRoutes.ps1` and `tools/2ia-route-content-manifest.json` to regression-test the homepage and all source-controlled public fallback routes for HTTP 200, required content phrases, and absence of PHP diagnostic text.
- Expanded source-controlled route pages again with additional safe report-backed material, added the sitewide key phrase `Lawful public intelligence for human freedom.`, and made thin published pages receive the source-controlled research backbone when they lack required material.
- Strengthened `tools/Test-2IAContentRoutes.ps1` with static source inventory coverage, a manifest-to-virtual-page comparison, sitewide phrase checks, and `-StaticOnly` mode. Local route test passed for 18 routes at `http://localhost:8904/` after the change.
- Expanded the public route corpus again with a rights-forward civic-power layer: procurement scrutiny, public records leverage, data-broker accountability, AI due process, false-positive repair, anonymity and assembly, metadata as relationship mapping, and lawful pressure through records, testimony, comments, journalism, and correction.
- Reworked source-backed public pages into a denser dossier-card layout so 2IA pages read like substantive archives instead of oversized warning panels. The homepage now includes a protected `Freedom dossiers` section with procurement, false positives, data brokers, AI due process, anonymity, and public-records leverage.
- Replaced prominent "what this does not do" homepage and route-page copy with positive civil-liberties operating standards while keeping the hard boundary against misuse guidance intact.
- Reviewed the 2026-05-16 four-file publication-system and guardrail-calibration Improvement batch. Safe strategic material was applied into trust-page routes, methodology/corrections/public-records/support pathways, homepage CTA cleanup, navigation, route regression coverage, and hot/long memory; operational OSINT, cyber, skip-tracing, evasion, doxxing, coercive influence, and unverified current-crisis public guidance was routed away.
- Added source-controlled fallback routes for `/start-here/`, `/methodology/`, `/public-records-and-foia/`, `/support/`, `/newsletter/`, `/volunteer/`, and `/corrections-and-right-of-reply/`.
- Updated homepage defaults away from pseudo-institutional "International Intelligence Apparatus" language and toward a clearer civil-liberties publication posture with Start Here and Methodology CTAs.
- Replaced the public newsletter placeholder block with reader pathways for Newsletter, Support, and Volunteer, framed around privacy-respecting publication infrastructure.
- Added filtering so the default WordPress `Hello world!` placeholder post does not appear as a public briefing on the homepage or virtual research archive.
- Extended `tools/2ia-route-content-manifest.json` to 25 routes and updated `tools/Test-2IAContentRoutes.ps1` with per-route rendered-character thresholds. Static route regression passed for 25 routes.
- Reviewed the 2026-05-16 publication-system follow-up drop. The two reports were duplicate SHA256 matches of previously reviewed publication-system sources, so they were archived as duplicate-context follow-up under `agent-file-handoff/Archive/2026-05-16-publication-system-followup/`.
- Used the duplicate follow-up as an owner signal to deepen the publication-system implementation: added editorial post types for issue hubs, investigations, policy analysis, guides, toolkits, case studies, campaigns, and updates.
- Added a 2IA Editorial Review metadata panel for confidence labels, source notes, AI-use disclosure, right-of-reply status, minimization/redaction notes, and correction/update logs, with public rendering on single research content when fields are populated.
- Expanded article/archive infrastructure so editorial content types appear in frontend search, briefing cards show the content format, the virtual research archive displays publication-lane cards, and Article/WebPage/CollectionPage schema plus Open Graph metadata cover the new surfaces.
- Follow-up verification on 2026-05-16: `tools/Test-2IAContentRoutes.ps1 -BaseUrl http://localhost:8904` passed for all 25 protected routes, `tools/2ia-route-content-manifest.json` parsed with 25 routes, and `..\scripts\audit-agent-file-handoff.ps1 -FailOnActive -FailOnMissingSetup` reported all workspace intake buckets clear. PHP syntax lint could not run because `php` is unavailable on PATH.