Memory - Source Excerpt 02 - Working Memory Rules

Back to Memory

Summary

This source excerpt begins near Working Memory Rules and preserves the surrounding evidence from 2IA.org/.uai/memory.uai.

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

- The same calibration continues to block 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, mass-contact automation, and unverified current-crisis claims as public guidance.
- The theme filters the default WordPress `Hello world!` placeholder post out of homepage and virtual archive briefing lists so an unseeded install does not look like a live research archive with placeholder content.
- `tools/Test-2IAContentRoutes.ps1` now supports per-route `minimumRenderedCharacters` manifest overrides and static source coverage passes for 25 routes.
- On 2026-05-16, a publication-system follow-up drop repeated two already reviewed source reports. The duplicate hashes were `8E407A189858F25640B9B352B5317DB9BCAB103D5E37F4F42F171DB8BDBE418B` for `2IA.org Content Expansion Research Report.md` and `81DBC6150E064B5BB148E0CE312220BB8209E7106D71C7E7CFAF05AC11EDEF67` for `What People Want From OSINT Platforms.md`.
- The follow-up was treated as duplicate context plus a stronger owner signal, not new contradictory evidence. The files are archived under `agent-file-handoff/Archive/2026-05-16-publication-system-followup/`.
- The theme now includes a publication system with editorial post types for issue hubs, investigations, policy analysis, guides, toolkits, case studies, campaigns, and updates. These post types are searchable, categorized/tagged, REST-enabled, archive-enabled, and treated like public articles.
- The theme now includes public editorial-review metadata for articles: confidence label, source notes, AI-use disclosure, right-of-reply status, minimization/redaction notes, and correction/update logs. Public single pages render the ledger only when fields are populated.
- Research archive infrastructure now includes publication-lane cards, custom article post type queries, post-type format labels on cards and bylines, branded site names in document/SEO metadata, Article schema for editorial content types, and virtual WebPage/CollectionPage JSON-LD schema.
- On 2026-05-17, the civil-liberties overhaul intake was selectively applied. Public-safe value became stronger homepage positioning, Start Here reader maps, About/Methodology/Ethics/Public Records/Contact rewrites, Research Archive taxonomy, 12 launch article drafts, 6 issue hub outlines, 5 toolkit templates, dossier/corrections templates, SEO matrix, and a 90-day editorial calendar. Boundaries remain: no classified material, stolen data, exploit code, doxxing, personal-data dumps, target lists, evasion, sensor triggering, or operational misuse workflows.
- The unrelated copied handoff files in `agent-file-handoff/Content` were deleted per owner direction. The 19 useful current-source files from `Content/` and `Improvement/` were moved after processing to `agent-file-handoff/Archive/2026-05-17-civil-liberties-overhaul/`; active handoff buckets are clear except `.gitkeep`.
- The 2026-05-17 overhaul was verified with Studio WordPress eval, static route coverage, and a full 86-route live crawl at `http://localhost:8904/`. Standalone `php` remains unavailable on PATH.
- The next-level pass completed the public resource inventory promised by the overhaul: 13 issue hub outlines, 10 toolkit templates, and a source-class evidence matrix render in `/research-archive/`. The homepage also exposes an `Operating desk` with direct paths to reader maps, records packets, hubs/dossiers/toolkits, confidence labels, minimization standards, and corrections.
- Owner feedback on 2026-05-17 rejected the remaining route-generated copy as bullshit/process filler. The correction standard now is more direct: each route should name what is broken, who benefits, who gets hurt, the document to pull, and the demand. Avoid self-referential phrases about "routes", "cards", "reader pathways", or "lawful next steps" unless they are tied to a concrete institution, record, or action.
- The 2026-05-17 implementation response moved route-assembly/source-note material to bottom help disclosure, removed old detail sections such as `Where The Pressure Shows Up`, `What A Stronger Public Record Would Show`, `Reader Payoff`, and `Public Questions`, and recalibrated route tests so concrete failure/demand labels matter more than word-count volume. Current detail pages should lead with named systems, documents, beneficiaries, harms, demands, and correction conditions.
- The Who Cares Wizard is a homepage, local-only routing tool, not a legal-advice engine, crisis service, secure submission form, or external referral guarantee. It should keep asking short closed-ended questions, preserve privacy by default, and produce a concrete pressure map: responsible actors, helper actors, records to pull, first demand, boundaries, and links to 2IA routes plus verified external starting points.
- The processed Who Cares Wizard reports are archived under `agent-file-handoff/Archive/2026-05-17-who-cares-wizard/`; active `Improvement/` should remain clear except `.gitkeep`.
- The Organizations And Resource Directory is now a first-class source-controlled route at `/organizations/`. It is a verification-first civil-liberties resource map, not an endorsement list. It includes directory fields, starter sets to verify, civil-liberties organizations, OSINT/investigative groups, AI governance and safety organizations, digital-security/internet-freedom resources, public-records/transparency resources, controversial or historical hacktivist entries, state/country coverage, Alabama starter entries, verification before reliance, and 2IA name-collision disambiguation.
- Organization-directory entries should carry role, jurisdiction, official source, last-reviewed date, verification state, contact route, correction path, and risk note. Treat unverified organization lists as starter leads. Treat historical, hacktivist, leak, or leaderless-banner entries as context-heavy explainers with legal and attribution humility, not recommendations, recruitment paths, or operational guidance.
- The 2026-05-17 organizations-directory Improvement batch is archived under `agent-file-handoff/Archive/2026-05-17-organizations-directory-overhaul/`; active `Improvement/` should remain clear except `.gitkeep`.
- Owner correction on 2026-05-17: stop turning editorial instructions into public UI copy. Do not render phrases like "message worth sharing" or "public question to carry forward" as headings, labels, banners, or CTAs. If the product brief asks for a public question, render a real page-specific accountability question. If it asks for boundaries, write the concrete boundary only where it helps the reader. The public site should show the record, institution, risk, question, demand, or action directly instead of naming the internal content job.
- Route question panels should use distinct accountability questions per route or dossier, and tests should prevent stale meta-messaging and repeated question headings. Copy controls may say what they do, but prime public real estate must not become a checklist of internal instructions.
- Owner correction on 2026-05-18: wasted homepage hero space and public-facing instruction copy are release blockers. The current fix fills the hero right rail with useful record/action panels and adds rendered-text regression guards for internal planning phrases. Keep future public copy focused on records, institutions, risks, questions, demands, and actions; keep SEO matrices, article slates, internal-link labels, report synthesis labels, and editorial checklist language out of public UI.
- The 2026-05-18 top-navigation/density/public-copy handoff batch is archived under `agent-file-handoff/Archive/2026-05-18-top-navigation-density-public-copy/`; active `Content/` and `Improvement/` buckets should remain clear except `.gitkeep`.

## Working Memory Rules

- Use this file only for durable repository memory.
- Do not store secrets, credentials, private user data, or raw customer material here.
- Do not store claims that require external verification unless the source is named.
- If a fact changes, update or append a note instead of silently relying on private chat history.