Collection
Collection Discipline Selection
HUMINT, SIGINT, OSINT, cyber, imagery, geospatial, and technical methods produce different evidence and exposure profiles.
IARPG-OPS-2 · 2.0.11-wip
Filter by mission phase, role, authority type, collection discipline, interaction, evidence requirement, conformance level, and implementation maturity. Every human-readable record has a matching JSON document.
Direct answer
The catalog contains canonical, human-readable requirements for fictional intelligence operations and matching JSON records for machine use. It covers mission direction, authorities, roles, collection, evidence, source handling, simulation, interfaces, review, migration, integrity, and publication, with explicit conformance and implementation boundaries.
70 records shown
Collection
HUMINT, SIGINT, OSINT, cyber, imagery, geospatial, and technical methods produce different evidence and exposure profiles.
Collection
Human sources are relationships with access, motivation, reliability, vulnerability, and independent agency.
Collection
Defines reliability, access, motivation, corroboration, handling restrictions, and change over time for sources.
Counterintelligence
Counterintelligence identifies compromise through competing explanations, evidence provenance, access analysis, behavioral change, and controlled tests.
Counterintelligence
Defines anomaly intake, suspect files, corroboration, protective actions, warrant thresholds, and closure.
Evidence & Analysis
Analysis compares multiple explanations and records what evidence would discriminate among them.
Evidence & Analysis
The game separates what was observed, what a source reported, what an analyst inferred, and what explanation is being tested.
Evidence & Analysis
Confidence is earned through source context, provenance, independence, consistency, and discriminating evidence.
Evidence & Analysis
Defines custody, transformation, duplication, access, and handoff events for evidence packets.
Evidence & Analysis
Defines explicit contradiction relationships, review states, resolution, and preserved dissent.
Evidence & Analysis
Compare Evidence Packets, identify changed provenance and custody, and preserve unresolved disputes until an explicit resolution is recorded.
Foundation
Defines the machine-readable authority profile used by the directory and mission workbench.
Foundation
Authorities define mandates, resources, constraints, and customers; the system does not assign permanent hero or villain status.
Foundation
Operational authority is bounded by who requested the work, where it applies, what methods are permitted, and what review follows.
Foundation
Defines the minimum public profile for a fictional authority without moral-alignment labels.
Foundation
Defines how a customer states the decision, deadline, acceptable uncertainty, and dissemination boundary behind a requirement.
Governance & Safety
Defines equivalent access to operational information, controls, motion settings, and non-VR participation.
Governance & Safety
Review a local deterministic input set and publish aggregate plus per-artifact structural results without external transmission.
Governance & Safety
Public standard records are versioned, citable, machine-readable, and changed through visible release notes and test evidence.
Governance & Safety
Defines versioning, migration, deprecation, compatibility windows, and preservation of prior mission records.
Governance & Safety
Require explicit pass, fail, or not-tested evidence for every gate before removing the WIP suffix and incrementing the minor version.
Governance & Safety
Public material stays fictional, game-system focused, and clearly separated from real-world medical, legal, investigative, or tactical authority.
Governance & Safety
Defines privacy-conscious event telemetry, fairness indicators, operational health metrics, and change review.
Governance and Migration
Migrates OPS-1, early OPS-2, isolated component records, and current Operation Packages without silently discarding fields.
Interaction & Interfaces
Social stealth evaluates behavioral congruence, access, timing, environment, and explanation rather than invisibility or costume alone.
Interaction & Interfaces
Embodied VR, desktop, mobile, and browser roles coordinate through complementary information and actions.
Interface and Accessibility
Defines named, exportable, recoverable local drafts for missions, evidence packets, simulations, debriefs, packages, comparisons, and migration reports without accounts or server transmission.
Mission Design
Builds a debrief from mission, evidence, role handoffs, extraction state, and simulation events while separating facts, reports, interpretations, hypotheses, assessments, and decisions.
Mission Design
Defines the minimum human- and machine-readable output after success, partial success, conversion, abort, compromise, or failure.
Mission Design
Every mission begins with a question or decision need that collection and analysis are meant to support.
Mission Design
A mission brief is a reviewable contract connecting authority, requirement, roles, constraints, evidence thresholds, abort conditions, and extraction.
Mission Design
Operations progress through explicit lifecycle states from tasking to debrief, with observable transitions and recoverable failure states.
Mission Design
Operative, handler, analyst, technical, liaison, and support roles receive different information and actions while contributing to one requirement.
Mission Design
Operations define success beyond completion, permit professional aborts, and require extraction and debrief as first-class gameplay.
Mission Design
Requires durable UTC event records for consequential mission-state changes.
Mission Design
Defines compromise indicators, decision authority, abort states, conversion, extraction, and recovery.
Package Lifecycle
Recalculate canonical component hashes, validate package manifests, explain mismatches, and preserve failed imports unchanged.
Package Lifecycle
Merge two packages without silent overwrite, preserve unknown extensions, and require explicit resolution for every content conflict.
Publication & Data
Export an indexed saved-work backup, detect duplicates, quarantine malformed records, and selectively restore exact record IDs and payloads.
Publication & Data
Render one package as a compact human brief, role packet, evidence index, simulation expectation, debrief contract, standards matrix, and machine-link set.
Publication and Interchange
Bundles a mission brief, authority, roles, evidence, deterministic simulation, debrief contract, conformance, migration metadata, and component checksums into one portable local record.
Roles & Handoffs
Defines what each role transfers, what must be acknowledged, and who can approve consequential decisions.
Roles & Handoffs
Defines fair role-specific knowledge, withheld information, entitlement, and post-mission disclosure.
Roles & Interaction
Replay what each role knew, transmitted, withheld, acknowledged, or missed in stable UTC order.
Simulation & Conformance
Defines mission states, allowed transitions, guards, effects, event records, and reproducible simulation input.
Simulation & Conformance
Defines Level D — Simulatable and the limits of structural simulation conformance.
Simulation and Testing
Compares two decision branches from the same mission, starting state, evidence packet, authority, role allocation, and visible seed.
Simulation and Testing
Defines build-time and browser-local fixture checks for missions, evidence, simulation, migration, debrief, comparison, and Operation Packages.
Synthetic Sources
Synthetic characters and generated dialogue are visibly disclosed and cannot create authoritative game facts, inventory, permissions, or settlement.
Synthetic Sources
Potentially unreliable tasking is checked against records, world state, source history, logic, location, and mission economics before acceptance.
Synthetic Sources
Defines the machine-readable boundary between generated language, claimed entities or events, verification state, and authoritative game records.
Tasking & Logistics
Currency, access, time, cover, source trust, equipment, transport, and safe locations are operational resources with explicit creation, transfer, lock, and destruction semantics.
Tasking & Logistics
Severity and evidentiary certainty are separate axes; jurisdiction determines who can observe, investigate, restrict, pursue, or review.
Tasking & Logistics
Physical or digital operational handoffs use deterministic states, accessible destinations, tamper evidence, timeouts, and reviewable settlement.
Tasking & Logistics
Verified tasking uses engine-backed terms and settlement; unverified tasking exposes disclosed counterparty and deception risk.
Tradecraft
Defines channel purpose, authentication, delay, compromise indicators, fallback, and communication records at a game abstraction level.
Tradecraft
Cover is a persistent system of identity, access, behavior, records, competence, relationships, and exposure—not a costume slot.
Tradecraft
Surveillance is represented as pattern recognition, route pressure, environmental observation, and exposure management within fictional game spaces.
Tradecraft
Operational information moves through role-aware channels with explicit need-to-know boundaries, delivery state, and exposure cost.
Tradecraft
Defines how repeated inconsistencies, exposure, competence gaps, and relationship damage degrade a cover and how it may be repaired.
Data and Portability
Defines the IARPG-CJSON-1 bytes used for deterministic content equality, checksums, fixtures, and browser-local handoffs.
Packages and Integrity
Defines a separate exportable integrity record that accompanies an Operation Package without changing the package.
Evidence and Provenance
Records file-based workflow ancestry and declared local role labels without claiming human identity or approval.
Conformance
Defines import, normalization, export, reimport, comparison, and preservation evidence for portable artifacts.
Data and Portability
Defines explicit, digest-bound handoffs among the mission, evidence, simulation, review, migration, and publication tools.
Recovery
Defines non-destructive handling for malformed, unsupported, conflicting, partial, or checksum-failing local artifacts.
Governance
Defines browser-local lifecycle evidence where corrections are new reversal or superseding entries rather than edits.
Governance
Publishes explicit import, export, migration, round-trip, unknown-field, limitation, and fixture evidence by release and artifact type.
Governance
Defines safe, removable evidence for PHP, rewrites, headers, protected paths, assets, JSON delivery, UTC, and writable local storage on the actual host.
Accessibility
Defines an evidence matrix for keyboard, focus, labels, live regions, tables, fallback views, zoom, motion, contrast, mobile, print, and touch.
Clear one or more filters, search a related term, or open the relationship graph.