Skip to content
wiki.fftac.org

Agents

**Site relevance:** 2IA.org

**Memory type:** reviewed source memory

**Source path:** 2IA.org/AGENTS.md

**Size:** 7.9 KB

Summary

Mature Public-Interest Editorial Posture

Source Headings

  • AGENTS
  • Mature Public-Interest Editorial Posture
  • Handoff Summary
  • Workspace Coordination
  • Loaded Context
  • Agent File Handoff
  • Required First Response
  • Read First
  • Current-State Boundaries
  • Safety And Editorial Rules
  • Editing Rules
  • Verification

Source Preview

This source file is short enough to preview directly on its source-memory page.

---
uaix: "1.0"
project: "2IA.org"
created: "2026-05-16"
updated: "2026-05-17"
status: active
---

# AGENTS

## 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 is the working guide for anyone modifying the 2IA.org WordPress Studio site.

## Handoff Summary

2IA.org is a WordPress Studio site using the custom `twoia-intelligence` theme. It is a mature-audience, privacy-first public-intelligence and civil-liberties research surface about communications surveillance, metadata, identity, AI analysis, false positives, lawful public understanding, oversight, and ethical information operations. Short-term memory lives in this repository's UAIX Project Handoff files; reviewed long-term memory routes to `E:/Source/WP-FFTAC/Wiki.FFTAC.org/`.

## Workspace Coordination

This repo is part of the `E:/Source/WP-FFTAC` multisite workspace. Before broad work, read `E:/Source/WP-FFTAC/workspace.uai` when the human names any known site/domain, when a request spans multiple sites, or when the current shell directory and requested target differ. Explicit site or domain names decide which handoff bundle to load.

Use the UAIX AI Memory Package Wizard at `https://uaix.org/en-us/tools/ai-memory-package-wizard/` for short-term AI Memory, Project Handoff, and Agent File Handoff setup guidance. Use the LLMWikis setup wizard at `https://llmwikis.org/tools/llm-wiki-setup-wizard/` when planning long-term LLM Wiki structure, pointing reviewed long-memory/cold-memory routing to `E:/Source/WP-FFTAC/Wiki.FFTAC.org/` and public discovery at `wiki.fftac.org` after source-site review.

## Loaded Context

@uai[.uai/context.uai]
@uai[.uai/stack.uai]
@uai[.uai/constraints.uai]
@uai[.uai/architecture.uai]
@uai[.uai/decisions.uai]
@uai[.uai/progress.uai]
@uai[.uai/test-plan.uai]
@uai[.uai/operations.uai]
@uai[.uai/style.uai]
@uai[.uai/file-handoff.uai]
@uai[.uai/intake-index.uai]
@uai[.uai/memory.uai]

## Agent File Handoff

At the start of broad work, inspect `agent-file-handoff/Content/` and `agent-file-handoff/Improvement/`, classify files sitting directly under `agent-file-handoff/`, ignore `agent-file-handoff/Archive/` unless the human explicitly names an archived file, and review `.uai/intake-index.uai` before unrelated edits.

Dropped files are local review inputs only. Use `.uai/file-handoff.uai` for active bucket, disposition, archive, Wiki.FFTAC.org long-memory, and trust-boundary rules. Reviewed files should leave active intake after the complete outcome is recorded unless the human explicitly keeps a named file active.

Production packaging runs the workspace handoff audit. Treat active files in `Content/` or `Improvement/` as a build blocker until reviewed, logged, and archived or deliberately deferred with a current owner reason.

## Required First Response

Before broad edits, the next AI should summarize the project and immediate task in 3-5 bullets, name which `.uai` files loaded and whether any were missing or contradictory, confirm constraints that require explicit human approval, name the files/routes/docs it expects to touch, and name the targeted checks it expects to run.

## Read First

1. [readme.human](readme.human)
2. [wp-content/themes/twoia-intelligence/README.md](wp-content/themes/twoia-intelligence/README.md)
3. [LLM_WIKI_MEMORY_PLAN.md](LLM_WIKI_MEMORY_PLAN.md) when work needs reviewed long-memory routing through Wiki.FFTAC.org.
4. [AGENT_FILE_HANDOFF_PLAN.md](AGENT_FILE_HANDOFF_PLAN.md) when work touches dropped-file intake.
5. [../scripts/audit-agent-file-handoff.ps1](../scripts/audit-agent-file-handoff.ps1) when checking whether active intake is clear before packaging.

For WordPress Studio instructions, see [STUDIO.md](STUDIO.md).

## Current-State Boundaries

- Most custom work belongs in `wp-content/themes/twoia-intelligence/`.
- The theme now includes site-specific editorial content types and editorial review metadata in `inc/content-types.php` and `inc/editorial-meta.php`; keep search, schema, archive lanes, and single-briefing templates aligned when changing that publication system.
- WordPress core, bundled WordPress themes, Studio runtime files, default plugins, and upstream plugin code are not owned application code unless a task explicitly says otherwise.
- Wiki.FFTAC.org long memory is background evidence until a reviewed fact is promoted into this site's hot handoff files, code, release note, or explicit owner decision.
- The worktree may already contain unrelated changes. Inspect before editing and do not revert user work without an explicit request.

## Safety And Editorial Rules

- Use a libertarian, mature-audience editorial default: controversial public-interest material belongs on the site when it is lawful, source-aware, and framed for civil-liberties understanding.
- Do not sanitize adult public-interest analysis into institutional blandness. State violence, detention, labor coercion, surveillance overreach, censorship pressure, public-records opacity, algorithmic control, human-rights abuses, intelligence history, propaganda, and institutional misconduct are in scope.
- Treat guardrails as editorial routing rules, not censorship or blanket topic bans: publishable, background-only, duplicate, deferred, rejected, or routed away from public playbooks for misuse risk.
- Strong claims need evidence, confidence labels, source context, minimization, correction paths, and right of reply where appropriate. The site may be blunt, skeptical, anti-authoritarian, and rights-forward without becoming reckless.
- Do not provide step-by-step instructions for hacking, evasion, sensor-triggering, network probing, unauthorized testing, mass agency contact automation, disinformation, harassment, impersonation, coercive influence, or psychological manipulation. Discuss these topics as controversial public issues when the treatment is analytical, historical, legal, journalistic, defensive, or accountability-focused.
- Do not publish operational recipes such as selector lists, trigger-keyword matrices, packet/header crafting, sensor activation, signal-tripping tactics, radio-signaling instructions, WAF/payload examples, endpoint-trigger examples, or workflows meant to provoke monitoring systems. It is acceptable to analyze that such mechanisms exist, why they matter, and how oversight should govern them.
- Discuss surveillance, metadata, AI analysis, intelligence practices, information operations, and public contact norms with legal, ethical, historical, and oversight framing.
- Use strong language when the evidence supports it, but avoid fearbait, unsupported certainty, scapegoating, real-person targeting, or instructions that would materially enable misuse.

## Editing Rules

- Prefer editing the custom theme for layout, templates, assets, styling, and site-specific copy.
- Do not edit `wp-admin`, `wp-includes`, bundled WordPress themes, vendor libraries, third-party license files, or WordPress Studio runtime artifacts unless there is a specific maintenance reason.
- Keep this handoff bundle concise; move bulky history and reviewed archive evidence to Wiki.FFTAC.org.

## Verification

After editing PHP files, run `php -l` against the files you changed when PHP is available. For handoff-only changes, verify that referenced files exist and that Wiki.FFTAC.org paths resolve.