IARPG-OPS-1 online Intelligence operations standard Fictional missions · neutral authorities
FOUND-02 Current Foundation Version 1.0.0

Mandate, Customer, and Jurisdiction

Operational authority is bounded by who requested the work, where it applies, what methods are permitted, and what review follows.

Normative requirements

What conforming mission design must express.

01
MUST required for conformance

Tasking declare a customer, intelligence requirement, legal or organizational authority, and operating jurisdiction.

02
MUST required for conformance

The mission distinguish authorized methods from prohibited or unsupported methods.

03
SHOULD recommended unless a documented reason applies

Cross-jurisdiction work declare which authority can recognize, deny, contest, or punish an action.

04
MAY optional supported behavior

A mission include compartmented customers whose identities are revealed only when the player has the required access.

Mission lifecycle fit

Where this record applies.

Task Plan 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.