Work in progress IARPG-OPS-2 2.0.32-wip
IARPG Operations design system

Global publication search

Search the operations design system

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

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-2 current WIP portability and publication layer
  • IARPG-OPS-1 version 1.0.0 preserved as the compatibility baseline
  • 70 canonical standards records with stable HTML and JSON routes
  • Six complete missions, six neutral authorities, and eight role workstations
  • Global local search, command palette, relationship graph, and deep report links
  • Mission Workbench, Evidence Lab, and deterministic Operations Simulator
  • Operation Package Workspace with two complete portable fixtures
  • Deterministic Scenario Comparison and normalized difference exports
  • Lossless OPS-1 / early OPS-2 migration with field-by-field reports
  • Structured Debrief Composer and browser-local Saved Work Manager
  • Accessible OPS-1 / OPS-2 Standards Diff and deterministic fixture-test publication
  • Offline package-integrity verification with canonical component SHA-256 reports
  • Conflict-aware package merge with explicit resolution and unknown-extension preservation
  • Multi-role handoff replay and evidence-custody difference resolution
  • Batch conformance review, indexed backup and selective restore, and package publication preview
  • Machine-readable WIP-to-stable promotion gates with pass, fail, and not-tested evidence
  • IARPG-CJSON-1 canonicalization vectors with browser/build parity
  • Portable integrity bundles and non-authenticating provenance envelopes
  • Round-trip laboratory, cross-tool handoff contracts, and non-destructive recovery quarantine
  • Append-only review ledger, compatibility matrix, accessibility evidence, performance report, and removable hosting diagnostics
  • IARPG-CJSON-1 canonicalization vectors with browser/build parity
  • Round-trip laboratory, cross-tool handoff contracts, and non-destructive recovery quarantine
  • Append-only review ledger, compatibility matrix, accessibility evidence, performance report, and removable hosting diagnostics
  • Long-term `/docs/standards/`, original sources, reports, and UAI mirrors
02
HARDENING AND FIXTURES

Next

  • Native Firefox critical-path runtime testing and evidence capture
  • Actual target-hosting smoke-test evidence and removal of the diagnostic endpoint
  • Native assistive-technology review and release-candidate regression pass
03
NOT CURRENT SUPPORT

Planned

  • Optional offline conformance pack containing schemas, records, fixtures, and checksums
  • Game-engine implementation profiles for mission events, role handoffs, and evidence custody
  • Internationalized publication records and localized machine examples
  • Public proposal and issue workflow with attributable change discussion
  • Formal compatibility declarations for stable publishable releases
  • Reference import adapters for common game-design document formats
  • Certification-feasibility study without claiming current certification
04
EXPLORATORY ONLY

Research track

  • Agent-based operation and economy simulations
  • Counterintelligence adversarial test fixtures and deception telemetry
  • Cross-role information-asymmetry measurements
  • Synthetic-source reliability, contradiction, and fail-forward studies
  • Human-factors testing for VR evidence, handoff, and debrief interfaces
  • Operation-package provenance graphs and offline signature models
  • Formal conformance and 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.