IARPG-OPS-1 online Intelligence operations standard Fictional missions · neutral authorities
MISS-04 Current Mission Design Version 1.0.0

Roles and Information Asymmetry

Operative, handler, analyst, technical, liaison, and support roles receive different information and actions while contributing to one requirement.

Normative requirements

What conforming mission design must express.

01
MUST required for conformance

Each assigned role have at least one unique information source, decision, or action that materially affects the operation.

02
MUST required for conformance

Shared mission truth remain server-authoritative even when roles receive incomplete or conflicting views.

03
SHOULD recommended unless a documented reason applies

Role coordination reward concise handoffs, explicit uncertainty, and timely escalation.

04
MAY optional supported behavior

One player occupy multiple low-intensity support roles when population is limited, provided information boundaries remain visible.

Mission lifecycle fit

Where this record applies.

Plan Access Collect Validate Deliver

This list identifies the mission stages where the record is most likely to be implemented or reviewed. It does not prevent the requirement from influencing adjacent phases.

Search and implementation terms

Vocabulary carried by this record.

Supporting research

Deep links into the complete report archive.

The canonical record stays concise. These links preserve the longer argument, design context, limitations, and source lineage in the `/docs/` archive.

Connected tools and standards

Explore the wider AI ecosystem.