Work in progress IARPG-OPS-2 2.0.21-wip

Global publication search

Search the operations design system

Type to search standards, missions, roles, authorities, reports, sources, pages, schemas, and UAI memory.

Deterministic branch comparison · browser local

Compare the choices.
Replay the evidence.

Load two or more campaign records that share the immutable 2.0.16-wip baseline. The archive reconstructs every turn, exposes where relationships diverged, and preserves the source bytes—including invalid records—without uploading or silently repairing anything.

Direct answer

What is the Campaign Branch Archive?

It is a browser-local comparison workspace for fictional IARPG campaign records. It validates each record against the published contract, replays every known turn from the same immutable baseline, assigns neutral aliases, and shows relationship, domain, consultation, evidence, correction, and community-consequence differences. It does not upload files, infer identities, or calculate a universal friend/enemy or morality score.

Input
Two or more campaign-record JSON files
Comparison
Portable JSON contract
Invalid records
Quarantined and downloadable unchanged
Persistence
None unless explicitly downloaded

Comparative scenario method

Branches expose disagreement
instead of hiding it.

The archive is a comparative model: it reconstructs each branch from the same fictional baseline, then exposes where decisions, evidence, domains, corrections, internal responses, and consequences diverge.

Campaign archive workspace

Import locally.
Compare transparently.

Branch aliases are generated by import order, never from filenames, player names, organizations, or other identity signals. Select any committed turn as a replay return point before comparing.

Local inputs

Add campaign records

Up to 8 files

Ready. Add at least two campaign records or load the published examples.

Preservation contract

Known fields are validated and replayed. Unknown extension fields remain in the preserved original. Invalid input is never overwritten, repaired, relabeled from source identity, or discarded.

Valid branches0
Quarantined0
Divergent links0
Divergent domains0

Imported records

Branch shelf

Each valid branch exposes a return-point selector. Invalid records remain downloadable from their unchanged byte sequence.

No branches loaded yet.

Use the local file picker or load the two published examples to inspect the deterministic comparison workflow.

Safe branch-building briefs

Six ways to make
histories diverge.

These fictional briefs create meaningful campaign differences through consultation, lawful refusal, relief coordination, mandate revision, oversight, and reintegration—not real-world operational wrongdoing.

COALITION MEDIATION

The Fourth Draft

Two campaign branches preserve the same coalition but reach different consultation and burden-sharing arrangements after a mandate change.

Read the safe brief
Objective
Compare the branches turn by turn and draft a reversible mediation option that records dissent without forcing one political interpretation.
Player decisions
Which divergence needs mediation · Which domain remains in scope · Whose dissent must be recorded · What evidence permits a return
Rights safeguards
Equal evidence burden · Accessible dissent record · No retaliation for abstention
Partial outcome
The coalition keeps a narrow consultation channel even if burden sharing remains disputed.

Fictional institutional mediation only; no covert contact, coercion, targeting, or real-world operational guidance.

RELIEF COORDINATION

Two Routes, One Relief Window

One branch uses a monitored access bridge while another relies on neutral handoff points during the same public-service emergency.

Read the safe brief
Objective
Identify which evidence, consultation, and community safeguards explain the different relief arrangements without declaring one faction trustworthy in every domain.
Player decisions
Which route conditions are comparable · Which services are essential · How to record local consent · What triggers suspension or restoration
Rights safeguards
Beneficiary participation · Minimum-necessary data · Independent correction channel
Partial outcome
A reduced relief schedule remains viable while the wider authority dispute continues.

Fictional relief governance only; no real routes, evasion, smuggling, targeting, or weapons guidance.

OVERSIGHT DISPUTE

The Dissent Ledger

Parallel branches disagree over whether to pause a liaison, use an independent trustee, or continue essential service under external remedy supervision.

Read the safe brief
Objective
Reconstruct the evidence and oversight choices behind each branch and produce a correction-aware comparison for public review.
Player decisions
Which evidence was decisive · Which authority can review the dispute · Which service can continue · What remains contested
Rights safeguards
Source protection · Affected-community remedy · Independent appeal
Partial outcome
The parties agree on correction and review procedure without agreeing on intent.

Fictional oversight and evidence review only; no surveillance targeting, identity discovery, or operational intrusion guidance.

MANDATE CHANGE

Mandate at the Fork

An election changes one member mandate, creating branches for narrow continuity, member-led continuity, and orderly de-integration.

Read the safe brief
Objective
Compare how each branch changes lifecycle, burden, dependency, and consultation while keeping the faction internally plural.
Player decisions
Which domains remain authorized · Which members may continue · How costs shift · What permits future reintegration
Rights safeguards
Public mandate visibility · Minority and dissent record · Time-boxed review
Partial outcome
A narrower domain compact survives while the wider coalition mandate is renegotiated.

Fictional institutional mandate analysis only; no real political persuasion, targeting, or interference guidance.

INSTITUTIONAL REFUSAL

Refusal Is a Record

Different branches treat refusal as disavowal, independent review, or a condition for later reintegration rather than automatic betrayal.

Read the safe brief
Objective
Compare the evidence and safeguards behind each refusal path and identify a non-punitive return point.
Player decisions
Whether the claim is established · What conduct is actually authorized · Which support remains available · What reintegration requires
Rights safeguards
Due process · No retaliation for refusal · Voluntary participation
Partial outcome
The institution rejects the claimed authority while preserving a voluntary support and review path.

Fictional institutional refusal and support only; no recruitment, coercion, clandestine contact, or target selection.

REINTEGRATION

Return Without Erasure

A branch comparison reveals different conditions for returning a disengaged actor or member institution to a bounded cooperative role.

Read the safe brief
Objective
Build a reintegration option that preserves prior harm, correction history, consent, oversight, and the right to exit.
Player decisions
Which prior version remains authoritative · Which conditions have been met · What access is restored · What triggers renewed review
Rights safeguards
Voluntary reintegration · Independent monitoring · Accessible appeal and exit
Partial outcome
A limited service relationship resumes while higher-risk domains remain suspended.

Fictional reintegration governance only; no real-group joining instructions, coercive persuasion, or vulnerability scoring.

Machine-readable contract

Portable records.
Bounded claims.

The published examples demonstrate the contract, including preserved unknown extension fields. They do not prove production readiness, geopolitical accuracy, human comprehension, or entertainment quality.

Connected tools and standards

Explore the wider AI ecosystem.