IARPG-OPS-1 online Intelligence operations standard Fictional missions · neutral authorities
IARPG.COM INTELLIGENCE AGENT ROLE PLAYING GAME

Roadmap / support boundary

What exists now.
What remains future work.

The roadmap keeps the current public standard separate from planned validators, implementation profiles, game integrations, telemetry studies, and research experiments.

Open current standards Read changelog

Publication roadmap

Release claims stay inside the current column.

Items move only when the human record, machine assets, validator behavior, documentation, UAI memory, and release trail agree.

01
SHIPPED PUBLIC SURFACE

Current

  • IARPG-OPS-1 version 1.0.0
  • 26 canonical standards records
  • Search and filtering by category, status, and mission phase
  • Stable HTML and JSON record routes
  • Mission brief JSON Schema and Hollow Signal example
  • Local Level A/B/C mission validator
  • Governance, roadmap, and changelog pages
  • Long-term `/docs/standards/` and UAI memory copies
02
HARDENING AND FIXTURES

Next

  • Additional conforming and non-conforming mission fixtures
  • Field-level validator references to specific canonical records
  • Printable mission-review packet
  • Record-level revision history
  • Accessibility review of complex standards workbenches
  • More explicit role-specific interface profiles
  • Release-check automation for deep report anchors
03
NOT CURRENT SUPPORT

Planned

  • Mission package export with attached conformance evidence
  • Schema profiles for operations, sources, evidence, and debrief products
  • Game-engine implementation profiles
  • Reference API routes for validation and catalog discovery
  • Version-to-version migration notes
  • Public issue and proposal workflow
  • Optional conformance pack download
04
EXPLORATORY ONLY

Research track

  • Agent-based mission and economy simulation
  • Counterintelligence adversarial test fixtures
  • Evidence graph and custody visualization
  • Cross-role information asymmetry measurements
  • Synthetic-source reliability and fail-forward telemetry
  • Internationalization of public standards records
  • Formal certification feasibility study

Graduation gates

Future work becomes current only with proof.

A feature is not treated as shipped because it appears in research, a roadmap, a mockup, or a single page. Publication requires aligned implementation evidence.

RECORD

Canonical requirement

The affected standard states the supported behavior and its boundaries.

MACHINE

Schema or route evidence

JSON documents, examples, or discovery records expose the same support claim.

TEST

Repeatable validation

A test, fixture, validator rule, or release check demonstrates the behavior.

RELEASE

Dated public trail

The changelog and version metadata identify when the support boundary changed.

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.