IARPG-OPS-2 · 2.0.12-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.12-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.

Start here / site orientation

One game idea.
Five connected ways to explore it.

IARPG is the Intelligence Agent Role Playing Game: a fictional international intelligence-game concept and the open design system used to define, test, explain, and research its operations. This guide separates what exists on the site now from the persistent multiplayer game that remains a future ambition.

Take the 10-minute tour Open a complete mission

Direct answer

What exactly is iarpg.com?

iarpg.com is the public home of IARPG—Intelligence Agent Role Playing Game. It currently combines a fictional international intelligence role-playing game concept, the IARPG-OPS-2 mission-design standard, complete example operations, browser-local creation and review tools, and an international research archive. It is not yet a downloadable persistent multiplayer or VR game.

Game concept
Roles, authorities, tasking, evidence, extraction, and debrief
Available examples
6 complete fictional operations
Design publication
70 canonical standards plus schemas and local tools
Release truth
2.0.12-wip · work in progress · no live MMO claim

Current reality

What is available now—and what is not.

The site contains a substantial working publication, but the publication and the future game are not the same thing. This boundary should remain visible on every visitor path.

AVAILABLE ON THIS SITE

Use these today

  • Game premise and player loop: tasking, cover, collection, analysis, delivery, extraction, and debrief.
  • 6 complete mission examples: briefs, evidence, roles, simulation states, outcomes, and standards.
  • Browser-local workbenches: create, simulate, compare, validate, merge, replay, review, migrate, and preview publication.
  • 70 canonical standards: human pages and machine-readable JSON/schema companions.
  • International research: a 195-country roadmap, regional baselines, methodology, source lineage, and 220 canonical reports.
  • Open access: no account, API key, analytics library, or remote runtime dependency is required for the public reference tools.
NOT A CURRENT LAUNCH CLAIM

Future production ambitions

  • A persistent worldwide multiplayer world with shared live servers.
  • A downloadable native VR or headset game client.
  • Production matchmaking, player accounts, live economy, and social infrastructure.
  • A production AI-character service with live operational authority.
  • Stable-release status: the current package remains work in progress while external host, browser, accessibility, and field-performance gates remain open.

The `/play` route is a reference gateway and release-boundary demonstration. It does not turn the current publication into a live persistent MMO.

Deep research links

The orientation map and plain-language paths are grounded in portal strategy, brand, accessibility, and content-architecture research. The reports remain source-derived and explicitly unverified until their external claims receive claim-level review.

FULL REPORT Fictional Educational RPG Portal Product Strategy Audience paths, product boundaries, and useful first actions. FULL REPORT Fictional RPG Portal Brand Audit Clarity, trust, terminology, and the cost of repeating a logo instead of explaining the product. FULL REPORT Educational RPG Portal Audit Plan A testable plan for comprehension, accessibility, search, and task completion. FULL REPORT Public UX, Accessibility, Search, Mobile, and Cross-Project Navigation Audit Concrete checks for mobile wayfinding, keyboard access, search, and cross-project orientation.

Choose your entry point

Start with the goal you have.

You do not need to read the site in publication order. Pick the path that matches what you are trying to understand or produce.

01 · NEW VISITOR

I want to understand the game concept.

Learn the proposed player loop, evidence-centered decisions, role asymmetry, and what makes this different from a combat-first espionage game.

Read the player-loop guide → 02 · EXPLORER

I want to see a complete example.

Open Port Access Anomaly Investigation and follow the authority, requirement, roles, evidence threshold, state transitions, extraction, and debrief.

Open the first mission → 03 · DESIGNER

I want to create an operation.

Load the reference mission, work through twenty guided design stages, validate the structure, and export a portable mission brief.

Use the Mission Workbench → 04 · REVIEWER

I want to inspect or test a package.

Load a complete local Operation Package, inspect its components, and pass it through simulation, integrity, merge, replay, evidence, debrief, migration, and publication tools.

Open the package workspace → 05 · RESEARCHER

I want the international and institutional research.

Use the Global Intelligence Atlas, fairness method, regional pages, report archive, source lineage, review states, and correction boundaries.

Open the Global Atlas → 06 · IMPLEMENTER

I want schemas and machine records.

Browse JSON Schema, examples, canonicalization rules, discovery files, compatibility records, and explicit conformance limitations without an API key.

Open the developer publication →

The site model

Five layers, one fictional operations system.

Confusion usually comes from treating every page as the same kind of product. Each layer answers a different question and has a different truth boundary.

  1. 01

    Game concept

    What would players do?

    The world, roles, authorities, operations cycle, tradecraft, evidence, social uncertainty, and consequences define the intended role-playing experience.

    Start with the player-loop guide →
  2. 02

    Mission examples

    What does one complete operation look like?

    Six fictional examples turn the abstract model into inspectable mission briefs, evidence packets, role assignments, simulations, outcomes, and debriefs.

    Browse Missions →
  3. 03

    Browser-local laboratory

    How can I build and test it?

    Workbenches run in the browser, use local files or local storage, and produce portable records. They are reference tools, not the persistent game server.

    Open Create →
  4. 04

    Standards and schemas

    What must a conformant implementation declare?

    IARPG-OPS-2 defines fields, state contracts, evidence requirements, role handoffs, review controls, migration behavior, and machine-readable formats.

    Search Standards →
  5. 05

    Research and governance

    Why was the system designed this way?

    Reports, source files, international methodology, editorial policy, validation evidence, UAI memory, and release gates expose reasoning and limitations.

    Open Research →

First 10 minutes

A guided route through the whole idea.

This route gives a first-time visitor the game premise, a concrete mission, a role perspective, a design view, a simulation, and the evidence trail without requiring prior knowledge.

  1. 00–02

    Read the game premise

    Open How the game concept works. Read the direct answer and the Task → Plan → Access → Collect → Validate → Deliver → Extract → Debrief cycle.

  2. 02–04

    Inspect one complete mission

    Open Port Access Anomaly Investigation. Look first at the intelligence requirement, assigned roles, evidence threshold, abort conditions, and extraction plan.

  3. 04–05

    Compare role knowledge

    Open Roles. Notice that field, case, analysis, technical, and liaison perspectives receive different access and responsibilities.

  4. 05–07

    Load the reference design

    Open Create, choose Load example, use the stage rail, and inspect how the operation becomes a structured mission brief.

  5. 07–09

    Run one deterministic branch

    Open Simulate, load a mission, choose a role, make several decisions, and watch the state, meters, reasons, and event log change.

  6. 09–10

    Follow the supporting evidence

    Open Standards, Global Atlas, or Research to see definitions, sources, review status, fairness method, and implementation limits.

Toolchain map

How the browser-local tools fit together.

This publication toolchain is not the player loop. The player loop describes what happens inside a fictional operation; these browser-local tools help a designer or reviewer create, test, inspect, migrate, and publish the operation record. You can use one tool by itself or carry a complete Operation Package through the full review lifecycle.

Inputs, outputs, and recommended use for the IARPG browser-local toolchain
StageUse this pageStart withWhat it produces or explains
DesignMission WorkbenchA concept, imported mission JSON, or the reference exampleA validated Mission Brief and human-readable print view
EvidenceEvidence LabClaims, observations, sources, reliability, and custodyAn Evidence Packet with corroboration and contradiction relationships
SimulateOperations SimulatorA complete example or simulation configurationDeterministic states, reasoned transitions, meters, and event log
AssembleOperation PackageMission, evidence, simulation, debrief, and extension componentsOne portable package and links into every connected tool
VerifyPackage IntegrityAn Operation PackageCanonical component digests and a pass/fail Integrity Report
MergePackage MergeTwo package branchesAn explicit conflict ledger and resolved package without silent overwrite
ReplayRole ReplayRole events and handoffsA UTC-ordered view of what each role knew, sent, withheld, and acknowledged
ResolveEvidence DiffTwo Evidence PacketsCustody, provenance, corroboration, contradiction, and assessment differences
ReviewBatch ReviewMultiple local artifactsDeterministic aggregate and per-artifact conformance results
DebriefDebrief ComposerMission events, findings, consequences, and gapsA structured debrief with confidence, unresolved questions, and follow-on collection
MigrateMigration WorkbenchAn older or incompatible recordA reviewable transformed draft plus preserved original and migration report
PublishPublication PreviewA complete Operation PackageA compact human brief, role packet, evidence index, standards matrix, and checksums

Task finder

Where to go for a specific question.

Use this as a plain-language map when a navigation label or artifact name is unfamiliar.

PLAYHow would a session work?Briefing, role selection, collection, validation, delivery, extraction, and debrief. EXAMPLESShow me finished operations.Six complete examples with different authorities, jurisdictions, evidence, and outcomes. WORLDWhat kind of setting is this?A multipolar fictional world without permanent national or cultural hero-villain alignment. ROLESWhat can different players do?Field, case, analysis, technical, and support or liaison workstations. RULESWhat is required by the standard?Search canonical records by domain, status, code, term, and relationship. TERMSWhat does a term mean?Definitions for operations, evidence, roles, fairness, publication, and memory. GLOBALHow is international coverage handled?Regional baselines, country roadmap, rights review, source diversity, and uncertainty. RESEARCHWhere is the deep supporting material?Canonical reports, source lineage, sections, checksums, review status, and downloads. IMPLEMENTHow do I build against the formats?Schemas, examples, canonical JSON, compatibility, validation, and discovery records. STATUSWhat is actually verified?Pass, fail, and not-tested promotion gates with explicit evidence links. TRUSTHow are claims and corrections governed?Source hierarchy, truth boundaries, review states, fairness, corrections, and citation guidance. FINDI know the topic, not the page.Search standards, missions, roles, authorities, reports, sources, schemas, pages, and UAI memory.

Core vocabulary

Nine terms that unlock the site.

The full glossary contains more definitions, but these explain most page and tool labels.

Operation
The central design unit: one authority-sponsored effort from requirement and planning through collection, decision, extraction, and debrief.
Authority
The fictional institution sponsoring or permitting an operation. It defines mandate, jurisdiction, resources, constraints, and oversight—not universal morality.
Customer
The person or body that needs intelligence to make a decision. The customer is distinct from the authority and from the player roles collecting or analyzing information.
Intelligence requirement
The decision-oriented question the operation must answer, including deadline, uncertainty, evidence threshold, and constraints.
Mission Brief
The structured design contract for one operation: direction, baseline, roles, interactions, collection, evidence, risk, exit, and debrief.
Evidence Packet
A set of claims and supporting or contradicting items with origin, reliability, confidence, provenance, custody, jurisdiction, and review state.
Operation Package
The portable container that carries the mission brief, evidence, simulation, debrief, conformance, manifests, and extensions through connected tools.
Conformance level
A structural completeness label: A Briefable, B Playable, C Auditable, or D Simulatable. It is not a certification of truth, legality, safety, or fun.
UAI memory
The project’s structured current-state and handoff memory. It explains repository decisions and continuity; it is not a fictional in-game intelligence database.

Privacy, safety, and release boundary

Explore freely.
Keep the claims precise.

Public tools use local browser storage and explicit file import or export. The site does not load third-party analytics or remote UI libraries. Content is fictional game and standards design, not actionable real-world wrongdoing instruction. The release remains WIP, and local validation is not proof of live indexing, production hosting, accessibility certification, or a shipped MMO.

Read the Answer CenterReview the evidence methodInspect release gatesReview runtime boundaries

Recommended next step

See the concept become a complete operation.

Open one mission first. Then return to Create or Simulate once the authority, requirement, roles, evidence threshold, and extraction conditions make sense.

Open Port Access Anomaly Investigation Read the game concept

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.