{
  "canonicalUrl": "https://xn--mwe.com/evidence/limitations/range-success-is-not-operational-readiness/",
  "claim": "A system may perform well in simulation, a cyber range, or hardware-in-the-loop testing.",
  "claimStatus": "PROJECT DOCTRINE",
  "consequence": "Demonstration evidence can be marketed as a fielded capability and distort procurement or mission decisions.",
  "correctionStatus": "CURRENT K05 RELEASE",
  "id": "LIM-K04-STRAT-021",
  "lastReviewed": "2026-08-16",
  "limitation": "Test success does not establish live deployment, sustainment, current authorization, environmental robustness, or present operation.",
  "machineRecordUrl": "https://xn--mwe.com/data/evidence/limitations/range-success-is-not-operational-readiness.json",
  "mitigation": "Use staged readiness records with exact environment, release, test coverage, defects, residual risk, deployment, uptime, and last verification.",
  "name": "Range success is not operational readiness",
  "releaseId": "K12-2026-08-16",
  "researchCutoff": "2026-08-16",
  "slug": "range-success-is-not-operational-readiness",
  "sourceIds": [
    "SRC-DODD-3000-09"
  ],
  "sourceRevalidatedAt": "2026-08-15T23:00:00Z",
  "status": "PROJECT DOCTRINE",
  "topic": "adversarial-simulation",
  "type": "EvidenceLimitation"
}