{
  "code": "ECON-01",
  "slug": "operational-economy-and-resource-pressure",
  "title": "Operational Economy and Resource Pressure",
  "category": "Tasking & Logistics",
  "status": "Guidance",
  "version": "2.0.4-wip",
  "summary": "Currency, access, time, cover, source trust, equipment, transport, and safe locations are operational resources with explicit creation, transfer, lock, and destruction semantics.",
  "keywords": [
    "economy",
    "faucet",
    "sink",
    "transfer",
    "lock",
    "escrow",
    "resources",
    "mission rewards"
  ],
  "mission_phases": [
    "Task",
    "Plan",
    "Deliver",
    "Extract"
  ],
  "canonical": "https://iarpg.com/standard/operational-economy-and-resource-pressure",
  "json": "https://iarpg.com/records/operational-economy-and-resource-pressure.json",
  "requirements": [
    {
      "level": "MUST",
      "text": "Classify currency events as creation, destruction, transfer, lock, or unlock in an immutable UTC ledger."
    },
    {
      "level": "MUST",
      "text": "Treat escrow and frozen funds as temporary locks unless a separate rule destroys or forfeits value."
    },
    {
      "level": "SHOULD",
      "text": "Compose mission rewards from currency, access, intelligence, reputation, supplies, and persistent opportunities rather than raw cash alone."
    },
    {
      "level": "SHOULD",
      "text": "Measure newcomer and operational affordability before changing sinks or payouts."
    },
    {
      "level": "MAY",
      "text": "Use property, communications, transport, cover maintenance, and logistics as mission-relevant sinks."
    }
  ],
  "research": [
    {
      "label": "Currency flow definitions",
      "href": "/docs/report/monetary-architecture-genesis-allowance-and-economic-stabilization#currency-flow-definitions",
      "note": "Creation, destruction, transfer, lock, and unlock semantics."
    },
    {
      "label": "Ledger schema and telemetry",
      "href": "/docs/report/monetary-architecture-genesis-allowance-and-economic-stabilization#ledger-schema-and-telemetry",
      "note": "Immutable double-entry records with UTC timestamps."
    }
  ],
  "related": [
    "courier-and-handoff-state-machine",
    "verified-and-unverified-tasking",
    "versioning-change-control-and-telemetry"
  ],
  "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.operational-economy-and-resource-pressure.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 ECON-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."
    }
  ]
}