Build the mission from
declared operating truth.

{
  "mission_id": "IARPG-HS-001",
  "title": "Operation Hollow Signal",
  "authority": "Civic Directorate / Route Integrity Office",
  "customer": "Port Meridian Continuity Board",
  "mandate": "Determine the cause of a compromised route packet without forcing attribution before corroboration. Preserve source safety and route continuity while the case remains unresolved.",
  "intelligence_requirement": "Did the compromise result from human disclosure, automation failure, or a fabricated intercept intended to trigger a purge?",
  "jurisdiction": "Port Meridian civic facilities, contracted transit systems, and evidence obtained under the Route Integrity Office inspection mandate.",
  "known_facts": [
    "A privileged export path existed.",
    "Revision lineage conflicts with the official automation report.",
    "The packet copy lacks complete custody metadata."
  ],
  "assumptions": [
    "The apparent target may not be the intended beneficiary of the compromise.",
    "At least one source may be repeating an interpretation as a fact."
  ],
  "roles": [
    "VR Operative — conduct embodied interviews, inspect the facility, and preserve observations.",
    "Desktop Handler — maintain the caseboard, compare hypotheses, and monitor abort conditions.",
    "Field Support Analyst — verify logs, routes, timing, and evidence provenance."
  ],
  "collection_plan": [
    "HUMINT: interview route personnel without disclosing the preferred hypothesis.",
    "TECHINT: compare revision history, access logs, and packet metadata.",
    "OSINT: verify public route changes and maintenance notices.",
    "Counterintelligence: test whether the intercept was designed to provoke an internal purge."
  ],
  "evidence_threshold": "Independent corroboration from two different collection paths is required before naming an actor, removing access, or triggering public attribution.",
  "cover_plan": "The Operative enters as a facilities contractor with a limited maintenance-inspection mandate, expected technical competence, a documented service route, and explicit exposure indicators.",
  "interaction_model": "Players interview sources, inspect physical objects, compare logs, mark contradictions, request corroboration, manage a shared caseboard, protect the cover identity, choose whether to convert the task into reconnaissance, and hand custody to the Handler during extraction.",
  "abort_condition": "Abort direct collection when a source enters confirmed danger, the cover identity is materially exposed, evidence custody cannot be preserved, or continued access would force an irreversible action below the evidence threshold.",
  "extraction_plan": "Exit through the contracted service route, move source contact details into a protected compartment, transfer evidence custody to the Handler, and preserve a secondary route if the primary corridor closes.",
  "debrief_deliverable": "Deliver an assessment of all three hypotheses with confidence, supporting observations, contradictions, custody history, source-protection status, operational consequences, unresolved gaps, and recommended next collection.",
  "synthetic_source_policy": "disclosed-and-claim-only",
  "reward_posture": "verified",
  "reason_codes": true,
  "fiction_boundary": true,
  "standard_version": "IARPG-OPS-1"
}