2Ia Readme - Source Excerpt 01 - 2IA.org Human Briefing

Back to 2Ia Readme

Summary

This source excerpt begins near 2IA.org Human Briefing and preserves the surrounding evidence from 2IA.org/readme.human.

**Source path:** 2IA.org/readme.human

# 2IA.org Human Briefing

Updated: 2026-05-17

## 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.

This file is for humans working with AI on this repository. It explains what the AI sees, protects, and needs clarified. It does not override `AGENTS.md`, `.uai/constraints.uai`, system instructions, repository rules, laws, policies, or the current human request. It does clarify that the intended website is for mature readers and should not censor controversial public-interest subject matter merely because it is uncomfortable.

## What You Need To Know

- 2IA.org is a WordPress Studio site using the custom `twoia-intelligence` theme for Two Identities of Anonymous.
- The AI reads `AGENTS.md` first, then this file, then the `.uai` files listed under Loaded Context.
- Short-term working memory lives in `AGENTS.md`, `readme.human`, `.uai/`, and `agent-file-handoff/`, following the UAIX AI Memory Package Wizard at `https://uaix.org/en-us/tools/ai-memory-package-wizard/`.
- Long-term reviewed memory routes to `E:/Source/WP-FFTAC/Wiki.FFTAC.org/` and public `wiki.fftac.org`, following the LLMWikis setup wizard at `https://llmwikis.org/tools/llm-wiki-setup-wizard/`.
- Processed handoff files should not remain in active `Content/` or `Improvement/`; they should be archived after disposition and preserved through Wiki.FFTAC.org when durable.
- Production packaging runs a handoff audit and should fail if active intake is unresolved.
- The working tree may already contain unrelated user or runtime changes. The AI should inspect before editing and should not revert work it did not create unless explicitly asked.

## Things The AI Will Defend

- Secrets, credentials, private keys, tokens, customer data, and private material.
- WordPress core, vendor code, bundled third-party assets, generated runtime artifacts, and Studio-managed files.
- The editorial boundary between public education and operational misuse.
- Evidence boundaries for surveillance, AI analysis, identity, civil-liberties, lawful contact, and public-accountability claims.
- Targeted verification before claiming that code, packaging, or release behavior is ready.

## Things Humans Should Make Explicit

- Whether the task may touch production, public content, legal/security/support language, privacy policy, comments, forms, or irreversible data.
- Whether package ZIPs should be rebuilt or uploaded.
- Whether durable hot memory and Wiki.FFTAC.org long memory should be updated after the change.
- Which checks are required before the work is considered done.
- Whether dropped files in `agent-file-handoff/Content/` or `agent-file-handoff/Improvement/` should be applied, deferred, or ignored.
- Whether any surveillance, agency, or security-related examples should be public, internal-only, summarized without links, or routed away.

## Current Intake Note

The 2026-05-16 ten-file Improvement batch has been reviewed and archived. Its safe value is high-level surveillance literacy, metadata/identity analysis, civil-liberties framing, false-positive awareness, lawful public-contact norms, and defensive media literacy. Its unsafe or inappropriate value is routed away from step-by-step public guidance: trigger keywords, selectors, packet/header crafting, monitoring-system signaling, mass agency contact automation, sensor activation or bypass methods, stress testing, psychological manipulation, and coercive influence.

The 2026-05-16 lawful-intelligence Improvement batch has also been reviewed and archived. Its safe value is high-level governance: lawful purpose, minimization, consent/notice, sensitivity labels, access control, evidence-care, retention/deletion, oversight, anti-impersonation, and lawful contribution channels. Its unsafe or inappropriate value is routed away from step-by-step public guidance: operational OSINT/recon tooling, collection playbooks, stalking/trespass risk, impersonation, unlicensed private-investigation guidance, or detailed workflows that could enable misuse.

The 2026-05-16 OSINT and Anonymous Improvement batch has also been reviewed and archived. Its safe value is high-level OSINT governance and verification, plus Anonymous/hacktivism identity and accountability analysis. Its unsafe or inappropriate value is routed away from step-by-step public guidance: OSINT tool playbooks, OPSEC/counter-detection, recon workflows, social-media profiling steps, attack methods, target selection, doxxing, data-leak methods, disruption tactics, evasion, or unlawful participation guidance.

The 2026-05-16 homepage and psychological-warfare Improvement/Content batch has also been reviewed and archived. Its safe value is the provided homepage hazard-sign image, defensive influence literacy, propaganda/misinformation/disinformation distinctions, synthetic-media authenticity risk, source provenance, correction paths, and grey-hat/legal-boundary cautions. Its unsafe or inappropriate value is routed away from step-by-step public guidance: influence-campaign planning, persuasion targeting, deception scripts, intimidation, astroturfing, bot coordination, coercive microtargeting, hacking methods, exploit workflows, scanning, or evasion.

The default-navigation 404 on `/what-they-look-for/` was traced to missing published WordPress pages on an unseeded install. The theme now renders source-controlled fallback pages for required public routes when no published WordPress page exists; published editor-owned pages still take precedence.

The virtual fallback routes were expanded on 2026-05-16 with much more safe source-report material: OSINT discipline and source volatility, Anonymous history and attribution caution, influence literacy, metadata and AI governance, false-positive redress, lawful public contact, and an explicitly proud civil-libertarian posture. `tools/Test-2IAContentRoutes.ps1` now tests the homepage and all source-controlled public routes for HTTP 200, expected content phrases, and absence of PHP warning text.

The route guard was strengthened again on 2026-05-16. Every required route now carries the key phrase `Lawful public intelligence for human freedom.` plus `Proudly Civil-Libertarian`, and the test manifest enforces those phrases across all pages. The test also has `-StaticOnly` mode for no-server source coverage, and thin published pages receive a source-controlled research backbone so editor-owned pages cannot silently hide required report-backed content.

The 2026-05-16 publication-system and guardrail-calibration Improvement batch has also been reviewed and archived. Its safe value is the content-expansion blueprint, trust-page architecture, methodology/corrections workflow, public-records/FOIA pathway, support/newsletter/volunteer privacy model, OSINT user-needs synthesis, provenance/audit-trail emphasis, AI-as-assistant framing, and more direct adult civil-liberties language. The applied site change added source-controlled `/start-here/`, `/methodology/`, `/public-records-and-foia/`, `/support/`, `/newsletter/`, `/volunteer/`, and `/corrections-and-right-of-reply/` routes, cleaned homepage pathways, filtered the default `Hello world!` placeholder out of public briefing lists, and updated route regression coverage to 25 routes. Guardrails were recalibrated so hard public-interest topics remain in scope when sourced, lawful, minimized, and correctable; public guidance still blocks operational OSINT playbooks, attack-surface mapping, skip tracing, dark-web/tool workflows, OPSEC/counter-detection, evasion, exploit detail, doxxing, target selection, coercive influence, deception scripts, unverified current-crisis claims, and other misuse-enabling material.