Normative requirements
What conforming mission design must express.
Keep public documentation at fictional, abstract, game-system level and avoid practical real-world targeting instructions.
Represent surveillance through observable game patterns, uncertainty, and resource trade-offs.
Provide more than one response to suspected surveillance, including delay, route change, abort, decoy, or controlled exposure.
Use accessibility settings to surface patterns through visual, audio, or interface cues.
Mission lifecycle fit
Where this record applies.
This list identifies the mission stages where the record is most likely to be implemented or reviewed. It does not prevent the requirement from influencing adjacent phases.
Search and implementation terms
Vocabulary carried by this record.
Supporting research
Deep links into the complete report archive.
The canonical record stays concise. These links preserve the longer argument, design context, limitations, and source lineage in the `/docs/` archive.
