Normative requirements
What conforming mission design must express.
Classify currency events as creation, destruction, transfer, lock, or unlock in an immutable UTC ledger.
Treat escrow and frozen funds as temporary locks unless a separate rule destroys or forfeits value.
Compose mission rewards from currency, access, intelligence, reputation, supplies, and persistent opportunities rather than raw cash alone.
Measure newcomer and operational affordability before changing sinks or payouts.
Use property, communications, transport, cover maintenance, and logistics as mission-relevant sinks.
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.
