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

Mission Lifecycle

Operations progress through explicit lifecycle states from tasking to debrief, with observable transitions and recoverable failure states.

Normative requirements

What conforming mission design must express.

01
MUST required for conformance

Represent Task, Plan, Access, Collect, Validate, Deliver, Extract, and Debrief as distinct states or reviewable milestones.

02
MUST required for conformance

Persist accepted brief revision, evidence state, role assignments, and consequence state across transitions.

03
SHOULD recommended unless a documented reason applies

Permit fail-forward transitions when a planned path closes but the intelligence requirement remains answerable.

04
MAY optional supported behavior

Allow parallel collection tasks to converge into a shared validation state.

Mission lifecycle fit

Where this record applies.

Task Plan Access Collect Validate Deliver Extract Debrief

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.