Briefable
Mission identity, title, sponsoring authority, mandate, intelligence requirement, and jurisdiction.
Local conformance workbench / IARPG-OPS-2
Validate the mission contract.
Keep the work reviewable.
Paste or edit a fictional intelligence mission brief. The validator checks the current structural contract entirely in your browser and explains what is missing before the mission is treated as briefable, playable, auditable, or simulatable.
Mission brief input
One JSON brief.
Four review levels.
Structural conformance is not a truth or quality guarantee. It confirms that the mission exposes the minimum operating contract needed for players, reviewers, and machine tools to inspect the design.
MISSION BRIEF JSON
0 bytes
Local-only: this page does not send the mission content to iarpg.com or any third party.
{ "standard_version": "IARPG-OPS-2", "profile_version": "2.0.4-wip", "mission_id": "IARPG-MSN-001", "slug": "port-access-anomaly-investigation", "title": "Port Access Anomaly Investigation", "authority": "Port Meridian Civic Continuity Office", "authority_code": "CIV-01", "customer": "Metropolitan continuity council", "mandate": "Collect and assess information within the declared fictional jurisdiction and report uncertainty without forcing a preferred conclusion.", "jurisdiction": "Port Meridian civil port systems", "intelligence_requirement": "Determine whether repeated privileged export events reflect insider disclosure, automation failure, or fabricated traffic intended to trigger a purge.", "known_facts": [ "A triggering anomaly or request has been logged.", "The authority has access to some but not all relevant records.", "At least two explanations remain plausible." ], "assumptions": [ "Current system clocks are synchronized within the published tolerance.", "Declared access records have not yet been proven complete." ], "competing_hypotheses": [ "Administrative or technical failure", "Authorized but poorly documented activity", "Deliberate disclosure or manipulation", "Fabricated evidence intended to redirect attention" ], "roles": [ "Operative", "Handler", "Intelligence Analyst", "Technical Operator" ], "information_asymmetry": { "Operative": [ "Role-specific tasking", "Authorized evidence subset" ], "Handler": [ "Role-specific tasking", "Authorized evidence subset" ], "Intelligence Analyst": [ "Role-specific tasking", "Authorized evidence subset" ], "Technical Operator": [ "Role-specific tasking", "Authorized evidence subset" ] }, "collection_plan": [ "Access-control review", "Witness interview", "Technical log collection", "Open-source schedule comparison" ], "sources": [ { "source_id": "SRC-01", "class": "human-or-record", "reliability": "unknown-at-tasking", "access": "limited", "handling": "compartmented" } ], "player_interactions": [ "Review tasking", "Establish access", "Collect evidence", "Mark contradiction", "Request corroboration", "Choose continue, convert, or abort", "Complete extraction and debrief" ], "cover_and_access": "Use a mission-appropriate fictional professional cover or declared inspection authority; access must be plausible and documented.", "evidence_threshold": "Deliver an assessment only after two independent evidence classes corroborate the leading explanation.", "synthetic_source_policy": "disclosed-and-claim-only", "compromise_indicators": [ "Unexpected access challenge", "Unexplained route change", "Source behavior inconsistent with prior handling", "Evidence item lacking provenance", "Role handoff not acknowledged" ], "abort_conditions": [ "Cover integrity below 35", "Source safety cannot be maintained", "Jurisdiction is exceeded", "Required evidence custody cannot be preserved" ], "extraction_plan": "Extract through the public maintenance corridor or abort to remote debrief if cover integrity falls below 35.", "debrief_deliverable": "An assessment that separates observation, source report, interpretation, hypothesis, confidence, dissent, source impact, cover impact, and follow-on requirements.", "reward_posture": "authority-reviewed", "reason_codes": true, "fiction_boundary": true, "states": [ "Task", "Plan", "Access", "Collect", "Validate", "Deliver", "Extract", "Debrief" ], "transitions": [ { "from": "Task", "action": "accept tasking", "to": "Plan" }, { "from": "Plan", "action": "approve plan", "to": "Access" }, { "from": "Access", "action": "establish access", "to": "Collect" }, { "from": "Collect", "action": "submit evidence packet", "to": "Validate" }, { "from": "Validate", "action": "meet threshold", "to": "Deliver" }, { "from": "Deliver", "action": "complete handoff", "to": "Extract" }, { "from": "Extract", "action": "reach extraction or remote debrief", "to": "Debrief" } ], "failure_paths": [ "Abort", "Compromise", "Partial success", "Converted objective" ], "seed": "hollow-signal", "supporting_standards": [ "mission-brief-contract", "mission-lifecycle", "roles-and-information-asymmetry", "provenance-confidence-and-corroboration", "compromise-abort-handling", "mission-event-logging", "deterministic-mission-state-machines", "debrief-product-contract" ], "supporting_reports": [ "/docs/report/intelligence-operative-archetypes-and-tradecraft", "/docs/report/justice-system-and-warrant-escalation-for-rogue-intelligence", "/docs/report/hallucinated-ai-quest-design-in-vr-mmorpgs" ], "evidence_events": [ "Observation or source report recorded with origin and UTC event time", "Provenance and chain of custody reviewed", "Corroboration or contradiction relationship recorded", "Assessment and reason code published" ], "extraction_states": [ "Primary extraction", "Alternate extraction", "Emergency extraction", "Remote debrief" ], "debrief_outputs": [ "Objective status", "Evidence acquired", "Unresolved uncertainty", "Source impact", "Cover impact", "Access status", "Follow-on requirements" ] }What the validator checks
A structural contract,
not a certification claim.
The workbench is intentionally narrow. It checks whether the mission is reviewable. It cannot determine whether the underlying story is true, fair, balanced, legal, accessible, secure, or fun.
Playable
Known facts, roles, collection plan, interaction model, evidence threshold, abort condition, extraction, and debrief.
Auditable
Current release identifier, reward posture, synthetic-source policy, reason codes, explicit fiction boundary, and complete field coverage.
Simulatable
Explicit states, guarded transitions, interactions, evidence events, failure paths, extraction states, debrief outputs, and reproducible seed.
Not certified
No claim is made about factual accuracy, legal compliance, real-world intelligence practice, player safety, implementation quality, or production readiness.
