UAIX / AI Memory / Handoff
PsychologicalWar.org PSYOPS Realism, Information Architecture, Long-Term Memory, and Simulation Boundary Audit
Report summary
This synthesis is grounded in three kinds of material. First, I reviewed the twelve uploaded PSYOPS-related research files, which together cover terminology, doctrine, long-range history, organizational lifecycle, digital-era information operations, measurement, persuasion research, cross-cultural i
Key topics
- UAIX / AI Memory / Handoff
- UAIX
- AI Memory
- Handoff
- AI
- UAI
- Runtime
- Privacy
- Semantic Systems
Research provenance
For citation, use the report title and canonical URL. Archival presence does not establish authorship or promote report statements into portfolio evidence.
Source availability: 104 citation markers in the source export have no recoverable source links. Those markers are omitted from this reader; any supplied bibliography and ordinary links remain. Check the original sources before relying on the cited claims.
This page renders the archived Markdown as safe, formatted HTML. It is background research and does not become a portfolio claim without evidence review.
Full report
On this page
Scope and evidentiary posture
This synthesis is grounded in three kinds of material. First, I reviewed the twelve uploaded PSYOPS-related research files, which together cover terminology, doctrine, long-range history, organizational lifecycle, digital-era information operations, measurement, persuasion research, cross-cultural interpretation, architecture, and a broader casebook package. Those files provide the strongest evidence base for the domain-specific design work below.
Second, I directly inspected the public site as it currently presents itself on July 25, 2026. The homepage currently defines PsychologicalWar.org as an educational companion explaining “humans and authored NPCs” of RogueIntelligence.org and foregrounds People, Psychology, Roles, Ops, Dossiers, World, Systems, Models, and Research. Sampled public routes also show an existing labeling and provenance framework with page labels such as REAL-WORLD INTERPRETIVE, CLINICAL EDUCATION — NOT DIAGNOSIS, GAME MECHANIC, and FICTIONAL ROGUEINTELLIGENCE.ORG; visible review dates; source counts; confidence labels; and links to method/corrections.
Third, for unstable or load-bearing public terminology and safety boundaries, I cross-checked current primary or operator sources: EEAS on FIMI, NATO ACT on cognitive warfare, Meta on coordinated inauthentic behavior and AI labels, C2PA and OpenAI on provenance, Congress text for Smith-Mundt modernization, and Illinois law for SOPPA-style privacy constraints. Those sources matter because several uploaded drafts rely on the same doctrine and platform-policy vocabulary.
A critical limitation remains: no directly retrievable WIP.35 source tree, /docs directory, or protected .uai directory was available as a repository artifact in this session. Accordingly, direct findings below are strongest for the public site and the uploaded reports. Any recommendation about private memory structures, route registration, or source-tree organization is a design proposal unless and until the actual tree is made inspectable.
Current-state audit
The public site already has useful evidence-integrity machinery, but it is not yet unmistakably a psychological warfare history and literacy site. The central design problem is not lack of care; it is domain mismatch. The current public experience is cohesive around authored humans, NPCs, and game-adjacent analytical literacy, while the uploaded PSYOPS corpus is cohesive around historical, doctrinal, evidentiary, and non-operational treatment of psychological warfare. Those two systems are adjacent, but not yet legibly fused.
| Audit question | Verdict | Basis |
|---|---|---|
| Does the homepage explain what PsychologicalWar.org actually covers? | No | The homepage defines the site around “humans and authored NPCs” of RogueIntelligence.org, not psychological warfare as a historical or academic field. It does not lead with PSYOPS, propaganda, doctrine, artifacts, law, or case studies. |
| Does the current site distinguish psychological warfare, PSYOPS, IO, propaganda, public diplomacy, political warfare, MILDEC, strategic communication, disinformation, platform manipulation, cognitive warfare, and ordinary persuasion? | Not publicly enough | The distinctions are well developed in the upload set, especially the terminology atlas and comparative doctrine report, but they are not surfaced as a public gateway in the sampled navigation. |
| Is there a coherent historical path from early precedents to modern digital systems? | In the research corpus, yes; on the public site, no | The global history and casebook reports provide a strong chronological spine from antiquity to the digital era, but no sampled public route exposes that spine as the primary user journey. |
| Are major global regions represented proportionately to available evidence? | Partially | The intake is better than a purely US–UK corpus and includes Assyria, India, China, Peru, Haiti, Malaya, Kenya, Algeria, Vietnam, Soviet/East German material, and digital cases. Even so, coverage remains densest for the US, UK, NATO, Russia, and China, with thinner standalone treatment for Latin America, Africa beyond selected colonial cases, and the contemporary Global South. |
| Are case studies organized by era, actor, medium, audience, evidence, and outcome? | In draft form, yes; on the public site, not yet | The casebook and measurement reports do this explicitly. The public /case-files route is fictional RogueIntelligence material, not a historical PSYOPS casebook. |
| Does the site distinguish artifact existence, content status, coordination, identity, sponsor, intent, reach, and effect? | Conceptually yes, structurally incomplete | The homepage already separates role, access, operational function, sponsor, loyalty, and evidence at the person level; the digital-era report extends a rigorous eight-part analytic split for information operations. What is missing is a public psych-war artifact and claim system that applies those distinctions systematically. |
| Can readers see source origins, limitations, corrections, and currentness? | Partially yes | Sampled pages show source counts, confidence labels, currentness/review dates, independence indicators, and method/corrections links. But several pages also show independent corroboration of 0 or only 1 source, with specialist review still pending, so verbosity can exceed evidentiary maturity. |
| Are legal authority, oversight, human consequences, and remedy as visible as doctrine and tactics? | No | The lifecycle reports and IA audit emphasize legal advisers, parliamentary review, courts, complaint bodies, rights, and remedy. The sampled public navigation does not foreground a psych-war law, oversight, or rights-and-remedy pathway. |
| Does any content sensationalize mind control, brainwashing, bots, subliminal influence, or strategic omnipotence? | Mostly no, but boundaries need to be domain-explicit | The persuasion report rejects pseudo-scientific or overclaimed influence models; the measurement report insists that reach is not effect; and the digital report warns against equating telemetry with persuasion. The public site also rejects profiling and operational instruction. Still, the domain name and intelligence/game framing create room for misreading unless a PSYOPS-specific scope page is made unavoidable. |
| Does any simulation or workbench resemble real targeting, campaign design, microtargeting, surveillance, or persuasion optimization? | Not in the sampled public claims, but the resemblance risk is real | Current public materials say “no simulator” and “no operational influence tooling.” Even so, route names such as Psychology Workbench, Motivation Map, Operation Pressure Map, Compare systems, and Evidence Lab mean any future PSYOPS simulation must be even more visibly abstract, browser-local, and fictional-only. |
| Is historical content visually distinct from scenarios, estimates, projections, and fictional branches? | Partially | The site uses strong labels, but the homepage interleaves REAL-WORLD, GAME MECHANIC, and FICTIONAL blocks in one narrative flow, and the public case-files page uses “internal,” “sealed,” and “compartmented” framing. The branch/interstitial discipline recommended in the brief is not yet visible as a dedicated psych-war rule set. |
| Are internal documents and protected paths isolated from public routes? | Partially | Public pages expose “Protected research reference; no public report route in this release” rather than the underlying document bodies, which is good. But public-facing references to “sealed program file,” “internal / counterintelligence,” and compartment language should be softened or isolated so that protective boundaries are clear without dramatizing them. |
The net result is straightforward: the integrity scaffolding is stronger than the domain framing. PsychologicalWar.org already knows how to label evidence, fiction, uncertainty, and simulation boundaries. What it does not yet do is make psychological warfare itself the obvious subject, with a historical and educational filing system that ordinary readers can follow without first understanding the RogueIntelligence framing.
What the eleven drafts agree on and where they diverge
The strongest area of agreement across the upload set is boundary discipline. The terminology atlas, comparative doctrine survey, digital-era report, lifecycle reports, measurement report, and persuasion review all reject “psyop” as a catch-all for every surprising event. They converge on a few principles: terms must be distinguished by actor, authority, attribution, audience, and mechanism; reach must be separated from effect; coordination must be separated from content truth; and human behavior cannot be reduced to deterministic mind-control models.
A second strong consensus is chronological structure. The global history and research package argue for a long arc from ancient intimidation, ritual spectacle, and rumor; through print, nationalism, and total-war propaganda; into Cold War active measures and contemporary platform manipulation. The same logic appears in the doctrine and casebook files, which repeatedly move from antiquity and print to World War systems, decolonization, the Gulf War, and the digital environment. That common chronology is strong enough to become the public site’s main teaching spine.
A third area of agreement is the need to center law, oversight, and human consequences more visibly than many popular treatments do. The lifecycle papers explicitly model legal advisers, parliamentary reviewers, inspectors, courts, and complaint/remedy bodies. The IA audit pushes those into top-level routes. The cross-cultural papers add another constraint: affected communities are not passive targets but independent interpreters whose testimony can contradict official archives.
The disagreements are less about fundamentals than about emphasis. The clearest tension is between reports that treat some historical campaigns as operationally impressive and reports that insist causality is usually overclaimed. The terminology atlas and some historical cases cite very high surrender exposure and dramatic tactical outcomes in cases like the Gulf War, while the measurement report and broader research package warn that many purported “psychological” effects were actually driven by kinetic overmatch, deprivation, coercion, or existing social dynamics. That is not a contradiction to eliminate; it is exactly the kind of tension the site should preserve through claim ledgers and evidence states.
There is also productive instability around modern nomenclature. Different drafts variously foreground PSYOP, MISO, OIE, information operations, information confrontation, Three Warfares, and cognitive warfare. That instability is historically real, not editorial error. The site should not “solve” it by picking one term as universal; it should show who used which term, when, under what authority, and with what legal and doctrinal consequences.
Source dependence is concentrated in predictable clusters. The digital cluster leans heavily on EEAS FIMI, Meta threat reporting, C2PA/provenance materials, and high-visibility platform/disruption cases. The doctrine cluster leans on U.S. and NATO doctrinal vocabulary, plus well-known Russian and Chinese concepts. The governance cluster relies on common military planning and legal-boundary literature. This is not fatal, but it means the next release should deliberately add more regional archives, non-English scholarship, legal sources, and affected-community materials to reduce over-reliance on Anglophone security discourse.
The largest missing area is not doctrine or history. It is repository-ready implementation detail for public artifact handling, claim correction propagation, and rights/remedy visibility outside the IA audit itself. The IA audit proposes these strongly, but the rest of the corpus is denser on history and doctrine than on the concrete schema needed to operationalize a public educational archive. That is why the next release should prioritize schema, route hierarchy, metadata, and control surfaces before publishing a large volume of new prose.
Canonical information architecture
The proposed /psyops hierarchy is directionally correct, but it should be implemented as a domain hub with strict canonical reuse of the site’s existing evidence, correction, simulation-literacy, and psychology machinery. The goal is not to start a second site inside the first site. The goal is to make the existing site legible to the domain name by giving psychological warfare a first-class historical, doctrinal, and evidentiary home.
| Route | Recommendation | Rationale |
|---|---|---|
/psyops | Create as the new public domain gateway | This page should replace the current homepage ambiguity with a plain-English scope statement: historical and educational treatment of psychological warfare and adjacent information practices; explicit non-operational boundary; visible split between history, doctrine, artifacts, law, and bounded simulations. |
/psyops/what-are-psyops | Create | This is the public entry point for term boundaries and should map the field rather than assuming military-literacy. |
/psyops/terminology | Create | This becomes the canonical dictionary for domain terms drawn from the terminology atlas, with cross-links to doctrine, history, and case pages. |
/psyops/history and period children | Create | The history spine should be the site’s dominant educational path because it solves both realism and anti-sensationalism: readers see continuity, change, and limits over time. |
/psyops/doctrine | Create | Distinguish doctrine from practice, law, and effect. Use crosswalk tables rather than collapsing systems together. |
/psyops/institutions | Create | Needed to separate organizations, authorities, and periods from techniques or effects. |
/psyops/psychology | Create as a psych-war-specific index that reuses existing psychology material | The deep human-behavior guardrails already exist in the public site’s operational psychology content; /psyops/psychology should summarize psych mechanisms and link to that existing explanatory layer rather than duplicating it. |
/psyops/culture-and-language | Create | The two culture/semiotics reports justify a standalone route because translation and symbol misuse are recurrent failure points in both historical and digital cases. |
/psyops/media | Create | This should cut across eras: monument, print, leaflet, loudspeaker, radio, television, search, platform feeds, synthetic media, and provenance systems. |
/psyops/artifacts | Create | There is currently no visible artifact-first public route in the sampled site, and artifact handling is essential for evidentiary transparency. |
/psyops/case-studies | Create | Must be historical and source-led, distinct from the current fictional /case-files route. |
/psyops/assessment and /psyops/reach-versus-effect | Create | These should be explicit because the research corpus repeatedly treats effect inflation as the field’s central analytic failure. |
/psyops/blowback | Create | Needed to counter triumphalist or deterministic narratives. |
/psyops/law, /psyops/ethics, /psyops/oversight, /psyops/rights-and-remedy | Create | These are currently the most important public gaps. |
/psyops/digital-era and /psyops/ai-and-synthetic-media | Create | Keep them distinct: the former is the platform/information-environment transition; the latter is specifically synthetic media, provenance, and uncertainty. |
/psyops/glossary | Create or route to existing site glossary with a psych-war filtered view | Use one canonical glossary engine if the site already has one, not two parallel glossaries. |
/psyops/method, /psyops/corrections, /psyops/sources | Do not duplicate the existing sitewide method/corrections/source systems | Use these as psych-war landing indices only if needed. The canonical engines should remain the existing global method/corrections/source routes already linked from sampled pages. |
/psyops/simulations | Create as a bounded gateway, not as a standalone simulator | Reuse the existing branch/replay/correction framework already described on the site; make the psych-war section only a curated index for abstract, fictional, non-targeting educational scenarios. |
The public homepage should also change its one-sentence promise. The revised promise should foreground what the domain actually covers, for example: PsychologicalWar.org is a historical and educational archive about psychological warfare, PSYOPS, propaganda, information operations, and adjacent information practices. It distinguishes evidence from inference, history from fiction, and explanation from operational instruction. That language is consistent with the existing site’s safety posture while finally aligning the brand with the subject.
Content model, protected memory, and bounded simulations
Every public PSYOPS page should inherit a common metadata spine. At minimum: page_id, page_type, canonical_route, title, summary, time_range, jurisdiction_or_actor, evidence_state, confidence, independent_corroboration_count, review_status, review_date, currentness_cutoff, claim_ids, source_cards, correction_ids, supersession_state, related_routes, fiction_boundary, accessibility_notes, and last_substantive_change. This aligns with the site’s current public labeling habits and with the uploaded IA audit’s call for claim, correction, and currentness dependencies.
| Page type | Required metadata | Evidence state | Source cards | Currentness and correction | Accessibility elements |
|---|---|---|---|---|---|
| Term | term_id, doctrine family, first attested use, conflated terms, actor scope | official doctrine, archival usage, or peer-reviewed scholarship | source definition, comparison card, caution on misuse | current doctrinal status and deprecated aliases | definition-first heading, glossary backlinks, plain-language summary |
| Doctrine | doctrine_id, issuing body, publication date, supersession status, authority | authoritative document or archival doctrine | source doctrine, later revisions, practitioner critique | active/superseded/disputed flags; correction if later official text changes | semantic sections, abbreviation expansion, downloadable text alternative |
| Institution | institution_id, country/system, authority chain, active dates | official records plus secondary corroboration | institutional profile, authority record, review card | active/inactive/renamed; correction on misattribution | org-chart text alternative, acronym expansion |
| Historical period | period_id, start/end, regions, dominant media | synthetic historical evidence mix | timeline card, regional card, media card | usually stable; update only for historiography | accessible timeline list, era summary |
| Campaign case | case_id, dates, actors, audience, media, intent, reach/effect fields | multi-source case reconstruction | claim card, evidence matrix, dispute card | corrected when attribution/effect claims shift | event chronology list, uncertainty badges |
| Artifact | artifact_id, archive/provenance, language, medium, sponsor state, translation status | artifact existence separate from effect | image/scan card, translation card, provenance card | stable existence; content interpretation and attribution remain correctable | alt text, transcription, translation toggle |
| Person | person_id, public role, institutional affiliation, active dates | public historical role only | bio card, role card, caution on contested claims | update only with major historiographic correction | biographical summary, dates in prose and machine-readable form |
| Law or treaty | law_id, jurisdiction, date, articles, enforcement body | official legal text | statute card, commentary card, applicability note | current/in force/repealed/amended | article navigation, definitions list |
| Psychological theory | theory_id, original authors, year, evidence quality, misuse warnings | peer-reviewed literature only | theory card, replication card, limits card | currentness tied to literature review date | plain-language abstract, limitations box |
| Media channel | media_id, era, affordances, failure modes | historical/media-studies support | channel card, distribution limits, audience-access note | stable historically; digital channels reviewed periodically | diagrams described in text |
| Claim dispute | dispute_id, contested claim, positions, evidence for each side | explicitly disputed | side-by-side claim cards | must link to later corrections or unresolved status | comparison table with screen-reader labels |
| Correction | correction_id, original claim, revised claim, trigger source, latency | correction notice | original source, correcting source, affected pages list | visible propagation to all dependent routes | change summary at top; machine-readable changelog |
| Oversight body | oversight_id, jurisdiction, powers, review examples | official records and public reports | oversight charter, case card, limits card | update on structural reform or sunset | powers list, jurisdiction summary |
| Human-consequence record | consequence_id, affected population, harm type, remedy status | mixed evidence with strong uncertainty labeling | impact card, remedy card, alternative explanations | must carry currentness date and review queue | trauma-aware language, warning labels where needed |
| Simulation scenario | scenario_id, fictional population, divergence point, bounded variables | educational abstraction only | assumption card, boundary card, return-to-history card | version every variable change; never silently overwrite | visible interstitial, reduced-motion support, keyboard-only controls |
| Source report | source_id, publication type, author, custody, authenticity state, access level | source preservation or source brief | provenance card, reliability note, usage restrictions | review date and supersession note | file type disclosure, OCR/transcription availability |
The protected long-term memory structure should be created under private/.uai/psyops/ exactly as proposed in the brief, but with stable IDs and a strict distinction between preservation, synthesis, and publication. Use IDs like SRC-, TERM-, DOC-, INST-, PER-, CASE-, ART-, LAW-, PSY-, MED-, CLM-, COR-, CUR-, ROUTE-, and TOPIC-. Every memory record should point to a durable Markdown heading, never to a transient line number or an unversioned freeform note. The memory layer should store bounded summaries for hot retrieval and deep links to fuller preserved source records, not full reports in active summary memory. That design is directly supported by the site’s own event-sourcing and branch-isolation language.
The workbench and simulation layer should be deterministic, browser-local, and incapable of ingesting real persons, accounts, URLs, audiences, campaign assets, or targeting data. The eight required tools should therefore be implemented as structured reviewers, not generators:
| Workbench | Fixed controls | Output | Hard boundary |
|---|---|---|---|
| PSYOPS Term Boundary Review | select term, actor, era, authority, audience, overlap | finding IDs on conflation risk | no freeform operational prompts |
| Historical Artifact Context Review | select artifact metadata, provenance, language, medium, archive completeness | artifact-context findings | no upload of live campaign materials |
| Reach-versus-Effect Audit | choose case, reach evidence, effect evidence, alternative causes | evidentiary sufficiency findings | no metric optimization for live use |
| Doctrine-versus-Practice Review | choose doctrine, case, divergence factors | doctrine-practice gap findings | no tactical recommendations |
| Cultural and Translation Context Review | choose language, register, symbol type, mediation channel | translation/semiotic risk findings | no custom live audience tests |
| Historical Claim and Attribution Review | choose claim type, evidence sources, sponsor certainty, identity certainty | claim-grade findings | no doxxing or unverified identity assembly |
| Rights, Oversight, and Remedy Review | choose legal authority, complaint path, harm type, review status | visibility gap findings | no legal advice engine |
| Historical-to-Fictional Boundary Review | choose scenario, divergence point, historical record status | boundary-compliance findings | no forecasting, no probability unless source-authored |
The required interstitial before counterfactual branches should be mandatory, large, and unmissable: HISTORICAL RECORD ENDS HERE and FICTIONAL WHAT-IF — NOT HISTORICAL, NOT A FORECAST. It should appear before any branch content loads, not halfway through. It should also require the user to acknowledge the divergence point, see the historical source record first, and have a one-click route back to the history page. This is fully consistent with the site’s existing branch-isolation and correction framework.
Roadmap, validation, and acceptance gates
The immediate phase should correct terminology and public scope before anything else. Within the next thirty days, the site should ship a visible /psyops gateway, a homepage scope correction, a public terminology boundary page, a historical spine landing page, a rights-and-remedy landing page, and the schema needed for claim IDs, evidence states, currentness, and correction dependencies. Within sixty days, the history, doctrine, institutions, and casebook layers should become navigable. Within ninety days, the artifact database, deterministic workbenches, bounded simulations, and .uai memory integration should be in place. Specialist review for regional balance, rights review, legal review, archival rights, and translation review should remain open as a deferred but mandatory track.
Estimated additions for a credible first PSYOPS release are substantial but finite: roughly 35–50 new public pages, 90–130 glossary entries, 12–18 structured data files or registries, 180–300 protected memory records, 20–35 source briefs, and 8 deterministic workbench modules. Those estimates assume reuse of the current site’s existing method/correction/simulation-literacy infrastructure rather than rebuilding it.
The next release should be versioned as a foundation release rather than a triumphal one. A sensible target would be a WIP.36-psyops-foundation candidate with explicit acceptance gates, followed by a WIP.37-psyops-casebook candidate. The essential acceptance criteria for the foundation release are:
| Area | Acceptance gate |
|---|---|
| Public scope | Homepage and /psyops both state that the site covers psychological warfare and related practices historically and educationally, and explicitly rejects operational use. |
| Terminology | At least twelve core terms are publicly distinguished with actor, authority, audience, attribution, and overlap notes. |
| History | A chronological spine from early precedents to the digital era is publicly navigable. |
| Evidence | Every new PSYOPS page has evidence state, currentness date, claim IDs, source cards, and correction dependency fields. |
| Fiction boundary | Every counterfactual page or branch shows the required interstitial and return-to-history route. |
| Safety | No freeform simulation input accepts real persons, communities, accounts, URLs, or targeting parameters. |
| Public/private split | No public route renders a private .uai path, raw internal file path, or unreleased source body. |
| Accessibility | New pages meet keyboard navigation, heading structure, reduced-motion, transcription/alt text, and contrast requirements. |
The validation plan should define methods, not invented pass counts. At minimum, the following checks must exist before release:
| Validator | What must be tested | Method |
|---|---|---|
| Route registration | Every intended PSYOPS route is registered once and only once | route manifest diff plus build output inspection |
| Sitemap coverage | Every public PSYOPS page appears in sitemap and no private path does | compare route manifest to generated sitemap |
| Same-origin links | All internal links resolve without cross-origin leaks | automated link crawl of generated site |
| Accessibility | headings, landmarks, keyboard order, labels, alt text, transcripts | automated accessibility scan plus manual keyboard pass |
| Reduced motion | simulations and transitions respect reduced-motion preferences | browser setting test on scenario pages |
| Structured data | content-type metadata is valid and consistent | JSON-LD/schema lint or equivalent structured-data validator |
| Source provenance | every source card links to a provenance record and authenticity state | claim/source join validation against source registry |
| Claim-ledger completeness | every public claim-bearing page has claim IDs and claim records | registry completeness script or table join check |
| Historical-versus-fictional labels | all branches, scenarios, and fictional case pages display correct labels | route-class audit plus manual visual review |
| Currentness dates | every volatile page carries source cutoff and review date | metadata presence check |
| Correction propagation | a corrected claim updates all dependent pages and memory records | controlled test correction in a staging environment |
.uai deep links | public pages only point to approved deep-link abstractions, not private raw paths | string scan and link audit |
| Public/private isolation | no private/, .uai/, sealed source bodies, or raw source filenames leak publicly unless intended | build artifact grep and crawl |
| Representation safety | no protected-trait scoring, real-person inference, or targetability fields exist | schema review and prohibited-field scan |
| Non-operational boundary | no targeting, microtargeting, surveillance, persuasion optimization, or live campaign controls exist | UX review against prohibited feature list |
| PHP syntax | every PHP file parses | if PHP is present, lint all files with a parser such as php -l |
| JavaScript syntax | every JS file parses and bundles cleanly | project syntax check, linter, or bundler check |
| Clean-package integrity | release archive contains only intended public files and validated assets | reproducible build plus checksums and archive contents review |
Prioritized implementation backlog
| ticket_id | title | purpose | canonical_route | dependencies | source_reports | public_files | protected_memory | data_files | acceptance_criteria | safety_constraints | accessibility_requirements | validation_commands_or_method | estimated_complexity | release_candidate |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| PSY-001 | Reframe homepage around domain truth | Make the site unmistakably about psychological warfare history and literacy rather than primarily RogueIntelligence companion content | / and /psyops | none | Terminology Atlas; IA Audit; Research Package | homepage template; /psyops/index | ROUTE-PSYOPS-HUB; TOPIC-PSYOPS-SCOPE | route registry; homepage content config | homepage and /psyops carry clear scope, non-operational boundary, and gateway links | no claims of services, consulting, targeting, or real-world influence capability | visible landmark structure; concise summary first; high-contrast labels | manual homepage audit; route-manifest diff; link crawl | M | WIP.36 |
| PSY-002 | Publish terminology boundary atlas | Distinguish psywar/PSYOPS/IO/propaganda/public diplomacy/MILDEC/StratCom/disinformation/platform manipulation/cognitive warfare/persuasion | /psyops/terminology | PSY-001 | Terminology Atlas; Comparative Doctrine; Digital Era report | terminology landing page; term detail pages | TERM-*; CLM-TERM-* | terms.json; term_crosslinks.json | minimum 12 core terms live with authority, audience, attribution, overlap, and misuse notes | no tactical or live campaign exemplars framed as how-to | glossary navigation; acronym expansion; plain-language summaries | schema check; glossary link audit | M | WIP.36 |
| PSY-003 | Build historical spine | Give readers a coherent path from early precedents to digital systems | /psyops/history and child period routes | PSY-001, PSY-002 | Global History; Research Package | history hub; period pages | PER-*; TOPIC-HISTORY-* | periods.json; timeline.json | at least 8 period pages live with timeline and cross-links | no anachronistic overclaiming; historical equivalents labeled as analytical, not doctrinal identity | accessible timeline; no image-only chronology | route coverage check; timeline data validation | L | WIP.36 |
| PSY-004 | Add doctrine and institutions layers | Separate official doctrine, authorities, and organizations from campaigns and effects | /psyops/doctrine; /psyops/institutions | PSY-002, PSY-003 | Comparative Doctrine; Lifecycle reports | doctrine hub; institution hub; selected doctrine pages | DOC-*; INST-* | doctrines.json; institutions.json | at least 10 doctrine/institution pages live with supersession and authority metadata | no operational extraction; no current tactical advice | semantic headings; abbreviation tables readable by screen readers | metadata presence check; doctrine/institution join audit | L | WIP.36 |
| PSY-005 | Launch casebook and reach-versus-effect audit layer | Organize historical cases by era, actor, medium, audience, evidence, and outcome while preventing inflated claims | /psyops/case-studies; /psyops/reach-versus-effect; /psyops/assessment | PSY-003, PSY-004 | Measuring Effectiveness; Research Package; Digital Era report | case index; case pages; assessment explainer | CASE-*; CLM-*; COR-* | cases.json; claims.json; corrections.json | each case separates existence, attribution, reach, and demonstrated effect | no live optimization metrics, no audience scoring | comparison tables with accessible headers; uncertainty badges | claim-ledger completeness test; correction propagation test | XL | WIP.37 |
| PSY-006 | Build artifact and provenance system | Show artifact existence, provenance, translation status, and source limitations without implying effect | /psyops/artifacts | PSY-003, PSY-005 | IA Audit; Culture reports; Digital Era report | artifact index; artifact detail pages | ART-*; SRC-* | artifacts.json; sources.json; translations.json | every artifact page shows provenance, translation/transcription, and archive status | no upload of live operational materials by public users | alt text, transcripts, side-by-side translation access | source-provenance audit; asset manifest review | XL | WIP.37 |
| PSY-007 | Publish law, ethics, oversight, rights, and remedy hub | Make legal authority and human consequences as visible as doctrine and tactics | /psyops/law; /psyops/ethics; /psyops/oversight; /psyops/rights-and-remedy | PSY-004 | Lifecycle reports; IA Audit; Comparative Doctrine | law/ethics/oversight/remedy pages | LAW-*; OVR-*; HCR-* | laws.json; oversight.json; remedy_paths.json | top-level navigation exposes these routes alongside doctrine/history | no legal advice automation | readable legal summaries; definitions and article navigation | metadata validation; manual policy review | L | WIP.36 |
| PSY-008 | Enforce historical-to-fictional interstitial | Prevent counterfactual and fictional materials from blending with the historical record | /psyops/simulations and all branchable pages | PSY-003 | IA Audit; Event Sourcing page | simulation gateway; interstitial component | TOPIC-BRANCHING; ROUTE-BRANCH-* | scenarios.json | every fictional branch displays mandatory interstitial and return route | no forecasts, no real-world target modeling, no probability unless source-authored | reduced-motion compliant; keyboard-usable modal/interstitial | branch-label audit; manual scenario check | M | WIP.36 |
| PSY-009 | Build deterministic review workbenches | Provide educational review tools that stay browser-local and non-operational | /psyops/simulations and workbench routes | PSY-008, PSY-005 | IA Audit; Measurement; Culture; Lifecycle | 8 workbench pages/components | TOPIC-WB-*; CLM-WB-* | workbench_schemas.json | each tool uses fixed controls, stable finding IDs, and no arbitrary ingestion | prohibit people, accounts, URLs, psychographic inputs, target selection, campaign design | keyboard control, form labels, screen-reader result summaries | prohibited-field scan; manual UX safety review | XL | WIP.37 |
| PSY-010 | Implement protected .uai PSYOPS memory | Preserve source briefs, claim records, currentness states, corrections, and route maps with stable IDs and deep links | private/.uai/psyops/* | PSY-002 through PSY-007 | IA Audit; Event Sourcing page | none public except approved abstractions | full private/.uai/psyops/ tree | currentness.json; route_map.json; topic_maps.json | stable IDs issued; every public page maps to a protected record where appropriate | no public raw path leakage; no full hot-memory duplication of long reports | n/a for public UI except whatever is surfaced through approved cards | build-artifact grep; public/private isolation audit | L | WIP.36 |
| PSY-011 | Stand up currentness and correction registry | Make volatility and revision visible instead of burying them in prose | global method/correction system with psych-war views | PSY-005, PSY-010 | IA Audit; Research Package; sampled public pages | correction index view; currentness badges | CUR-*; COR-* | currentness.json; corrections.json | volatile pages show source cutoff, review date, and linked corrections | no silent revision of historical claim text | badges readable in text, not color alone | currentness presence check; correction propagation test | M | WIP.36 |
| PSY-012 | Commission deferred specialist review tranche | Close the largest known gaps in regional balance, archival rights, legal nuance, and lived-experience coverage | cross-site review program | after WIP.36 foundation | all eleven substantive reports plus public draft pages | selected revised pages | review memos and supersession records | review queue registry | review outcomes logged and pages updated or flagged | no publication of unresolved high-risk claims as definitive | public notice of review state retained | editorial review workflow, no invented pass counts | M | Deferred after WIP.36 |
The highest-priority sequence is therefore: PSY-001, PSY-002, PSY-003, PSY-007, PSY-010, PSY-011, PSY-004, PSY-006, PSY-005, PSY-009, PSY-012. That order fixes the domain mismatch first, then establishes the historical spine and safety boundary, then adds the structured systems necessary for credible casebooks, artifacts, and simulations. It is the most direct path to making PsychologicalWar.org feel authoritative, historically faithful, evidentially transparent, rights-aware, and unmistakably non-operational.