IARPG-OPS-2 · 2.0.4-wip Intelligence operations design system Fictional missions · neutral authorities
IARPG.COM INTELLIGENCE AGENT ROLE PLAYING GAME
Work in progress IARPG-OPS-2 2.0.4-wip

Global publication search

Search the operations design system

Type to search standards, missions, roles, authorities, reports, sources, schemas, and UAI memory.

IARPG-MSN-001 · Level D — Simulatable

Port Access Anomaly Investigation

Determine whether repeated privileged export events reflect insider disclosure, automation failure, or fabricated traffic intended to trigger a purge.

Authority
Port Meridian Civic Continuity Office
Customer
Metropolitan continuity council
Jurisdiction
Port Meridian civil port systems
Release
IARPG-OPS-2

Human-readable brief

Direction and mandate

Authority
Port Meridian Civic Continuity Office
Customer
Metropolitan continuity council
Mandate
Collect and assess information within the declared fictional jurisdiction and report uncertainty without forcing a preferred conclusion.
Jurisdiction
Port Meridian civil port systems
Intelligence requirement
Determine whether repeated privileged export events reflect insider disclosure, automation failure, or fabricated traffic intended to trigger a purge.
Evidence threshold
Deliver an assessment only after two independent evidence classes corroborate the leading explanation.
Extraction plan
Extract through the public maintenance corridor or abort to remote debrief if cover integrity falls below 35.
Debrief deliverable
An assessment that separates observation, source report, interpretation, hypothesis, confidence, dissent, source impact, cover impact, and follow-on requirements.

Known facts

  • A triggering anomaly or request has been logged.
  • The authority has access to some but not all relevant records.
  • At least two explanations remain plausible.

Assumptions

  • Current system clocks are synchronized within the published tolerance.
  • Declared access records have not yet been proven complete.

Competing hypotheses

  • Administrative or technical failure
  • Authorized but poorly documented activity
  • Deliberate disclosure or manipulation
  • Fabricated evidence intended to redirect attention

Role contract

Roles and information asymmetry

ASSIGNED

Operative

  • Role-specific tasking
  • Authorized evidence subset
ASSIGNED

Handler

  • Role-specific tasking
  • Authorized evidence subset
ASSIGNED

Intelligence Analyst

  • Role-specific tasking
  • Authorized evidence subset
ASSIGNED

Technical Operator

  • Role-specific tasking
  • Authorized evidence subset

Collection and interaction

What the players do

Collection plan

  • Access-control review
  • Witness interview
  • Technical log collection
  • Open-source schedule comparison

Player interactions

  • Review tasking
  • Establish access
  • Collect evidence
  • Mark contradiction
  • Request corroboration
  • Choose continue, convert, or abort
  • Complete extraction and debrief

Compromise and abort

  • Unexpected access challenge
  • Unexplained route change
  • Source behavior inconsistent with prior handling
  • Evidence item lacking provenance
  • Role handoff not acknowledged
  • Abort: Cover integrity below 35
  • Abort: Source safety cannot be maintained
  • Abort: Jurisdiction is exceeded
  • Abort: Required evidence custody cannot be preserved

Evidence Packet JSON

EVP-001

OBSERVATION

EV-001

Origin: player observation

Provenance: role event log

OBSERVED
SOURCE REPORT

EV-002

Origin: declared source

Provenance: source handling record

SOURCE_CLAIM
CONTRADICTION

EV-003

Origin: analytic comparison

Provenance: EV-001,EV-002

CONTRADICTION
Download complete mission package ↗

Simulation configuration

Deterministic state contract

TaskPlanAccessCollectValidateDeliverExtractDebrief

Seed: hollow-signal

Expected terminal states: Debrief, Abort, Compromise

Load simulator →

Supporting standards

Canonical implementation records

Full reports

Research lineage and limitations

Connected tools and standards

Explore the wider AI ecosystem.