IARPG-OPS-2 · 2.0.4-wip Intelligence operations design system Fictional missions · neutral authorities
IARPG.COM INTELLIGENCE AGENT ROLE PLAYING GAME
Work in progress IARPG-OPS-2 2.0.4-wip

Global publication search

Search the operations design system

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

IARPG Mission Design Workbench

Build a complete operation without sending the draft anywhere.

Drafts remain in this browser’s local storage. Import JSON, load the complete example, validate continuously, print the brief, and export a Level A–D mission record.

Local-only draftNo account · no API call · no external transmission
DraftUntitled operationNot saved

Stage 01 / direction

Authority

Select or name the fictional organization sponsoring the operation. Authority defines resources, constraints, jurisdiction, and desired effect—not moral alignment.

FOUND-03 Neutral Authority Profile →

Stage 02 / direction

Customer

Identify the decision-maker or operating body that will use the intelligence.

FOUND-04 Intelligence Customer Requirements →

Stage 03 / direction

Mandate

State what the authority is permitted and expected to do.

FOUND-02 Mandate, Customer, and Jurisdiction →

Stage 04 / direction

Jurisdiction

Declare where the operation and its authority apply, including negotiated or contested boundaries.

JUR-01 Evidence-Based Jurisdiction →

Stage 05 / tasking

Intelligence requirement

Ask the question the operation must answer. Avoid writing the preferred conclusion into the requirement.

MISS-01 Intelligence Requirement →

Stage 06 / baseline

Known facts

Enter one fact per line. Facts must be currently supported by authoritative game state or reviewed evidence.

EVID-01 Evidence Types →

Stage 07 / baseline

Assumptions

Enter one assumption per line. Assumptions remain visible and reviewable.

ANAL-01 Competing Hypotheses →

Stage 08 / analysis

Competing hypotheses

Provide at least two plausible explanations before collection narrows the field.

ANAL-01 Competing Hypotheses →

Stage 09 / cell

Roles

Select the roles assigned to the operation.

MISS-04 Roles and Information Asymmetry →

Stage 10 / cell

Information asymmetry

Describe what roles know, what is withheld, and why.

ROLE-02 Information Asymmetry Disclosure →

Stage 11 / collection

Collection plan

Enter one collection action or discipline per line.

COLL-01 Collection Discipline Selection →

Stage 12 / collection

Sources

Describe source classes, access, reliability, motivation, and handling boundaries.

HUM-02 Source Reliability and Access →

Stage 13 / play

Player interactions

Enter the meaningful actions players perform, one per line.

GAME-01 Player Interaction →

Stage 14 / access

Cover and access

Explain why the operative can be present and what expected behavior sustains that access.

TRADE-01 Cover Identity and Congruence →

Stage 15 / validation

Evidence thresholds

State what is required before attribution, restriction, settlement, or mission completion.

EVID-02 Provenance and Corroboration →

Stage 16 / validation

Synthetic-source policy

Generated language may provide claims but cannot create authoritative mission state.

AI-03 Synthetic Source Claim Packets →

Stage 17 / protection

Compromise indicators

Enter observable signs that access, source safety, communications, or evidence custody may be compromised.

MISS-07 Compromise and Abort Handling →

Stage 18 / protection

Abort conditions

Enter conditions that require abort, conversion, or emergency extraction.

MISS-07 Compromise and Abort Handling →

Stage 19 / extraction

Extraction

Define primary, alternate, emergency, and remote-debrief extraction options.

MISS-05 Success, Abort, Extraction, and Debrief →

Stage 20 / debrief

Debrief deliverable

Define the final intelligence product and what uncertainty, source impact, cover impact, access, and follow-on work it preserves.

DEBRIEF-01 Debrief Product Contract →
01 / 20

Connected tools and standards

Explore the wider AI ecosystem.