{
  "code": "JUR-01",
  "slug": "evidence-based-jurisdiction-and-warrants",
  "title": "Evidence-Based Jurisdiction and Warrants",
  "category": "Tasking & Logistics",
  "status": "Current",
  "version": "2.0.4-wip",
  "summary": "Severity and evidentiary certainty are separate axes; jurisdiction determines who can observe, investigate, restrict, pursue, or review.",
  "keywords": [
    "jurisdiction",
    "warrant",
    "evidence",
    "severity",
    "certainty",
    "witness",
    "review"
  ],
  "mission_phases": [
    "Collect",
    "Validate",
    "Deliver",
    "Debrief"
  ],
  "canonical": "https://iarpg.com/standard/evidence-based-jurisdiction-and-warrants",
  "json": "https://iarpg.com/records/evidence-based-jurisdiction-and-warrants.json",
  "requirements": [
    {
      "level": "MUST",
      "text": "Track offense severity separately from evidentiary certainty."
    },
    {
      "level": "MUST",
      "text": "Use anomaly, suspect file, confirmed warrant, and active manhunt as distinguishable case states."
    },
    {
      "level": "MUST",
      "text": "Expose reason codes, jurisdiction, evidence basis, review path, and applicable restrictions."
    },
    {
      "level": "SHOULD",
      "text": "Fund bounty outcomes through fines, bonds, seized value, or capped budgets rather than unconstrained currency creation."
    },
    {
      "level": "SHOULD",
      "text": "Provide surrender, appeal, restitution, review, evasion, and lawful resolution paths."
    },
    {
      "level": "MAY",
      "text": "Different jurisdictions recognize or contest the same case differently based on evidence and agreements."
    }
  ],
  "research": [
    {
      "label": "Recommended warrant architecture",
      "href": "/docs/report/justice-system-and-warrant-escalation-for-rogue-intelligence#recommended-warrant-architecture",
      "note": "Dual-axis severity and certainty model."
    },
    {
      "label": "Economy and anti-exploit controls",
      "href": "/docs/report/justice-system-and-warrant-escalation-for-rogue-intelligence#economy-and-anti-exploit-controls",
      "note": "Bounty funding and anti-collusion constraints."
    }
  ],
  "related": [
    "mandate-customer-and-jurisdiction",
    "counterintelligence-investigation",
    "operational-economy-and-resource-pressure"
  ],
  "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.evidence-based-jurisdiction-and-warrants.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 JUR-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."
    }
  ]
}