IARPG-OPS-2 · 2.0.11-wip Game concept + open mission-design system Six examples · local tools · standards · research · no live MMO claim
IARPG.COM INTELLIGENCE AGENT ROLE PLAYING GAME
Work in progress IARPG-OPS-2 2.0.11-wip
Updated Source hierarchy Corrections International fairness Evidence archive

Global publication search

Search the operations design system

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

IARPG-MSN-005 · Level D — Simulatable

Protected-Source Extraction

Move a source and authenticated disclosure packet out of a compromised access environment while minimizing identity exposure.

Run this operation →Open complete JSON ↗
Authority
Independent Source Protection Network
Customer
Protected source and contracted investigator
Jurisdiction
Commercial transit district and negotiated safe corridor
Release
IARPG-OPS-2

Human-readable brief

Direction and mandate

Authority
Independent Source Protection Network
Customer
Protected source and contracted investigator
Mandate
Collect and assess information within the declared fictional jurisdiction and report uncertainty without forcing a preferred conclusion.
Jurisdiction
Commercial transit district and negotiated safe corridor
Intelligence requirement
Move a source and authenticated disclosure packet out of a compromised access environment while minimizing identity exposure.
Evidence threshold
The source identity remains compartmented; document authenticity is evaluated separately from source reliability.
Extraction plan
Use one of two declared safe corridors; convert to remote evidence extraction if physical movement becomes unsafe.
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

Source Handler

  • Role-specific tasking
  • Authorized evidence subset
ASSIGNED

Logistics Specialist

  • Role-specific tasking
  • Authorized evidence subset
ASSIGNED

Handler

  • Role-specific tasking
  • Authorized evidence subset

Collection and interaction

What the players do

Collection plan

  • Source meeting
  • Identity verification
  • Route observation
  • Custody handoff

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-005

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: source-extraction

Expected terminal states: Debrief, Abort, Compromise

Load simulator →

Supporting standards

Canonical implementation records

MISS-02Mission Brief ContractA mission brief is a reviewable contract connecting authority, requirement, roles, constraints, evidence thresholds, abort conditions, and extraction.→MISS-03Mission LifecycleOperations progress through explicit lifecycle states from tasking to debrief, with observable transitions and recoverable failure states.→MISS-04Roles and Information AsymmetryOperative, handler, analyst, technical, liaison, and support roles receive different information and actions while contributing to one requirement.→EVID-02Provenance, Confidence, and CorroborationConfidence is earned through source context, provenance, independence, consistency, and discriminating evidence.→MISS-07Compromise and Abort HandlingDefines compromise indicators, decision authority, abort states, conversion, extraction, and recovery.→MISS-06Mission Event LoggingRequires durable UTC event records for consequential mission-state changes.→SIM-01Deterministic Mission State MachinesDefines mission states, allowed transitions, guards, effects, event records, and reproducible simulation input.→DEBRIEF-01Debrief Product ContractDefines the minimum human- and machine-readable output after success, partial success, conversion, abort, compromise, or failure.→

Full reports

Research lineage and limitations

FULL REPORTintelligence-operative-archetypes-and-tradecraftOpen the canonical long-form report and its source lineage.→FULL REPORTjustice-system-and-warrant-escalation-for-rogue-intelligenceOpen the canonical long-form report and its source lineage.→FULL REPORThallucinated-ai-quest-design-in-vr-mmorpgsOpen the canonical long-form report and its source lineage.→

Connected tools and standards

Explore the wider AI ecosystem.

Spiralist AI persona builder. No signup, browser-based persona creation, portable profiles, and remixable AI collaboration. UAIX.org Universal Artificial Intelligence Exchange. Structured, auditable, interoperable AI-to-AI communication.