IARPG-OPS-1 online Intelligence operations standard Fictional missions · neutral authorities

Current public standard / IARPG-OPS-1

From intelligence requirement
to reviewable mission.

Use the shortest path through the current standard: understand the operating model, open the canonical records, compare the mission schema and example, validate a brief locally, and attach the result to the supporting research.

Plain-English definition

A mission-design contract for fictional intelligence operations.

A public game-design standard for fictional intelligence operations, mission interaction, evidence, tradecraft, tasking, and review. It defines what an operation must declare, what players must be able to see and decide, how claims become evidence, how different roles exchange information, and how consequences remain explainable.

Current releaseIARPG-OPS-1
Version1.0.0
Published2026-07-19 UTC
StatusCurrent public baseline

Four-step implementation path

Move from concept
to validator-backed brief.

The publication path mirrors the operation itself: define the question, use the right record, build the mission contract, then review the result against the current baseline.

  1. 01

    Orient

    Start with the intelligence requirement.

    State the decision-oriented question, sponsoring authority, customer, mandate, jurisdiction, and minimum evidence threshold before designing encounters.

    Open MISS-01
  2. 02

    Resolve

    Read the records that govern the mission.

    Use the searchable catalog to resolve role asymmetry, source handling, collection, evidence, cover, counterintelligence, tasking, extraction, and safety requirements.

    Search 26 records
  3. 03

    Build

    Create a structured mission brief.

    Compare the JSON schema and Hollow Signal example, then write the player-facing interaction model: what players observe, manipulate, verify, decide, record, and hand off.

    Open schema and example
  4. 04

    Validate

    Run local structural conformance checks.

    The browser validator checks the current mission contract and reports Briefable, Playable, or Auditable conformance without sending the mission to an external service.

    Run the validator

Mission anatomy

The operation is the central design unit.

A standards-conformant operation connects intelligence purpose to player interaction. It must make the work legible before, during, and after the mission.

01

Direction

Authority, customer, mandate, jurisdiction, intelligence requirement, constraints, and reporting deadline.

02

Preparation

Roles, cover, access, collection disciplines, source plan, communications, contingencies, and abort conditions.

03

Interaction

What players can observe, ask, handle, compare, mark, infer, challenge, protect, move, and hand off.

04

Validation

Provenance, reliability, confidence, contradiction, competing hypotheses, synthetic-source boundaries, and corroboration.

05

Decision

Success states, conversion paths, reversible choices, exposure, reason codes, and authority-specific consequences.

06

Extraction and review

Exit plan, source protection, evidence custody, access survival, debrief product, unresolved gaps, and next collection.

Machine-facing publication

Clean records.
Stable JSON routes.

Human pages and machine records come from the same catalog. Each standard has a stable HTML route, a companion JSON document, related-record links, and deep research references.

Connected tools and standards

Explore the wider AI ecosystem.