Decisions - Source Excerpt 01 - Decisions

Back to Decisions

Summary

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

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

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

# Decisions

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

- Use UAIX Project Handoff for short-term repository memory: `AGENTS.md`, `readme.human`, `.uai/*.uai`, and `agent-file-handoff/`.
- Route reviewed long-term memory to `E:/Source/WP-FFTAC/Wiki.FFTAC.org/wiki/projects/2ia.org/index.md`.
- Treat `wp-content/themes/twoia-intelligence/` as the owned implementation surface for 2IA.org.
- Keep the public site libertarian, civil-liberties-centered, public-accountability-oriented, mature-audience, and open to controversial lawful analysis while separating analysis from operational misuse guidance.
- Processed handoff files should leave active `Content/` and `Improvement/` after disposition; continued editorial value belongs in Archive plus Wiki.FFTAC.org long memory, not in active intake.
- Production packaging should fail on unresolved active handoff intake through `scripts/audit-agent-file-handoff.ps1`.
- The 2026-05-16 Improvement batch is not a public playbook. Publishable material may inform high-level privacy literacy, metadata/identity analysis, false-positive cautions, and lawful public-contact norms; unsafe operational details stay archived and unpromoted.
- The "hello signal" is an editorial metaphor for identity, visibility, consent, and metadata. It is not permission to trigger monitoring systems, contact agencies in bulk, generate suspicious traffic, trip sensors, or provoke law-enforcement/intelligence workflows.
- 2IA.org should never publish operational trigger lists, selector recipes, packet/header crafting, sensor activation methods, WAF/payload examples, endpoint-trigger examples, radio signaling instructions, or automated agency-contact workflows.
- Ethical information operations coverage must stay defensive and analytical: media literacy, transparency, oversight, non-deception, harm minimization, accountability, and respect for autonomy.
- Core public routes are protected by theme-level fallback pages so the default navigation and hero CTAs do not 404 on fresh, unseeded, or partially seeded installs. A published WordPress page with the same slug takes precedence over the fallback.
- The seed-content tool should create only missing draft starter pages/posts. It should not be routed away by a default `Sample Page`, should not duplicate existing content, and should not auto-publish.
- Lawful-intelligence source material may inform high-level governance language: lawful purpose, minimization, consent/notice, sensitivity labels, access control, evidence-care, retention, deletion, oversight, anti-impersonation, and lawful contribution channels. It must not become an OSINT tool playbook, recon workflow, unlicensed private-investigation guide, stalking/trespass aid, or operational reporting template.
- OSINT source material may inform high-level public verification language: lawful purpose, minimization, source context, corroboration, confidence labels, AI caution, redaction, retention, and correction paths. It must not become a tool playbook, recon workflow, OPSEC/counter-detection guide, social-media profiling recipe, dark-web guide, or private-investigation template.
- Anonymous/hacktivism source material may inform high-level identity, attribution, media, legal, and accountability analysis. It must not teach attack methods, target selection, data leaks, doxxing, disruption tactics, evasion, or unlawful participation.
- Psychological-warfare source material may inform defensive influence literacy: propaganda/misinformation/disinformation distinctions, synthetic-media authenticity risk, provenance, fact checking, transparency, correction paths, and public resilience. It must not become influence-campaign planning, persuasion targeting, deception scripts, intimidation tactics, astroturfing, bot coordination, coercive microtargeting, or psychological manipulation guidance.
- Grey-hat source material may inform only legal/ethical boundary cautions such as authorization, safe harbor, transparency, auditability, and the risk of ambiguous conduct. It must not teach exploit methods, scanning/probing, detection/evasion, or operational cyber workflows.
- The provided `2IA_Home_Page_Top_Right.png` was selected as the homepage hero image and copied into the deployable theme asset path `wp-content/themes/twoia-intelligence/assets/images/2ia-home-page-top-right.png`; handoff copies should still be archived after disposition.
- Public pages should be proud and explicit about American-style civil liberties: speech, press, petition, assembly, privacy, due process, anonymity, public records, and accountability. That posture must remain lawful, non-coercive, non-deceptive, and non-operational.
- Source-controlled public route content is protected by `tools/Test-2IAContentRoutes.ps1` and `tools/2ia-route-content-manifest.json`; route edits should update the manifest and run the test so pages do not silently disappear or thin out.
- Every required public route should carry the sitewide key phrase `Lawful public intelligence for human freedom.` plus `Proudly Civil-Libertarian`. The test manifest enforces those phrases across all routes.
- Published WordPress pages may still lead route content, but if a route page is thin or missing the key phrase, the theme appends the source-controlled research backbone so report-backed content remains visible.
- The 2026-05-16 publication-system batch should be treated as a strategic direction: 2IA needs trust pages, issue hubs, public-records/FOIA utility, methodology, corrections/right-of-reply, support/newsletter/volunteer pathways, and publication machinery, not only concept pages.
- Guardrails should be applied as review-and-routing standards. Adult public-interest topics about human rights, surveillance, state power, labor coercion, censorship pressure, and algorithmic control remain in scope when sourced, lawful, minimized, confidence-labeled, and correctable.
- Guardrails should still route away step-by-step public guidance that enables misuse: operational OSINT playbooks, attack-surface mapping, skip tracing, dark-web/tool workflows, OPSEC/counter-detection, hacking, evasion, exploit detail, doxxing, target selection, coercive influence, deception scripts, and mass-contact automation.
- The theme should hide the default WordPress `Hello world!` placeholder from public briefing lists so shallow default content does not damage publication trust.
- Public route regression may use per-route rendered-character thresholds in the manifest for smaller trust pages while keeping broad dossier routes covered by the global threshold.
- 2IA should use custom editorial content types as publication lanes, not only standard posts: issue hubs, investigations, policy analysis, guides, toolkits, case studies, campaigns, and updates.
- Editorial review metadata is part of the publication trust model. Confidence, provenance, AI assistance, right of reply, minimization/redaction, and correction history should stay easy to edit and visible on public article pages when provided.
- Article search, archive queries, post cards, bylines, Open Graph metadata, and JSON-LD schema should include the 2IA editorial post types wherever they behave as public articles.
- Duplicate follow-up reports should be archived and logged, but repeated owner emphasis can justify deeper implementation of already reviewed safe recommendations.
- The organization/resource directory is part of the public route system, not a loose future roadmap note. `/organizations/` should remain source-controlled, manifest-tested, and verification-first until a dedicated directory content type exists.
- Organization entries should distinguish verified help resources, candidate leads, stale leads, historical entries, controversial/high-risk entries, duplicates, and needs-records states. Do not present exhaustive generated lists as verified current facts without source dates and official confirmation.