{
  "code": "TASK-01",
  "slug": "verified-and-unverified-tasking",
  "title": "Verified and Unverified Tasking",
  "category": "Tasking & Logistics",
  "status": "Current",
  "version": "2.0.4-wip",
  "summary": "Verified tasking uses engine-backed terms and settlement; unverified tasking exposes disclosed counterparty and deception risk.",
  "keywords": [
    "verified",
    "unverified",
    "tasking",
    "escrow",
    "reputation",
    "deception",
    "contract"
  ],
  "mission_phases": [
    "Task",
    "Plan",
    "Deliver"
  ],
  "canonical": "https://iarpg.com/standard/verified-and-unverified-tasking",
  "json": "https://iarpg.com/records/verified-and-unverified-tasking.json",
  "requirements": [
    {
      "level": "MUST",
      "text": "Label tasking as verified, authority-reviewed, reputation-backed, or unverified before acceptance."
    },
    {
      "level": "MUST",
      "text": "Verified tasking lock reward terms and use deterministic completion or review rules."
    },
    {
      "level": "MUST",
      "text": "Unverified tasking disclose that objective, reward, or sponsor claims may fail without engine settlement."
    },
    {
      "level": "SHOULD",
      "text": "Expose issuer history, proof of interaction, dispute record, and relevant reputation without presenting them as infallible truth."
    },
    {
      "level": "MAY",
      "text": "Unverified tasking offer higher potential reward or unique access to justify risk."
    }
  ],
  "research": [
    {
      "label": "Quest design: unverified vs verified",
      "href": "/docs/report/social-deception-and-player-generated-fake-quests#quest-design-unverified-vs-verified-contracts",
      "note": "Safety-with-fee versus freedom-with-risk."
    },
    {
      "label": "Trust recovery through escrow and reputation",
      "href": "/docs/report/trust-deception-and-virtual-economies#escrow-verification-and-reputation-systems",
      "note": "Layered trust signals and dispute histories."
    }
  ],
  "related": [
    "mission-brief-contract",
    "mission-claim-verification",
    "courier-and-handoff-state-machine"
  ],
  "release": "IARPG-OPS-2",
  "revised_utc": "2026-07-20T12:04:07Z",
  "purpose": "Define trusted and untrusted tasking, deterministic handoffs, operational resources, jurisdiction, and support systems.",
  "rationale": "Operational logistics must expose risk, settlement, custody, and failure states before a player commits time or collateral.",
  "game_interaction": [
    "Accept tasking",
    "Lock escrow",
    "Carry package",
    "Complete handoff",
    "Review warrant reason"
  ],
  "inputs": [
    "Task contract",
    "Cargo or intelligence packet",
    "Jurisdiction state"
  ],
  "outputs": [
    "Settlement event",
    "Handoff record",
    "Warrant or clearance event"
  ],
  "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.verified-and-unverified-tasking.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 TASK-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": [
    "Accept tasking",
    "Lock escrow",
    "Carry package"
  ],
  "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."
    }
  ]
}