{
  "code": "GOV-01",
  "slug": "versioning-change-control-and-telemetry",
  "title": "Versioning, Change Control, and Telemetry",
  "category": "Governance & Safety",
  "status": "Current",
  "version": "2.0.4-wip",
  "summary": "Public standard records are versioned, citable, machine-readable, and changed through visible release notes and test evidence.",
  "keywords": [
    "governance",
    "versioning",
    "changelog",
    "roadmap",
    "telemetry",
    "conformance",
    "release"
  ],
  "mission_phases": [
    "Task",
    "Debrief"
  ],
  "canonical": "https://iarpg.com/standard/versioning-change-control-and-telemetry",
  "json": "https://iarpg.com/records/versioning-change-control-and-telemetry.json",
  "requirements": [
    {
      "level": "MUST",
      "text": "Every standard record publish code, version, status, canonical URL, summary, requirements, related records, and research links."
    },
    {
      "level": "MUST",
      "text": "Breaking changes increment the major version and retain the superseded public record."
    },
    {
      "level": "MUST",
      "text": "Current, guidance, experimental, planned, and retired states remain visibly distinct."
    },
    {
      "level": "SHOULD",
      "text": "Mission implementations attach validation evidence and telemetry before claiming conformance."
    },
    {
      "level": "MAY",
      "text": "Publish machine-readable catalogs, schemas, examples, and discovery manifests beside human-readable pages."
    }
  ],
  "research": [
    {
      "label": "Telemetry and live-ops tuning",
      "href": "/docs/report/justice-system-and-warrant-escalation-for-rogue-intelligence#telemetry-and-live-ops-tuning",
      "note": "Instrumentation and controlled regional pilots."
    },
    {
      "label": "Simulation and validation plan",
      "href": "/docs/report/monetary-architecture-genesis-allowance-and-economic-stabilization#simulation-validation-plan",
      "note": "Shock testing and acceptance criteria before launch."
    }
  ],
  "related": [
    "operational-neutrality-and-authority",
    "safety-and-fiction-boundary",
    "mission-brief-contract"
  ],
  "release": "IARPG-OPS-2",
  "revised_utc": "2026-07-20T12:04:07Z",
  "purpose": "Maintain versioned publication, telemetry, accessibility, fiction boundaries, and reviewable change control.",
  "rationale": "A public standard needs explicit status, migration, limitations, and safety boundaries to remain durable.",
  "game_interaction": [
    "Inspect version",
    "Review reason code",
    "Choose comfort option",
    "Read change notice"
  ],
  "inputs": [
    "Release record",
    "Telemetry",
    "Accessibility profile"
  ],
  "outputs": [
    "Change log",
    "Migration note",
    "Conformance report"
  ],
  "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.versioning-change-control-and-telemetry.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 GOV-01 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": [
    "Inspect version",
    "Review reason code",
    "Choose comfort option"
  ],
  "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."
    }
  ]
}