Who needs the intelligence?
Identify the fictional institution, its mandate, its customer, and the jurisdiction in which it can act.
Intelligence Agent Role Playing Game
Intelligence is work.
Not an alignment.
Every operation begins with an authority, a requirement, a customer decision, and constraints. The player’s job is to gain access, collect responsibly inside the fictional system, validate what was found, and deliver intelligence that can survive scrutiny.
The professional premise
The same event creates
different legitimate tasking.
A defense command may need warning. A commercial office may need continuity. A liaison secretariat may need releasable corroboration. An independent network may need source protection. The event does not arrive pre-labeled as good or evil; the authority defines the requirement and the player manages the consequences.
What decision must be supported?
Define the question, desired effect, deadline, confidence threshold, and information gaps before collection begins.
What makes collection possible?
Use cover, relationships, liaison, credentials, technical position, timing, or environmental access as game systems.
What must be delivered?
Produce reporting, warning, assessment, verification, denial, source protection, or another task-specific operational result.
The operation cycle
Task. Plan. Access. Collect.
Validate. Deliver. Debrief.
Each stage can create new requirements, expose a compromised assumption, or force a controlled withdrawal. The cycle is iterative rather than a straight line to combat.
01 / 07
Task
Receive the authority, intelligence requirement, desired effect, mandate, constraints, and reporting deadline.
02 / 07
Plan
Select collection disciplines, covers, routes, sources, cut-outs, communications, contingencies, and abort conditions.
03 / 07
Access
Establish a legitimate reason to be present and create the relationships, credentials, or technical position required to collect.
04 / 07
Collect
Acquire observations, documents, signals, imagery, testimony, network evidence, or physical material without collapsing the operation.
05 / 07
Validate
Check provenance, source reliability, contradictions, alternate explanations, and whether the apparent answer was planted.
06 / 07
Deliver
Move intelligence through the required channel, classification boundary, handler, liaison, or customer without losing context.
07 / 07
Debrief
Record what happened, what remains uncertain, what access survived, what was burned, and what the next operation must know.
Operational outcomes
Success is more than
taking an object.
An operation can achieve its requirement without a firefight and can fail intelligently without becoming meaningless. What matters is the customer’s decision, the surviving access, the protected source, and the accuracy of the brief.
Strategic or tactical warning
Deliver enough lead time and confidence for an authority to change posture.
Confirm or reject a claim
Separate planted narratives, reporting error, source bias, and observable fact.
Preserve source and access
Withdraw before a short-term gain destroys a valuable relationship or future position.
Prevent an intelligence advantage
Secure material, close an exposure, alter access, or neutralize a compromised channel inside the game.
Restore capability or continuity
Recover a person, record, route, credential, communications link, or trusted process.
Explain motive and implication
Tell the customer what the evidence means, what remains uncertain, and what should be collected next.
Reference operation
Hollow
Signal
A compromised route packet supports three plausible explanations.
The cell must determine whether the anomaly represents an insider disclosure, an automation failure, or a fabricated intercept intended to force an internal purge. The first coherent story is not automatically the correct one.
CASEBOARD / MULTI-SOURCE REVIEWFICTIONAL OPERATION
Privileged export detected
A valid path existed. Opportunity is established; actor and intent are not.
CONFIDENCE 0.82Insider disclosure
Possible. Motive and action remain uncorroborated.
Automation failure
Revision lineage and control behavior require comparison.
Fabricated intercept
A forced purge may benefit a concealed third authority.
Deep research links
Read the doctrine sources.
The live page keeps the operating model concise. The full reports preserve the broader reasoning, alternate designs, and source context.
FULL REPORT
Systemic Subterfuge: A Geopolitically Neutral Espionage MMO
Multipolar authority design without permanent hero or enemy factions.
→
FULL REPORT
VR-First Post-National Espionage MMO
World architecture, role structure, and persistent operational systems.
→
FULL REPORT
Counterintelligence Directive: Leak Investigation
A source-linked model for anomaly, evidence, competing hypotheses, and review.
→
Next briefing
Choose the work.
Then choose the authority.
Study the role matrix, understand the tasking, and enter the reference operation with a reason for every decision.
