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

Operational Neutrality and Authority

Authorities define mandates, resources, constraints, and customers; the system does not assign permanent hero or villain status.

Normative requirements

What conforming mission design must express.

01
MUST required for conformance

Every operation identify the sponsoring authority, customer, mandate, and jurisdiction before player acceptance.

02
MUST required for conformance

No authority receive a permanent good, evil, hero, or villain flag in canonical game logic.

03
SHOULD recommended unless a documented reason applies

Conflicting authorities expose different objectives, constraints, and definitions of success without hiding their operational interests.

04
MAY optional supported behavior

Authorities cooperate temporarily when requirements overlap, even when their long-term interests conflict.

Mission lifecycle fit

Where this record applies.

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