{
  "code": "MISS-05",
  "slug": "success-abort-extraction-and-debrief",
  "title": "Success, Abort, Extraction, and Debrief",
  "category": "Mission Design",
  "status": "Current",
  "version": "2.0.4-wip",
  "summary": "Operations define success beyond completion, permit professional aborts, and require extraction and debrief as first-class gameplay.",
  "keywords": [
    "success",
    "abort",
    "extraction",
    "debrief",
    "partial success",
    "consequence"
  ],
  "mission_phases": [
    "Deliver",
    "Extract",
    "Debrief"
  ],
  "canonical": "https://iarpg.com/standard/success-abort-extraction-and-debrief",
  "json": "https://iarpg.com/records/success-abort-extraction-and-debrief.json",
  "requirements": [
    {
      "level": "MUST",
      "text": "Define complete success, partial success, professional abort, compromised extraction, and failed debrief outcomes."
    },
    {
      "level": "MUST",
      "text": "Record why the operation ended and which intelligence gaps remain."
    },
    {
      "level": "SHOULD",
      "text": "Reward source protection, cover preservation, evidence quality, and decision usefulness independently of objective completion."
    },
    {
      "level": "MAY",
      "text": "Convert an unsuccessful collection attempt into future access, counterintelligence warning, or environmental discovery."
    }
  ],
  "research": [
    {
      "label": "Operational egress and contingencies",
      "href": "/docs/report/operational-directive-analog-tradecraft-and-counter-surveillance-in-high-density-virtual-urban-environments#operational-egress-and-contingencies",
      "note": "Egress and contingency planning as part of the operation."
    },
    {
      "label": "Mitigating zero-payout frustration",
      "href": "/docs/report/systemic-implementation-of-delusional-ai-and-hallucinated-mission-vectors-in-virtual-reality-mmorpgs#mitigating-the-frustration-of-zero-payout",
      "note": "Fail-forward value and meaningful secondary outcomes."
    }
  ],
  "related": [
    "mission-lifecycle",
    "provenance-confidence-and-corroboration",
    "versioning-change-control-and-telemetry"
  ],
  "release": "IARPG-OPS-2",
  "revised_utc": "2026-07-20T12:04:07Z",
  "purpose": "Turn an intelligence requirement into a playable, reviewable operation with explicit states, roles, evidence thresholds, abort conditions, extraction, and debriefing.",
  "rationale": "Structured mission contracts keep narrative, player interaction, and server-authoritative outcomes synchronized.",
  "game_interaction": [
    "Read brief",
    "Assign roles",
    "Plan collection",
    "Select abort conditions",
    "Approve extraction"
  ],
  "inputs": [
    "Intelligence requirement",
    "Known facts",
    "Assumptions",
    "Authority constraints"
  ],
  "outputs": [
    "Mission brief",
    "Role tasking",
    "State machine",
    "Debrief contract"
  ],
  "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.success-abort-extraction-and-debrief.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 MISS-05 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": [
    "Read brief",
    "Assign roles",
    "Plan collection"
  ],
  "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."
    }
  ]
}