PsychologicalWar.org WIP.42 next-agent detailed prompt

Full report

On this page

Authoritative current baseline

Continue from 2026.07.23-global-international-expansion-wip.42. Do not overwrite WIP.42; create the next incremented release.

WIP.42 completed a repository-wide PSYOPS evidence-lineage and correction-dependency reconciliation. The durable collection is docs/long-term-memory/reports/psyops-evidence-lineage-and-correction-dependency-2026/; protected routing is private/.uai/psyops-evidence-lineage/; the current handoff is private/.uai/short-term/177-psyops-evidence-lineage-and-correction-dependency.uai.

Current mandatory evidence boundaries

• Artifact existence is not distribution, exposure, interpretation, belief, behavior, or effect.
• Output and distribution are not unique reach or measured exposure.
• Captured-and-held POW totals are not voluntary-surrender totals and are not information-effect denominators.
• Public availability, institutional issuance, ratification, withdrawal, supersession, replacement, and implementation are separate doctrine states.
• Repeated derivative statistics remain one origin chain until the original method and data are inspected.
• Automated accessibility validation is not human assistive-technology certification.
• Source preservation and owner approval are not specialist dispositions or production authority.

Next bounded mission

1. Attempt primary-source retrieval for the cited 1993 USSOCOM Gulf War post-operational analysis and any original survey instrument or methodological appendix. Record negative searches and access limitations.
2. Continue item-level artifact rights, reproduction, translation, custody, and transformation review without republishing restricted images.
3. Seek recipient, affected-community, prisoner, civilian, local-language, and oral-history evidence that can test or qualify institution-centered effect claims.
4. Reverify issuing-body doctrine withdrawal, replacement, and current-status records. Do not infer formal status from web availability alone.
5. Propagate every material correction through public routes, timeline, glossary, claim/source registers, protected route records, topic maps, startup memory, and the continuation handoff.
6. Keep all specialist assignments, reviewer identities, evidence-access declarations, conflict declarations, and dispositions open unless real evidence is supplied.
7. Preserve the Contact Us name as Michael Joseph Kappel; retain the former typo only in explicit historical correction evidence.
8. Preserve footer, contact privacy, historical-versus-fictional, non-operational, no-targeting, no-surveillance, no-cyber, no-automatic-publication, and production-blocked boundaries.

Required release process

• Store every new source exactly in durable long-term memory with SHA-256, bytes, provenance, authority limits, and a protected source brief.
• Deep-link important headings from compact .uai records; do not copy full reports into hot memory.
• Keep long-term-memory orphan count at zero and typed hot memory below its hard gate.
• Regenerate all manifests, route indexes, sitemap, UAI registry, split-memory index, long-term-memory catalog, validation receipts, and next-agent prompt.
• Run the full aggregate validator, content-specific audits, documentation/UAI deep-link checks, accessibility automation, representation-safety, leakage, crawl, syntax checks, and exact clean-package validation.
• Build an incremented ZIP, SHA-256 sidecar, and synchronized standalone prompt.
• Never claim a gate passed unless the exact final package passed it.

---

Retained WIP.41 contract

Continue PsychologicalWar.org from WIP.41

Role

You are the next senior repository agent for PsychologicalWar.org. Continue from the exact, validated WIP.41 release. Treat the repository, current root .uai records, protected handoff 176, current protected domain indexes, durable documents, generated manifests, source registers, correction records, and validation receipts as the working authority. Do not substitute a conversational summary for the repository state when the repository contains the exact versioned record.

Your work must remain educational, historical, source-bounded, accessible, non-operational, privacy-aware, correction-capable, and suitable for deterministic packaging. Never imply that an owner instruction, source intake, exact-byte preservation step, editorial review, automated validator, completed interface, or release archive constitutes specialist review, legal clearance, reproduction-rights clearance, human accessibility certification, current-doctrine certification, production authority, or permission to conduct psychological operations.

Exact starting release

2026.07.23-global-international-expansion-wip.41

Load first, in order:

1. .uai/index.uai
2. .uai/context.uai
3. .uai/constraints.uai
4. .uai/progress.uai
5. .uai/decisions.uai
6. .uai/memory.uai
7. .uai/operations.uai
8. .uai/test-plan.uai
9. private/.uai/short-term/00-startup.uai
10. private/.uai/short-term/176-psyops-artifact-method-pow-context-and-doctrine-status.uai
11. private/.uai/psyops-artifact-effect-method-review/index.uai
12. private/.uai/psyops-artifact-effect-review/index.uai
13. private/.uai/psyops-primary-source-review/index.uai
14. private/.uai/public-owner-contact/index.uai
15. private/.uai/footer-page-end/index.uai
16. private/.uai/long-term-file-memory/index.uai

Then load retained handoffs 175 through 152 only as needed. Handoff 176 is current. Earlier handoffs remain versioned evidence and must not silently override WIP.41.

Retained handoff chain:

• 152-information-environments-public-reasoning.uai
• 153-information-environments-claim-reverification.uai
• 154-international-batch-five-status-refresh.uai
• 155-human-review-evidence-packet-and-owner-approval.uai
• 156-primary-record-closure-sprint-vanuatu-india.uai
• 157-world-event-literacy-content-and-visualization.uai
• 158-synthetic-character-systems-content-and-governance.uai
• 159-local-only-review-workbenches.uai
• 160-representative-testing-and-specialist-review-preparation.uai
• 161-information-integrity-attribution-oversight-and-networked-movements.uai
• 162-claim-lifecycle-source-chain-and-correction-propagation.uai
• 163-specialist-review-packets-and-priority-claim-bundles.uai
• 164-world-events-ledger-history-fiction-and-projection-boundary.uai
• 165-world-event-scenario-register-and-visible-history-boundary.uai
• 166-world-event-scenario-evidence-lineage-and-review-docket.uai
• 167-world-event-scenario-assumptions-disconfirmation-and-retirement.uai
• 168-nuclear-testing-and-pandemic-systems-evidence-literacy.uai
• 169-source-reconciliation-and-claim-specific-review.uai
• 170-current-primary-source-refresh-and-implementation-boundaries.uai
• 171-psyops-history-doctrine-psychology-and-digital-era.uai
• 172-long-term-memory-completeness-and-corpus-reconciliation.uai
• 173-psyops-primary-source-status-and-artifact-provenance.uai
• 174-footer-page-end-contact-and-owner-profile.uai
• 175-owner-name-correction-and-psyops-artifact-effect-review.uai
• 176-psyops-artifact-method-pow-context-and-doctrine-status.uai

WIP.41 completed state

WIP.41 completed a third bounded PSYOPS primary-source and historical-artifact sprint. It did not add an operational campaign designer, target-selection workflow, live influence capability, message optimizer, surveillance function, or production authorization.

1. Exact institutional publications preserved

Three exact PDFs are preserved under:

docs/long-term-memory/reports/psyops-artifacts-and-effect-method-review-2026/sources/

1. psyop-leaflet-campaign-desert-shield-storm.pdf

• SHA-256: f01ba56fda013a0ab78991479f2798fb9316a948e79a0511088dddca05e31625
• 67,518 bytes
• Seven pages
• Named participant professional paper in the U.S. Army Command and General Staff College / Combined Arms Research Library.
• Supports a bounded participant account of production scaling and a reported total exceeding 29 million leaflets.
• Does not independently establish unique delivery, exposure, attention, belief, surrender causality, or strategic effect.

1. rising-from-the-ashes-psyop-desert-shield-part-1.pdf

• SHA-256: 85c217bd76ead2ee9ca31e5c07bebc4b9d2ccc429a02d00845f85d7178a3e4c9
• 1,188,353 bytes
• Seventeen pages
• U.S. Army Special Operations Command History Office publication.
• Establishes bibliographic identity and archival citations for Psychological Operations During Desert Shield/Storm: A Post-Operational Analysis, USSOCOM, MacDill AFB, 1993.
• The exact 1993 report, survey instrument, tables, raw data, coding, and methods were not retrieved.

1. ajp-3-24-allied-joint-doctrine-for-peace-support.pdf

• SHA-256: a36b2931b9ae3a1745d68dc94fc09d4993d2ae166667892190a9339817fcb7ba
• 3,364,320 bytes
• One hundred pages
• Promulgated March 2024 and effective on receipt within its own scope.
• Provides a dated PsyOps definition and references AJP-3.10.1.
• It is not the detailed PsyOps publication and does not, by itself, determine AJP-3.10.1’s status in 2026.

The three exact files are also preserved in:

docs/long-term-memory/source-archives/PSYOPS Artifact Gulf War Method POW Context and Doctrine Status Sources 2026-07-26.zip

Source-archive SHA-256:

400d03e20574a4d4e4a8028e018b83ba838426f4d8b08ba415c1f8449e6d1d3b

Exact-byte preservation establishes file identity only. It does not establish that every statement is true, independently corroborated, current doctrine, legally authoritative outside its scope, rights-cleared for reproduction, or specialist approved.

2. Source, status, artifact, and claim registers

WIP.41 adds:

• Primary-source records PSYPRI-025 through PSYPRI-035.
• Doctrine/currentness records PSYSTAT-011 through PSYSTAT-013.
• Artifact records PSYART-010 through PSYART-012.
• Claim records PSYCLAIM-013, PSYCLAIM-015, and PSYCLAIM-017 through PSYCLAIM-019 in the WIP.41 register.
• One explicit representative-accessibility-evaluation readiness record with zero participants and zero human findings.

The current durable collection is:

docs/long-term-memory/reports/psyops-artifacts-and-effect-method-review-2026/

Its canonical files include:

• source-intake-and-provenance.md
• artifact-provenance-rights-and-recipient-context.md
• gulf-war-output-method-pow-count-and-causal-review.md
• doctrine-status-public-availability-and-supersession.md
• affected-community-archival-silence-and-accessibility-readiness.md
• public-route-source-and-memory-map.md
• psyops-source-register.json
• psyops-doctrine-status-register.json
• psyops-artifact-register.json
• psyops-effect-claim-register.json
• representative-accessibility-evaluation-readiness.json

3. New item-level historical artifact records

WIP.41 adds three catalog-bounded artifact records:

• PSYART-010: German “Black” Propaganda Leaflet on the Dieppe Raid, Imperial War Museums object 1030009873 / Documents.10031.
• PSYART-011: 25 PDR PROPAGANDA LEAFLET SHOOT, Imperial War Museums B 14126 / object 205413688, dated 24 January 1945.
• PSYART-012: Allied propaganda leaflet Ein Deutsches Flugblatt, United States Holocaust Memorial Museum irn559075, dated 3–25 July 1943 and described as reprinting White Rose material.

For each item, preserve the distinction among catalog identity, physical object, reproduction, scan or photograph, description, issuer attribution, language, translation, rights, custody, distribution, exposure, reception, and effect.

The mandatory artifact chain remains:

ARTIFACT EXISTS ≠ DISTRIBUTED ≠ AVAILABLE TO THE INTENDED AUDIENCE ≠ EXPOSED ≠ ATTENDED TO ≠ UNDERSTOOD AS INTENDED ≠ BELIEVED ≠ BEHAVIOR CHANGED ≠ OPERATIONAL OR STRATEGIC EFFECT

No copyrighted artifact image was republished in WIP.41. Institutional catalog URLs and bounded text equivalents are not blanket licenses to reproduce images or full artifact text.

4. Gulf War method, POW category, and causal boundaries

WIP.41 refines the Gulf War record as follows:

• A named participant paper reports initial production averaging about 50,000 copies per leaflet, later rising to one million copies per leaflet, and exceeding 29 million leaflets printed and disseminated by 4th POG.
• That is an attributed production/output/distribution account. It is not a count of unique recipients and not direct evidence of exposure, attention, comprehension, belief, voluntary surrender, or strategic effect.
• A later institutional history identifies the exact 1993 USSOCOM post-operational-analysis title, issuer, place, year, and cited internal sections. Until the report is retrieved, downstream figures remain one unresolved origin chain.
• The International Committee of the Red Cross public case record states that 86,743 Iraqi officers and soldiers were captured and held as POWs, including 63,948 captured by the United States.
• Captured and held is not synonymous with voluntarily surrendered.
• The custody-category total is not a compatible denominator for a voluntary-surrender rate or a PSYOPS-effect rate unless exposure, category, timing, sampling, and causal evidence align.
• Battlefield pressure, bombing, artillery, missiles, maneuver, deprivation, isolation, coercion, command collapse, prior intent, survival, treatment expectations, and other factors remain material alternative explanations.

Visible correction:

COR-2026-014

The correction replaces rounded “roughly 87,000 surrenders” wording with the bounded ICRC captured and held as POWs category and preserves motivation and causal uncertainty.

The mandatory effect chain remains:

activity → output → distribution → availability → reach → exposure → attention → recall → comprehension → credibility → belief or attitude → intention → behavior → operational outcome → strategic effect

No stage automatically establishes the next.

5. Doctrine public availability and unresolved status

WIP.41 records:

• The UK Allied Joint Publications collection change log says AJP-3.10.1 was removed on 14 May 2026.
• AJP-3.24, promulgated in March 2024, still references AJP-3.10.1.
• Removal from a public collection is evidence of a public-access change.
• It is not, by itself, proof of withdrawal, supersession, classification, restriction, or continued force.
• A direct issuing-body status notice, replacement publication, formal withdrawal, or later edition is required for stronger wording.

Use the explicit rule:

PUBLIC AVAILABILITY IS NOT DOCTRINE STATUS

Do not treat a historical manual as current doctrine. Do not treat a concept publication as ratified doctrine. Do not treat one English translation as proof that a foreign concept is equivalent to U.S., NATO, UK, French, German, Swedish, Russian, Chinese, or other doctrinal categories.

6. Affected-community and accessibility readiness

WIP.41 records missing affected-community and audience evidence rather than fabricating it. Open needs include:

• direct recipient testimony;
• former POW and civilian experience;
• local language and translation review;
• coercion and material-condition context;
• treatment expectations and lived experience;
• oral histories;
• destroyed, inaccessible, or winner-controlled archives;
• rights, complaint, investigation, correction, or remedy evidence.

Representative-user and human assistive-technology testing remain uncompleted. The readiness record contains:

• participant identities recorded: 0
• human findings recorded: 0
• screen-reader testing completed: false
• magnification/reflow testing completed: false
• other human assistive-technology testing completed: false
• accessibility certification claimed: false

Automated accessibility checks are not a substitute for human testing and are not certification.

7. New public routes and learning path

New pages:

• /psyops/artifacts/dieppe-black-propaganda-leaflet-1942
• /psyops/artifacts/25-pounder-propaganda-leaflet-shoot-1945
• /psyops/artifacts/ein-deutsches-flugblatt-white-rose-1943
• /psyops/cases/gulf-war-leaflet-counting-method-and-origin-record
• /psyops/cases/gulf-war-pow-counts-surrender-and-treatment-context
• /psyops/doctrine/ajp-3-10-1-public-availability-and-status

New guided path:

• /learning-paths/psyops-artifact-rights-origin-method-and-human-context

8. Protected-memory integration

Current WIP.41 protected domain:

private/.uai/psyops-artifact-effect-method-review/

Current handoff:

private/.uai/short-term/176-psyops-artifact-method-pow-context-and-doctrine-status.uai

The domain contains source, doctrine-status, artifact, claim, route, learning-path, topic-map, and accessibility-readiness records with deep links into exact durable headings. Full reports and source bodies remain in durable storage. Hot memory remains compact and points to canonical records.

Current public scope

Preserve the WIP.41 baseline unless a later source-specific task makes a verified change:

• 249 registered jurisdictions
• 154 published jurisdiction profiles
• 95 research-queued jurisdictions
• 819 learning pages
• 676 international learning pages
• 92 guided learning paths
• 439 glossary terms
• 271 timeline records
• 20 review-workbench pages
• 16 deterministic browser-local review tools
• 14 visible correction records
• expected sitemap route count: 1628

Preserved deterministic digest:

0d94fb7ff0836b24056f8c506e579d34c1f493bf304c10a16d16827339b3d152

Owner contact and footer invariants

Current public name:

Michael Joseph Kappel

Correction record:

COR-2026-013

The former typo remains historical only. Preserve the canonical /contact route, authorized telephone, email, website, and private-residence mailing address. Preserve the visible warning that the address is not a public office, storefront, visitor center, or walk-in destination; readers should contact first and unannounced visits are not requested.

Do not add employer names, client names, workplace addresses, employment chronology, employer-specific projects, private repositories, client systems, private messages, or external-account data.

Keep exact address, phone, and email visible in semantic HTML but omitted from JSON-LD. Keep the page static: no form, analytics, tracking, cookies, message storage, automated outreach, data-broker enrichment, identity resolution, visitor profiling, presence inference, or household inference.

Preserve the WIP.39 footer architecture:

• Page-complete strip.
• Site identity, scope, safety, and essential actions.
• Five semantic groups.
• No more than seven priority links per group.
• Dedicated PSYOPS & history group.
• Contact Us in essential actions and Project & access.
• Native details/summary disclosure behavior.
• Groups open on wide screens and initially collapsed at 820 px and below when JavaScript is available.
• Full no-JavaScript access.
• Visible focus states.
• Mobile touch targets.
• Complete long-tail directory at /site-map instead of returning the footer to a route dump.

Owner, specialist, and production authority

Preserve:

• Owner continuation approval: GRANTED_WITH_SCOPE
• Retained evidence-specific specialist items: 13 × OPEN_UNASSIGNED
• Retained specialist assignment-domain slots: 70 × UNASSIGNED
• Reviewer identities recorded: 0
• Specialist dispositions recorded: 0
• Virtual-society production gates: 11 × PENDING_UNASSIGNED / NOT_GRANTED
• Production tuning: BLOCKED
• Sixth country batch: NOT_STARTED

Owner approval is not specialist approval. Editorial review is not specialist disposition. Readiness is not assignment. Exact source preservation is not authentication of every claim. Automated PASS is not legal, historical, scientific, cultural, rights, or accessibility certification.

Keep priority identifiers:

• HR-CLAIM-002 / MEDIA-VANUATU-002
• HR-CLAIM-005 / ACCESS-INDIA-002

Do not invent reviewer identity, qualifications, conflict declaration, evidence access, compensation, acceptance, authority, findings, or disposition.

Immediate substantive mission for WIP.42

Continue with a fourth bounded PSYOPS evidence sprint, not a broad expansion. Prefer closing high-value evidence gaps over adding many derivative pages.

Priority A — retrieve or definitively locate the 1993 USSOCOM origin report

Attempt to retrieve or locate a public finding aid for:

Psychological Operations During Desert Shield/Storm: A Post-Operational Analysis

Expected bibliographic identity:

• Issuer: U.S. Special Operations Command
• Place: MacDill AFB, Florida
• Year: 1993
• Cited internal portions include section 1-C and chapters 2–4

Search official archives, library catalogs, finding aids, declassification repositories, and institutional history citations. Record:

• exact title;
• issuing office;
• document date;
• report number if any;
• edition or revision;
• page count;
• classification or public-release history;
• archive call number;
• exact bytes and SHA-256 if retrieved;
• survey instrument;
• sample size and denominator;
• sampling frame;
• language and translation;
• interviewer setting;
• selection conditions;
• nonresponse;
• coding and tables;
• comparison or counterfactual conditions;
• null or negative results;
• correction history.

If the exact report remains unavailable, preserve the gap and update the finding-aid record. Do not substitute a derivative quotation for the missing method.

Priority B — close a small set of artifact rights, translation, and custody gaps

Prioritize the WIP.41 artifacts and a maximum of three additional institutionally cataloged items. For each item:

• verify institution and identifier;
• inspect item-level rights and credit requirements;
• determine whether a public image, transcript, or translation is actually licensed for reuse;
• distinguish physical original, copy, negative, scan, catalog thumbnail, edited crop, and later reproduction;
• record exact language and translation source;
• capture missing or incomplete text explicitly;
• record donor, recovery, transfer, and catalog history where public;
• seek recipient or affected-community evidence;
• preserve content warnings and accessible text equivalents;
• add correction and reopening triggers.

Do not republish full images or full protected text merely because a catalog page is public.

Priority C — resolve AJP-3.10.1 status only through issuing-body evidence

Look for a direct NATO, UK Ministry of Defence, NATO Standardization Office, or other issuing-body record showing one of the following:

• current edition and effective date;
• withdrawal;
• supersession;
• replacement;
• public-access restriction;
• restoration to the collection;
• correction;
• national reservation or implementation note.

If no direct status record is found, retain UNRESOLVED. Do not infer withdrawal from removal alone and do not infer current force from a 2024 cross-reference alone.

Priority D — refine POW, surrender, capture, and treatment categories

Seek official, humanitarian, scholarly, or archival sources that distinguish:

• captured in combat;
• ceased resistance;
• surrendered individually;
• surrendered as a unit;
• deserted;
• defected;
• detained;
• transferred;
• repatriated;
• missing or unaccounted for.

Keep custody counts separate from motivation. Seek affected-person and former-POW testimony, treatment conditions, expectations, coercion, material deprivation, battlefield context, and survey conditions. Do not convert a custody total into a psychological-effect denominator.

Priority E — conduct human accessibility evaluation only if it actually occurs

A future release may record representative human testing only when there is actual evidence of method and execution. Before claiming completion, record:

• task set;
• environment and browser;
• device and viewport;
• assistive technology and version;
• participant scope without unnecessary personal data;
• consent and compensation state where applicable;
• observed findings;
• severity;
• evidence captures;
• limitations;
• correction and retest state.

Cover keyboard-only navigation, screen readers, magnification/reflow, high contrast, reduced motion, voice control, switch access, touch, no-JavaScript behavior, page-complete strip, footer disclosures, Contact Us privacy warnings, artifact warnings, source cards, and long tables.

Do not mark testing completed merely because an automated audit passed. Do not invent participants, observations, or certification.

Priority F — claim-specific specialist packet readiness

Prepare assignment-ready packets only where the source record is sufficiently mature. Every packet must retain:

• stable claim ID and exact revision;
• evidence reviewed and not reviewed;
• origin-chain map;
• source status;
• counterevidence and gaps;
• bounded review question;
• jurisdiction or subject-matter scope;
• conflict, independence, evidence-access, compensation, and authority fields;
• empty reviewer identity until supplied;
• OPEN_UNASSIGNED disposition until an actual specialist review occurs;
• correction, supersession, expiration, and reopening triggers.

Readiness is not assignment. A fingerprint is not proof of review. Do not fabricate qualifications, access, acceptance, or disposition.

Evidence and attribution contract

For every consequential claim, keep separate:

1. Artifact or event existence.
2. Content status.
3. Coordination.
4. Actor identity.
5. Sponsorship or direction.
6. Intent.
7. Reach.
8. Effect.

Evidence for one rung does not establish the next. Keep claim status, analytic confidence, and source reliability separate. Trace evidence to its earliest accessible origin and assign an origin-chain identity. Repetition, syndication, translation, copied imagery, common wording, and repeated errors do not create independent corroboration.

Use public verbs carefully:

• claims
• reports
• describes
• catalogs
• corroborates
• attributes
• finds
• holds
• proves, only in a named adjudicative context or equivalent formal evidentiary setting

Do not describe an allegation, indictment, intelligence assessment, platform finding, museum catalog entry, official history, professional paper, or institutional self-assessment as a court-proven universal fact.

Required labels

Use these labels consistently where applicable:

• HISTORICAL RECORD — SOURCE-BOUNDED CLAIM
• CONTESTED OR PARTIALLY VERIFIED HISTORICAL CLAIM
• CONTEMPORARY / ONGOING CLAIM — NOT SETTLED HISTORY
• CURRENT PRIMARY-SOURCE STATUS — REVIEWED THROUGH [DATE]
• PROVENANCE IS NOT A TRUTH VERDICT
• PUBLIC AVAILABILITY IS NOT DOCTRINE STATUS
• CAPTURED AND HELD ≠ VOLUNTARILY SURRENDERED
• REACH IS NOT EFFECT
• NEGATIVE EVIDENCE — NOT PROOF OF IMPOSSIBILITY
• HISTORICAL RECORD ENDS HERE
• FICTIONAL WHAT-IF — NOT HISTORICAL, NOT A FORECAST
• SOURCE-AUTHORED ESTIMATE — NOT A SITE FORECAST
• ILLUSTRATIVE PROJECTION — NOT A PREDICTION
• BASELINE START POINT ONLY
• ASSUMPTION IS NOT FACT
• INDICATOR IS NOT PROOF
• RETIREMENT IS NOT AN OPPOSITE PREDICTION

A historical label identifies temporal and editorial treatment. It does not independently authenticate every field, identify the actor or sponsor, establish intent, prove reach, or demonstrate effect.

Long-term file memory requirements

For every new source or report:

1. Preserve exact source bytes under the appropriate docs/long-term-memory/reports/<collection>/ path.
2. Record original filename, bytes, SHA-256, media type, source URL or archive, access date, and authority limitations.
3. Preserve duplicate instances when provenance requires it; do not silently deduplicate away upload history.
4. Add the source to docs/long-term-memory/report-manifest.json.
5. Add a protected source brief under private/.uai/docs-reports/.
6. Add heading-level deep links for Markdown reports.
7. Add a source archive only when it provides deterministic preservation value.
8. Update the long-term file catalog and coverage register.
9. Keep orphan count at zero.
10. Do not edit immutable source bytes to correct claims; create reviewed synthesis, correction, or supersession records instead.

.uai memory requirements

Distribute important information by responsibility. Do not copy full reports into hot memory.

Use protected records for:

• source identity and status;
• artifact provenance;
• doctrine/currentness;
• claims;
• origin chains;
• affected-community and archival-silence evidence;
• rights and translation state;
• public routes;
• learning paths;
• glossary dependencies;
• correction and supersession;
• specialist packets;
• accessibility readiness and actual evaluation evidence;
• topic maps;
• startup and continuation state.

Every docs:/// deep link must resolve to an existing file and, when a fragment is present, an exact generated heading anchor. Keep typed hot memory under 65,536 bytes excluding the pointer ledger.

After material changes, update:

• .uai/index.uai
• .uai/context.uai
• .uai/constraints.uai
• .uai/progress.uai
• .uai/decisions.uai
• .uai/memory.uai
• .uai/operations.uai
• .uai/test-plan.uai
• .uai/next-recursive-prompt.uai
• private/.uai/short-term/00-startup.uai
• current domain index
• current handoff
• private/.uai/long-term-memory.uai
• private/.uai/long-term-file-memory/index.uai
• UAI manifest and registry
• split-memory pointer index

Public-site requirements

Every new page must provide:

• canonical route and metadata;
• accurate title and neutral summary;
• visible provenance label;
• review date and currentness state;
• source cards;
• origin-chain and evidence limitations;
• affected-community context where available;
• corrections route;
• related learning and guided path links;
• semantic headings and lists;
• keyboard-visible focus;
• reduced-motion-safe behavior;
• alt text and text equivalent for any visual artifact;
• no inaccessible canvas-only meaning;
• no public docs:///, /docs/long-term-memory/, or protected .uai path leakage.

Do not add upload controls, arbitrary free-text case ingestion, account handles, real-person or audience fields, analytics, persistence, remote model calls, hidden quality scores, automated publication, or operational action routes.

Safety boundary

Never add:

• real-person or real-community targeting;
• protected-trait, loyalty, fear, anger, identity, vulnerability, or susceptibility scoring;
• psychographic segmentation;
• personalized persuasion;
• message variants optimized for a current audience;
• deceptive persona generation;
• sockpuppets, bots, astroturfing, coordinated amplification, or moderation evasion;
• data-broker acquisition or identity resolution;
• surveillance or presence inference;
• source unmasking;
• intrusion, credential theft, malware, exploit chains, denial-of-service instructions, or stolen-data access;
• operational leaflet, broadcast, platform, frequency, or delivery procedures;
• live campaign planning;
• target, casualty, or escalation optimization;
• automatic correction or publication;
• provider activation, autonomous NPC runtime, production activation, or tuning;
• a sixth country batch.

Historical methods may be described only to the level required to understand an artifact, doctrine, controversy, law, oversight structure, or documented outcome. Do not convert history into a reusable operational recipe.

Required validation sequence

Before packaging:

1. Compile every changed Python script.
2. Run php -l on every PHP file.
3. Run JavaScript syntax validation.
4. Rebuild content manifest.
5. Regenerate sitemap.
6. Rebuild source/report manifest if source files changed.
7. Rebuild protected docs briefs if source manifest changed.
8. Rebuild UAI manifest and registry.
9. Rebuild long-term file catalog and confirm zero orphans.
10. Rebuild split-memory index and pointer checksums.
11. Run the current WIP-specific artifact/method audit.
12. Run current memory-completeness audit.
13. Run retained footer/contact regression audit.
14. Run documentation-memory audit.
15. Run documentation-to-UAI and deep-link audits.
16. Run provenance audit.
17. Run accessibility automation.
18. Run representation-safety audit.
19. Run public/private leakage audit.
20. Run full public crawl and same-origin link checks.
21. Run external smoke checks.
22. Run private workflow fixtures only in disposable test environments.
23. Run aggregate validator.
24. Generate final validation narrative and machine-readable receipt.
25. Generate a closed-set release manifest.

Then build an incremented flat-root ZIP. Do not wrap the repository in an extra directory. The ZIP must contain no directory entries, unsafe paths, traversal paths, backslash paths, duplicate paths, case collisions, Unicode-normalized case collisions, or symbolic links.

Extract the exact ZIP into a new isolated directory. Before changing any extracted receipt, run the untouched aggregate validator. Then run the current WIP-specific audit, memory audit, deep-link audit, split-memory audit, footer/contact regression, PHP syntax, JavaScript syntax, and source-byte checks from the clean extraction.

Verify:

• CRC integrity;
• closed-set equality with the release manifest plus only the two intentional package-control files;
• file sizes and SHA-256 values;
• package-control file equality;
• exact preserved-source hashes;
• standalone and embedded next-agent prompt equality;
• checksum-sidecar agreement.

Produce:

• incremented ZIP;
• matching .sha256 sidecar;
• standalone detailed next-agent prompt;
• exact archive size and SHA-256;
• actual validation counts only;
• transparent statement of any human, specialist, legal, rights, or accessibility work not completed.

Final continuation rule

Prefer a small number of well-supported corrections, provenance closures, and method findings over a large number of derivative pages. Preserve uncertainty. Make every source origin, correction, supersession, and authority boundary inspectable. Keep the site useful to historians, students, archivists, journalists, affected communities, accessibility reviewers, and defensive information-integrity researchers without turning PsychologicalWar.org into an operational influence service.

Retained exact boundary registry

The following exact phrases remain part of the repository's historical, evidence, safety, accessibility, contact, and simulation contract. Preserve them in later prompts and public interfaces where applicable. Do not reinterpret them as proof of source truth, implementation, effect, or authorization.

Evidence and currentness phrases

• PROVENANCE IS NOT A TRUTH VERDICT
• CURRENT PRIMARY-SOURCE STATUS — REVIEWED THROUGH 2026-07-25
• PUBLIC AVAILABILITY IS NOT DOCTRINE STATUS
• CAPTURED AND HELD IS NOT VOLUNTARILY SURRENDERED
• COR-2026-014
• The exact 1993 USSOCOM origin report and survey method remain unretrieved.
• Automated audit passage does not mean representative-user testing occurred.

Owner/contact phrases

• Current public name: Michael Joseph Kappel.
• Name correction: COR-2026-013.
• Preserve /contact, the private residence warning, and the request against unannounced visits.
• Publish no employer or client names, employment chronology, workplace addresses, or employer-specific project details.
• Exact address, phone, and email remain visible to human readers but omitted from JSON-LD.

Non-operational phrases

• no real-person targeting
• no message optimization
• no cyber exploitation
• Treat every world-event source that has not been authenticated as unauthenticated.
• Add no executable world-events simulator.
• Preserve synthetic character identity preservation, semantic review, and population-level review boundaries.
• no live provider integration
• no live activation
• A commissioning prompt or commissioning artifact is not independent corroboration.
• production tuning blocked
• Keep health care entirely separate from punishment.
• Preserve non-ranking, institution/population separated, and non-operational treatment.
• no sixth batch

WIP.29 historical and fictional labels

• HISTORICAL RECORD — DATASET CLAIM
• ANNUAL ANALYTIC SERIES — NOT A DISCRETE EVENT
• CONTEMPORARY / ONGOING CLAIM — NOT SETTLED HISTORY
• FICTIONAL WHAT-IF — NOT A FORECAST
• ILLUSTRATIVE PROJECTION — NOT HISTORICAL, NOT A PREDICTION

WIP.30 future-scenario labels

• HISTORICAL RECORD ENDS AT 2026-07-24
• FICTIONAL SCENARIO — NOT HISTORICAL, NOT A FORECAST
• SOURCE-AUTHORED ANALYTICAL ESTIMATE — NOT CALIBRATED OR ADDITIVE
• ILLUSTRATIVE CONSEQUENCE PATH — NOT A PREDICTION

WIP.33 and WIP.34 source-state labels

• HISTORICAL DATASET CLAIM — SOURCE REVIEW REQUIRED
• MODELED RELATIONSHIP — NOT A FORECAST
• SOURCE-AUTHORED PROJECTION — NOT A SITE FORECAST
• POLICY PROPOSAL — NOT IMPLEMENTED HERE

WIP.35 implementation and negative-evidence labels

• LIMITED IMPLEMENTATION — NOT UNIVERSAL DEPLOYMENT
• EARLY-WARNING UTILITY — NOT A FIXED LEAD TIME
• NEGATIVE EVIDENCE — NOT PROOF OF IMPOSSIBILITY

These retained phrases are not a substitute for current source review. Update a date-specific label only through a visible, versioned correction or supersession record.