{
  "status": "Illustrative acceptance plan, not an executable test suite or observed production result",
  "topic": "Wearable data freshness indicators",
  "date": "2026-11-04",
  "sourceArticle": "https://aptixlabs.com/insights/wearable-data-freshness-app",
  "setup": [
    "Use synthetic accounts and records",
    "Record the environment and implementation version",
    "Agree the expected product contract before testing"
  ],
  "reviewSequence": [
    "Store measurement and synchronization timestamps separately",
    "Define metric-specific freshness policies",
    "Test derived values when one input is stale"
  ],
  "cases": [
    {
      "id": "1",
      "condition": "An old sample arrives in a new sync",
      "expectedBehavior": "Its measurement age remains visible",
      "observedBehavior": null,
      "status": "not_run"
    },
    {
      "id": "2",
      "condition": "One metric is unavailable",
      "expectedBehavior": "Do not substitute a plausible zero",
      "observedBehavior": null,
      "status": "not_run"
    },
    {
      "id": "3",
      "condition": "A derived score uses stale inputs",
      "expectedBehavior": "Apply and disclose the chosen policy",
      "observedBehavior": null,
      "status": "not_run"
    }
  ],
  "tradeoff": "Too many status badges can overwhelm the interface. Surface freshness where it changes interpretation, and keep deeper provenance available on demand."
}