Skip to content
wiki.fftac.org

Architecture

**Site relevance:** 2IA.org

**Memory type:** UAI memory file

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

**Size:** 2.3 KB

Summary

Mature Public-Interest Editorial Posture

Source Headings

  • Architecture
  • Mature Public-Interest Editorial Posture
  • Layers
  • Separation Rules

Source Preview

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

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

# Architecture

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


## Layers

- Presentation and site-specific behavior: `wp-content/themes/twoia-intelligence/`.
- Theme assets: `wp-content/themes/twoia-intelligence/assets/`.
- Theme includes: `wp-content/themes/twoia-intelligence/inc/`.
- Template partials: `wp-content/themes/twoia-intelligence/template-parts/`.
- Publication system: `inc/content-types.php` owns 2IA editorial post types and research archive lanes; `inc/editorial-meta.php` owns confidence, provenance, AI-use, right-of-reply, minimization, and correction metadata.
- WordPress Studio/runtime layer: root WordPress files, `wp-admin/`, `wp-includes/`, and Studio-managed runtime files.
- Memory layer: root `AGENTS.md`, `readme.human`, `.uai/`, `agent-file-handoff/`, and Wiki.FFTAC.org long memory.

## Separation Rules

- Theme code owns the public research surface, templates, assets, Customizer settings, seed-content helper, and responsive presentation.
- Editorial content types should stay aligned across registration, search inclusion, route archive queries, schema, Open Graph type selection, single templates, and card metadata.
- WordPress core and third-party/default plugin files are not project-owned application code.
- Wiki.FFTAC.org long memory is evidence storage, not runtime code or public site content by itself.