Deterministic Alliance Campaign State and Mission Expansion Report

Status

Current implementation report for IARPG-OPS-2 2.0.15-wip. The campaign system is fictional, browser-local, deterministic, and reviewed as implementation evidence rather than proof of entertainment value, human comprehension, or real-world geopolitical accuracy.

Purpose

Document the conversion of the static fictional alliance publication into a versioned campaign-state prototype with explicit evidence, consultation, burden, dependency, internal-bloc, affected-community, correction, and reversible-transition records.

Scope

This report covers campaign-state.json, its schemas and example export, the /campaign console, the extension of alliance-network.json, twelve alliance-centered mission briefs, discovery and memory routing, and deterministic fairness and abuse-case review. It does not establish facts about real countries, organizations, people, recruitment pathways, or current alliances.

Executive Summary

IARPG now models alliance change as a versioned sequence of explainable turns rather than a mutable friendship meter. The 12 fictional factions and 27 relationships remain domain-specific. Nine safe stress events provide 27 response options. Each option identifies evidence events, consultation rules, versioned before-and-after relationship states, reason codes, relative burden changes, dependency changes, internal-bloc reactions, affected-community consequences, corrections, and reversal conditions.

The browser-local Campaign State Console embeds its machine records in the page, performs no external request, stores no identity or work data, and exports compact turn or multi-turn JSON through local Blob downloads. Its command surface includes a full 27-row current-state board, lifecycle distribution, explainable next-turn preview, versioned turn history, local undo, and a responsive campaign dashboard. Twelve campaign mission briefs translate mediation, humanitarian access, source protection, rumor correction, deconfliction, oversight, burden sharing, refusal, disengagement, and reintegration into nonviolent fictional operations.

Evidence Reviewed

• [Alliance and Recruitment Worldbuilding System](alliance-and-recruitment-worldbuilding-system.md#reviewed-synthesis)
• [How Alliances Actually Work](how-alliances-actually-work.md#reviewed-synthesis)
• [Faction Archetypes and Recruitment Ecosystems](faction-archetypes-and-recruitment-ecosystems.md#reviewed-synthesis)
• [Lone-Actor Mobilization, Network Influence, and Disengagement](lone-actor-mobilization-network-influence-and-disengagement.md#reviewed-synthesis)
• [Alliance, Faction, and Network World-System Integration Report](alliance-faction-and-network-world-system-integration-report.md#findings)
• Fictional alliance network
• Campaign-state publication
• Campaign-state schema
• Campaign-turn schema
• Campaign-turn example

Findings

Relationship history is versioned and reconstructable

The campaign publication contains 27 versioned relationship-state records that establish Turn 0. Every preview starts from the current in-memory versions and every commit appends a full turn record. The active tab also permits one-step undo: it removes the latest unexported turn from the current session and reconstructs state from the immutable baseline plus the remaining turns. Any previously downloaded export remains unchanged.

Change requires evidence and a reason code

Each relationship delta cites one or more explicit evidence-event IDs and one or more of 16 neutral reason codes: mandate change, evidence correction, safeguard breach, burden imbalance, dependency shock, consultation failure, access restoration, affected-community consequence, confidence repair, or scope narrowing.

Domain specificity remains the core rule

A scenario changes only the named relationship domains. It never converts the network into a global friend/enemy, loyalty, morality, threat, or recruitability score. Cooperation, competition, deconfliction, sponsorship, and rivalry can still coexist across different domains.

Consultation and dissent are first-class records

Every scenario names the decision body, question, rule, participants, and whether dissent was retained. Internal faction blocs respond separately, preventing a faction from being represented as a single mind.

Burden and dependency are visible but not moralized

Baseline relationships publish relative coordination burdens and bounded dependency statements. Turn previews show before-and-after burden categories and dependency levels with explanations. These fields describe institutional load and reliance, not virtue, loyalty, power, or human worth.

Affected communities and corrections shape the turn

Every response option records at least one affected-community effect, safeguard, and review trigger. Every option also records a correction so that unsupported attribution, overbroad claims, or scope confusion can be repaired without deleting history.

The console is local and deterministic

The /campaign page embeds the network and campaign records as inert JSON. JavaScript reads those records, builds deterministic next-turn previews, commits multiple turns in memory, reconstructs state on undo, and exports either one previewed turn or the complete session locally. A 27-row state board exposes each current relationship version, lifecycle stage, domain posture, burden, dependency, consultation state, evidence confidence, and community impact; a versioned history explains which response and reason codes produced every committed turn. The interface does not use local storage, analytics, accounts, fingerprints, demographic input, external APIs, or persistent identity profiling.

Mission content now supports alliance-centered play

Twelve mission briefs cover mediation, humanitarian access, source protection, rumor correction, deconfliction, oversight, burden sharing, lawful refusal, disengagement, and reintegration. Each contains uncertainty, a nonviolent path, and a safety boundary against real operational wrongdoing or coercive recruitment guidance.

Decisions or Recommendations

• Keep the 12-faction and 27-relationship baseline immutable within a campaign turn; exported turns should append to history in a future package rather than mutate the reference dataset silently.
• Require every future relationship transition to remain reason-coded, evidence-linked, reversible, domain-specific, and correction-aware.
• Preserve internal blocs, affected-community safeguards, and dissent in every scenario template.
• Never add a universal alignment, threat, trustworthiness, loyalty, dangerousness, or recruitability score.
• Keep campaign input fictional and institutional. Do not accept real-person identifiers, protected characteristics, medical status, or real-world operational targets.
• In a later round, add deterministic branch comparison and replay so two exported response sequences can be compared from the same immutable baseline.

Risks and Limitations

• The nine stress events are curated design examples; they do not establish balance, completeness, or entertainment quality.
• Relative burden and dependency indexes are fictional design values, not real economic or political measurements.
• Browser-local export proves a technical path only; it does not prove that unfamiliar designers understand the model.
• Native Firefox, native assistive-technology speech output, unrestricted external-host browser testing, field performance, and production-host evidence remain unavailable.
• Real-world alliance claims in source reports remain governed by their review states and require current authoritative verification before reuse.

Validation Performed

• Validated alliance-network.json, campaign-state.json, campaign-turn-example.json, campaign-record-example.json, and all declared schemas: 76/76 schema records and 20/20 canonicalization vectors passed.
• Checked 12 faction IDs, 27 relationship IDs, 12 baseline mission IDs, nine scenario IDs, 27 response IDs, 16 reason codes, 27 baseline state records, and 12 campaign mission IDs for uniqueness and referential integrity: 14/14 campaign-state checks passed.
• Checked every response for evidence links, consultation, reversible version increments, reason codes, internal-bloc responses, community safeguards, corrections, and a safe mission brief.
• Exercised preview, commit, two-turn append, undo, state reconstruction, turn and session export, 27-row state-board rendering, lifecycle distribution, scenario deep links, responsive containment, and zero runtime requests or storage writes: 7/7 campaign-browser groups passed.
• Preserved the shell contract: 20/20 layout checks and 27/27 density checks passed, with .menu-strip as the sole sticky surface.
• Verified 355/355 source hashes, 99/99 UAI mirrors, 239 pointer records, 4,808 local documentation links, 3,152 heading anchors, and 983/983 documentation checksums.
• Passed 567/567 static checks, 15/15 general browser fixtures, 7/7 alliance-browser groups, 22/22 isolated Apache checks, 59/59 controlled-edge checks, 93 accessibility-structure routes with zero deterministic findings, and 10/10 delivery budgets.
• Re-ran finalization at the same timestamp with zero differences, then verified a flat archive and fresh extraction with 1,642/1,642 byte-identical files, zero nested archives, and zero compiled Python bytecode.

These checks establish deterministic repository and harness behavior only. They do not establish human comprehension, entertainment value, geopolitical accuracy, native Firefox behavior, native assistive-technology speech output, field performance, or production readiness.

Memory References

• campaign-state.uai
• alliance-network.uai
• mission-design.uai
• progress.uai
• architecture.uai
• test-plan.uai
• memory.uai

Related Durable Documents

• [Alliance, Faction, and Network World-System Integration Report](alliance-faction-and-network-world-system-integration-report.md#findings)
• [Interface Density and Navigation Polish Report](interface-density-and-navigation-polish-report.md#findings)
• [Claim-Level Review and Comparative Fairness Audit](claim-level-review-and-comparative-fairness-audit.md#findings)
• Split-Memory Architecture

Supersession Status

Current for IARPG-OPS-2 2.0.15-wip. A later branch-and-replay engine may supersede the active-tab undo behavior while preserving this report, the stable machine-record identities, versioned export history, and the prohibition on global moral or personal-risk scores.