All chapters
9
Chapter 9

Mission Validation

LiveUpdated 2026-07-15

Reaching a target does not complete a Mission. Evidence does. mission-validation@v1.0.0.

Mission validation is the evidence-backed policy that decides whether a Mission actually completed. A single reading of the market cap is not evidence. Completion requires a full 24-hour cycle of canonical snapshots that passes every threshold defined by mission-validation@v1.0.0.

  • 01LOCKED — previous Mission not yet completed
  • 02AVAILABLE — previous Mission completed; may become current
  • 03QUALIFYING — Math Power window open
  • 04TARGET_REACHED — market cap crossed target
  • 05VALIDATING — 24-hour evidence cycle running
  • 06VALIDATED — passed every threshold
  • 07COMPLETED — persisted, irreversible
  • 08SUSPENDED · INVALIDATED — recoverable / failed branches
MISSION LIFECYCLELOCKEDAVAILABLEQUALIFYINGTARGETVALIDATINGVALIDATEDCOMPLETED24h · ≥48 snapshots · median ≥ target · ≥80% at/aboveSUSPENDED / INVALIDATED are recoverable branches
  • 0124-hour rolling validation window
  • 02At least 48 valid market-cap snapshots
  • 03Median market cap at or above target
  • 04At least 80% of valid snapshots at or above target
  • 05Snapshots must occur AFTER the cycle started
  • 06Fresh canonical evidence only — stale data suspends the cycle
VALIDATION POLICY v124hrolling window≥48valid snapshotsmedian≥ target≥80%at/above targetPROPOSED targets preview progress · never auto-complete
EVIDENCE PACK · MISSION VALIDATIONwindow24h · cycle bounds (UTC)samples≥ 48 valid snapshotsmedian≥ targetratio≥ 80% at/above targetverdictPASS · FAIL · SUSPENDEDprovenanceoracle / aggregator authority
  • 01Cycle start and end timestamps (UTC)
  • 02Number of valid snapshots collected
  • 03Median market cap over the window
  • 04Ratio of snapshots at or above target
  • 05Verdict: PASS · FAIL · SUSPENDED · CANCELLED
  • 06Data-source authority and provenance
  • 01Canonical MM72 contract on BSC (chain 56) is the token authority
  • 02Market-cap data must come from approved oracles/aggregators
  • 03The Mission Engine — not the UI — decides validation
  • 04The frontend never locally decides Mission completion
  • 05Founder approval may be required for PROPOSED targets

Target: $72,000 market cap. When observed market cap first crosses $72K, Mission 1 enters TARGET_REACHED and a 24-hour cycle begins. Over that cycle the Engine collects ≥48 valid snapshots, computes the median, and counts how many snapshots stayed at or above target. Only if median ≥ target AND ≥80% at/above does Mission 1 move to VALIDATED → COMPLETED. Its Reward Unlock then enters READY_NOT_ACTIVE. No tokens move until the Pool contract is deployed, funded, and Founder-approved to ACTIVE.

A cycle collects 48 valid snapshots. Median is above target, but only 71% of snapshots stayed at/above. The verdict is FAIL. Mission status becomes INVALIDATED. Nothing is rewritten; a new cycle may start when the target is crossed again.

  • · Track the current Mission from the Mission Map
  • · Build Math Power while the current Mission is QUALIFYING
  • · Never treat a temporary spike as a completed Mission