{
  "code": "GAME-02",
  "slug": "vr-and-browser-role-interdependence",
  "title": "VR and Browser Role Interdependence",
  "category": "Interaction & Interfaces",
  "status": "Current",
  "version": "2.0.4-wip",
  "summary": "Embodied VR, desktop, mobile, and browser roles coordinate through complementary information and actions.",
  "keywords": [
    "VR",
    "WebXR",
    "browser",
    "handler",
    "analyst",
    "mobile",
    "cross-platform"
  ],
  "mission_phases": [
    "Plan",
    "Access",
    "Collect",
    "Validate",
    "Extract"
  ],
  "canonical": "https://iarpg.com/standard/vr-and-browser-role-interdependence",
  "json": "https://iarpg.com/records/vr-and-browser-role-interdependence.json",
  "requirements": [
    {
      "level": "MUST",
      "text": "Define unique responsibilities for embodied and non-embodied roles within the same mission requirement."
    },
    {
      "level": "MUST",
      "text": "Synchronize authoritative mission state while allowing role-specific latency, visibility, and presentation."
    },
    {
      "level": "SHOULD",
      "text": "Non-VR roles support short sessions, asynchronous continuity, and accessibility without trivializing field decisions."
    },
    {
      "level": "MAY",
      "text": "The system adapt role distribution when a cell has fewer players than available roles."
    }
  ],
  "research": [
    {
      "label": "Asymmetric cross-platform multiplayer",
      "href": "/docs/report/architectural-and-narrative-design-specifications-for-a-vr-first-post-national-espionage-mmo#the-asymmetric-cross-platform-multiplayer-paradigm",
      "note": "Cross-dimensional role design."
    },
    {
      "label": "Mirrored interdependence and collaboration",
      "href": "/docs/report/architectural-and-narrative-design-specifications-for-a-vr-first-post-national-espionage-mmo#mirrored-interdependence-and-collaboration",
      "note": "Complementary roles and shared operation state."
    }
  ],
  "related": [
    "roles-and-information-asymmetry",
    "player-interaction-and-social-stealth",
    "mission-lifecycle"
  ],
  "release": "IARPG-OPS-2",
  "revised_utc": "2026-07-20T12:04:07Z",
  "purpose": "Define what players actually do across VR and browser roles and how information asymmetry is represented accessibly.",
  "rationale": "Distinct roles need complementary information and meaningful actions rather than duplicated screens.",
  "game_interaction": [
    "Observe",
    "Handle object",
    "Mark contradiction",
    "Coordinate handoff",
    "Request corroboration"
  ],
  "inputs": [
    "Role profile",
    "Mission state",
    "Information entitlement"
  ],
  "outputs": [
    "Interaction event",
    "Role handoff",
    "Updated mission state"
  ],
  "state_transitions": [
    {
      "from": "not-applicable",
      "event": "record requirement evaluated",
      "to": "conforming-or-documented-exception"
    }
  ],
  "evidence_and_provenance": [
    "The implementation records the source, UTC event time, mission identifier, responsible role, and reason code for consequential state changes.",
    "Generated dialogue and player interpretation are not stored as authoritative facts without a separate verification event."
  ],
  "ui_requirements": [
    "Show the record code and requirement level at the point of use.",
    "Expose the reason for blocked, failed, escalated, or irreversible actions.",
    "Provide a direct link to the canonical standard and machine-readable record."
  ],
  "accessibility_requirements": [
    "Essential information is available without reliance on color, audio, motion, or a VR-only gesture.",
    "Keyboard, screen-reader, reduced-motion, seated-play, and high-contrast equivalents are documented where the interaction applies."
  ],
  "telemetry_events": [
    {
      "name": "standard.vr-and-browser-role-interdependence.evaluated",
      "required_fields": [
        "event_id",
        "timestamp_utc",
        "mission_id",
        "record_code",
        "result",
        "reason_code"
      ]
    }
  ],
  "abuse_and_exploit_cases": [
    "A participant attempts to omit required context so another role accepts a misleading task.",
    "A generated or user-authored statement is presented as server-authoritative without verification.",
    "A consequential state transition occurs without a durable reason code."
  ],
  "failure_behavior": "Fail closed for irreversible or settlement-bearing actions. Preserve the current state, show the missing requirement, and allow correction or documented exception review.",
  "recovery_behavior": "Restore from the last authoritative event, retain the rejected transition in the audit log, and require a new validated event before continuing.",
  "example_implementation": "A mission interface evaluates GAME-02 before advancing the relevant state and writes the result to the local event log with a UTC timestamp and reason code.",
  "roles": [
    "Operative",
    "Handler",
    "Intelligence Analyst"
  ],
  "authority_types": [
    "Civil administration",
    "Military command",
    "Commercial intelligence service",
    "International verification body",
    "Scientific consortium",
    "Independent investigative network"
  ],
  "collection_disciplines": [],
  "interaction_types": [
    "Observe",
    "Handle object",
    "Mark contradiction"
  ],
  "evidence_requirement": "Reviewable provenance required",
  "conformance_level": "Level B — Playable",
  "implementation_maturity": "Published WIP",
  "related_examples": [
    "port-access-anomaly-investigation"
  ],
  "revision_history": [
    {
      "version": "1.0.0",
      "date_utc": "2026-07-19",
      "note": "Initial IARPG-OPS-1 publication."
    },
    {
      "version": "2.0.1-wip",
      "date_utc": "2026-07-19",
      "note": "Expanded for IARPG-OPS-2 workbench, simulation, evidence, accessibility, telemetry, and machine-readable publication."
    },
    {
      "version": "2.0.2-wip",
      "date_utc": "2026-07-19T16:42:07Z",
      "change": "Reviewed for operation-package lifecycle compatibility and local tool integration."
    },
    {
      "version": "2.0.3-wip",
      "date_utc": "2026-07-19T18:45:50Z",
      "note": "Reviewed for integrity-aware package verification, merge, multi-role replay, custody comparison, batch review, backup, publication preview, and release-promotion workflows."
    },
    {
      "version": "2.0.4-wip",
      "date_utc": "2026-07-20T12:04:07Z",
      "note": "Reviewed for canonicalization, round-trip portability, recovery, provenance, compatibility, accessibility, hosting evidence, and stable-promotion gates."
    }
  ]
}