Canonical records for
intelligence mission design.

FOUND-01 Current

Operational Neutrality and Authority

Authorities define mandates, resources, constraints, and customers; the system does not assign permanent hero or villain status.

Task Plan Debrief

• MUSTEvery operation identify the sponsoring authority, customer, mandate, and jurisdiction before player acceptance.
• MUSTNo authority receive a permanent good, evil, hero, or villain flag in canonical game logic.

Open canonical record → JSON ↗

FOUND-02 Current

Mandate, Customer, and Jurisdiction

Operational authority is bounded by who requested the work, where it applies, what methods are permitted, and what review follows.

Task Plan Deliver

• MUSTTasking declare a customer, intelligence requirement, legal or organizational authority, and operating jurisdiction.
• MUSTThe mission distinguish authorized methods from prohibited or unsupported methods.

Open canonical record → JSON ↗

MISS-01 Current

Intelligence Requirement

Every mission begins with a question or decision need that collection and analysis are meant to support.

Task Plan

• MUSTState the primary intelligence requirement as a decision-oriented question.
• MUSTSeparate the requirement from assumptions, preferred explanations, and desired political outcomes.

Open canonical record → JSON ↗

MISS-02 Current

Mission Brief Contract

A mission brief is a reviewable contract connecting authority, requirement, roles, constraints, evidence thresholds, abort conditions, and extraction.

Task Plan Extract

• MUSTInclude title, authority, mandate, intelligence requirement, jurisdiction, roles, known facts, assumptions, constraints, abort condition, extraction plan, and debrief deliverable.
• MUSTDisclose whether rewards are engine-verified, authority-reviewed, or dependent on an unverified sponsor.

Open canonical record → JSON ↗

MISS-03 Current

Mission Lifecycle

Operations progress through explicit lifecycle states from tasking to debrief, with observable transitions and recoverable failure states.

Task Plan Access Collect Validate Deliver Extract Debrief

• MUSTRepresent Task, Plan, Access, Collect, Validate, Deliver, Extract, and Debrief as distinct states or reviewable milestones.
• MUSTPersist accepted brief revision, evidence state, role assignments, and consequence state across transitions.

Open canonical record → JSON ↗

MISS-04 Current

Roles and Information Asymmetry

Operative, handler, analyst, technical, liaison, and support roles receive different information and actions while contributing to one requirement.

Plan Access Collect Validate Deliver

• MUSTEach assigned role have at least one unique information source, decision, or action that materially affects the operation.
• MUSTShared mission truth remain server-authoritative even when roles receive incomplete or conflicting views.

Open canonical record → JSON ↗

MISS-05 Current

Success, Abort, Extraction, and Debrief

Operations define success beyond completion, permit professional aborts, and require extraction and debrief as first-class gameplay.

Deliver Extract Debrief

• MUSTDefine complete success, partial success, professional abort, compromised extraction, and failed debrief outcomes.
• MUSTRecord why the operation ended and which intelligence gaps remain.

Open canonical record → JSON ↗

COLL-01 Current

Collection Discipline Selection

HUMINT, SIGINT, OSINT, cyber, imagery, geospatial, and technical methods produce different evidence and exposure profiles.

Plan Access Collect

• MUSTEvery collection method declare what it can observe, what it cannot establish, and what exposure it creates.
• MUSTCollection output identify source discipline and acquisition context.

Open canonical record → JSON ↗

HUM-01 Current

Source Handling

Human sources are relationships with access, motivation, reliability, vulnerability, and independent agency.

Access Collect Validate Extract

• MUSTRepresent source access, motivation, placement, reliability history, and protection risk separately.
• MUSTStore source statements as reports with attribution and context, not as direct game truth.

Open canonical record → JSON ↗

EVID-01 Current

Observation, Report, Interpretation, and Hypothesis

The game separates what was observed, what a source reported, what an analyst inferred, and what explanation is being tested.

Collect Validate Deliver Debrief

• MUSTClassify every dossier item as observation, source report, interpretation, hypothesis, assessment, or decision.
• MUSTPreserve author, time, context, source, and revision lineage for each item.

Open canonical record → JSON ↗

EVID-02 Current

Provenance, Confidence, and Corroboration

Confidence is earned through source context, provenance, independence, consistency, and discriminating evidence.

Collect Validate Deliver Debrief

• MUSTEvery material claim carry provenance, source type, acquisition time, confidence, and reason codes.
• MUSTIndependent corroboration be required for mission-defined irreversible actions.

Open canonical record → JSON ↗

ANAL-01 Current

Competing Hypotheses and Assessment

Analysis compares multiple explanations and records what evidence would discriminate among them.

Plan Validate Deliver Debrief

• MUSTMaterial assessments identify at least one plausible alternative explanation when evidence is incomplete.
• MUSTEach hypothesis list supporting, contradicting, and non-discriminating evidence.

Open canonical record → JSON ↗

TRADE-01 Current

Cover Identity and Congruence

Cover is a persistent system of identity, access, behavior, records, competence, relationships, and exposure—not a costume slot.

Plan Access Collect Extract

• MUSTA cover define identity, occupation, purpose, access rationale, expected competence, records, relationships, and exposure indicators.
• MUSTSuspicion respond to incongruence among behavior, environment, documentation, and known history rather than a hidden alignment score.

Open canonical record → JSON ↗

TRADE-02 Guidance

Surveillance, Detection, and Counter-Surveillance

Surveillance is represented as pattern recognition, route pressure, environmental observation, and exposure management within fictional game spaces.

Plan Access Collect Extract

• MUSTKeep public documentation at fictional, abstract, game-system level and avoid practical real-world targeting instructions.
• MUSTRepresent surveillance through observable game patterns, uncertainty, and resource trade-offs.

Open canonical record → JSON ↗

TRADE-03 Current

Communications and Compartmentation

Operational information moves through role-aware channels with explicit need-to-know boundaries, delivery state, and exposure cost.

Plan Collect Deliver Extract

• MUSTOperational messages identify sender role, intended recipient, mission context, sensitivity, and delivery status.
• MUSTCompartmented information remain inaccessible to roles without a declared need-to-know path.

Open canonical record → JSON ↗

CI-01 Current

Counterintelligence Investigation

Counterintelligence identifies compromise through competing explanations, evidence provenance, access analysis, behavioral change, and controlled tests.

Task Plan Collect Validate Deliver

• MUSTSeparate access, opportunity, action, motive, and attribution as distinct investigative questions.
• MUSTCounterintelligence consequences require case evidence and reason codes rather than omniscient server accusation.

Open canonical record → JSON ↗

AI-01 Current

Synthetic Source Disclosure and Authority

Synthetic characters and generated dialogue are visibly disclosed and cannot create authoritative game facts, inventory, permissions, or settlement.

Access Collect Validate Deliver

• MUSTDisclose synthetic characters and generated responses in the interaction surface.
• MUSTKeep mission facts, inventory, access, rewards, legal status, and world state server-authoritative.

Open canonical record → JSON ↗

AI-02 Current

Mission Claim Verification

Potentially unreliable tasking is checked against records, world state, source history, logic, location, and mission economics before acceptance.

Task Plan Validate

• MUSTProvide at least one accessible method to test high-impact mission claims before commitment.
• MUSTDistinguish object, relation, event, location, authority, and reward claims in the verification model.

Open canonical record → JSON ↗

GAME-01 Current

Player Interaction and Social Stealth

Social stealth evaluates behavioral congruence, access, timing, environment, and explanation rather than invisibility or costume alone.

Access Collect Extract

• MUSTSuspicion derive from observable incongruence, restricted actions, known records, and environmental context.
• MUSTProvide nonviolent paths for access, collection, recovery, and extraction when the mission design supports them.

Open canonical record → JSON ↗

GAME-02 Current

VR and Browser Role Interdependence

Embodied VR, desktop, mobile, and browser roles coordinate through complementary information and actions.

Plan Access Collect Validate Extract

• MUSTDefine unique responsibilities for embodied and non-embodied roles within the same mission requirement.
• MUSTSynchronize authoritative mission state while allowing role-specific latency, visibility, and presentation.

Open canonical record → JSON ↗

TASK-01 Current

Verified and Unverified Tasking

Verified tasking uses engine-backed terms and settlement; unverified tasking exposes disclosed counterparty and deception risk.

Task Plan Deliver

• MUSTLabel tasking as verified, authority-reviewed, reputation-backed, or unverified before acceptance.
• MUSTVerified tasking lock reward terms and use deterministic completion or review rules.

Open canonical record → JSON ↗

LOG-01 Current

Courier and Handoff State Machine

Physical or digital operational handoffs use deterministic states, accessible destinations, tamper evidence, timeouts, and reviewable settlement.

Plan Deliver Extract

• MUSTUse Created, Accepted, In Transit, Delivered, Breached, Expired, and Canceled states with atomic settlement.
• MUSTVerify destination accessibility before posting and protect accepted couriers from later access revocation or obstruction.

Open canonical record → JSON ↗

JUR-01 Current

Evidence-Based Jurisdiction and Warrants

Severity and evidentiary certainty are separate axes; jurisdiction determines who can observe, investigate, restrict, pursue, or review.

Collect Validate Deliver Debrief

• MUSTTrack offense severity separately from evidentiary certainty.
• MUSTUse anomaly, suspect file, confirmed warrant, and active manhunt as distinguishable case states.

Open canonical record → JSON ↗

ECON-01 Guidance

Operational Economy and Resource Pressure

Currency, access, time, cover, source trust, equipment, transport, and safe locations are operational resources with explicit creation, transfer, lock, and destruction semantics.

Task Plan Deliver Extract

• MUSTClassify currency events as creation, destruction, transfer, lock, or unlock in an immutable UTC ledger.
• MUSTTreat escrow and frozen funds as temporary locks unless a separate rule destroys or forfeits value.

Open canonical record → JSON ↗

GOV-01 Current

Versioning, Change Control, and Telemetry

Public standard records are versioned, citable, machine-readable, and changed through visible release notes and test evidence.

Task Debrief

• MUSTEvery standard record publish code, version, status, canonical URL, summary, requirements, related records, and research links.
• MUSTBreaking changes increment the major version and retain the superseded public record.

Open canonical record → JSON ↗

SAFE-01 Current

Safety and Fiction Boundary

Public material stays fictional, game-system focused, and clearly separated from real-world medical, legal, investigative, or tactical authority.

Task Debrief

• MUSTLabel organizations, authorities, operations, jurisdictions, and examples as fictional where ambiguity could cause harm.
• MUSTKeep psychiatric status separate from guilt, danger, credibility, alignment, and punishment mechanics.

Open canonical record → JSON ↗