IARPG-OPS-1 online Intelligence operations standard Fictional missions · neutral authorities
EVID-02 Current Evidence & Analysis Version 1.0.0

Provenance, Confidence, and Corroboration

Confidence is earned through source context, provenance, independence, consistency, and discriminating evidence.

Normative requirements

What conforming mission design must express.

01
MUST required for conformance

Every material claim carry provenance, source type, acquisition time, confidence, and reason codes.

02
MUST required for conformance

Independent corroboration be required for mission-defined irreversible actions.

03
SHOULD recommended unless a documented reason applies

Confidence changes reference the specific evidence or contradiction responsible for the update.

04
MAY optional supported behavior

Mission authors define different evidence thresholds for public attribution, operational action, and internal warning.

Mission lifecycle fit

Where this record applies.

Collect Validate Deliver 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.