Skip to content
wiki.fftac.org

Style

**Site relevance:** 2IA.org

**Memory type:** UAI memory file

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

**Size:** 4.3 KB

Summary

Mature Public-Interest Editorial Posture

Source Headings

  • Style
  • Mature Public-Interest Editorial Posture
  • Site Voice
  • Code Style
  • Libertarian Mature-Audience Voice

Source Preview

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

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

# Style

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


## Site Voice

- Use sober, source-led, civil-liberties-centered public language.
- Explain surveillance, metadata, AI analysis, false positives, identity, and public contact norms at a high level.
- Allow blunt, adult, controversial language when evidence supports it; avoid panic, harassment, scapegoating, operational harm, extremist recruitment, real-person targeting, and unsupported certainty.
- Keep the visual and editorial tone serious, modern, privacy-first, and public-interest oriented.
- Treat "hello" as a calm consent-and-visibility metaphor, not a provocation. Preferred copy should feel like public accountability and privacy literacy, not agency cosplay, threats, or surveillance theater.
- Acceptable brand language includes restrained lines such as "Your privacy, our promise" and "Two identities, one civic truth" when context fits.
- The voice may be direct, adult, and rights-forward when evidence carries the claim. Do not flatten state violence, detention, labor coercion, surveillance overreach, censorship pressure, public-records opacity, algorithmic control, or human-rights abuse into bland safety language.
- Controlled edge is allowed when it clarifies a sourced public issue. Avoid empty swagger, pseudo-intelligence cosplay, unsupported current claims, or rhetoric that outpaces evidence.
- Guardrail copy should describe review standards and lawful boundaries without making the site feel like a refusal page. Prefer positive standards: source notes, confidence labels, minimization, redaction, correction, right of reply, and human accountability.
- Publication-system copy should make format clear without jargon: issue hub, investigation, policy analysis, guide, toolkit, case study, campaign, or update. Editorial review ledgers should be plain, source-centered, and concise.
- Do not publish the editorial instruction as the public copy. If a brief says to provide a public question, ask the actual page-specific question; do not label the slot "public question." If a brief says to show boundaries, write the concrete boundary only where it helps the reader; do not turn internal process language into repeated headings.
- Avoid repeated meta-label clusters such as "message worth sharing," "public question to carry forward," or other self-referential phrases. High-priority copy must deliver substance directly: the record, institution, risk, question, or action, not a description of the copy's intended function.

## Code Style

- Follow the existing theme conventions in `wp-content/themes/twoia-intelligence/`.
- Keep PHP templates readable and local to the theme unless a future plugin boundary is established.
- Keep package-level notes brief and point durable memory to `.uai/` plus Wiki.FFTAC.org.


## Libertarian Mature-Audience Voice

- The site should feel adult, unsanitized, skeptical of concentrated power, and comfortable with controversy.
- Controversial content is a feature, not a defect, when it is grounded in evidence and public-interest purpose.
- Do not write like a compliance refusal page. Write like a serious civil-liberties publication: direct, careful, rights-forward, and unafraid of hard realities.
- Prefer "publish with context" over "omit": add source notes, confidence levels, dissenting views, correction language, and redaction rather than hiding a topic.