{
  "schemaVersion": 1,
  "kind": "design-review-packet",
  "bundle": "artifacts/example-settings",
  "profileSummary": {
    "available": true,
    "schemaVersion": 1,
    "platform": "ios",
    "sourceCount": 3,
    "componentCount": 2,
    "screenTypeCount": 1,
    "stateSemanticCount": 1,
    "reviewRuleCount": 2,
    "freshnessStatus": "current"
  },
  "profileStatus": "current",
  "screenshot": "artifacts/example-settings/screenshot.jpg",
  "accessibilitySummary": {
    "visibleControls": 4,
    "labels": [
      "Settings",
      "Save",
      "Cancel"
    ]
  },
  "deterministicSummary": {
    "total": 0,
    "bySeverity": {
      "P0": 0,
      "P1": 0,
      "P2": 0,
      "P3": 0
    }
  },
  "captureStatus": "complete",
  "captureStability": "stable",
  "matrixCell": null,
  "questions": [
    "Does the hierarchy match the project profile?",
    "Does any badge or status copy contradict the visible state?"
  ],
  "personas": [
    {
      "id": "first-launch",
      "name": "First-launch user",
      "lens": "Opens this screen with zero context; the next step has to be obvious without any prior knowledge.",
      "questions": [
        "With zero context, what would you tap first on this screen? If that is not the intended primary action, return a design finding."
      ]
    },
    {
      "id": "one-handed",
      "name": "One-handed phone user",
      "lens": "Holds the phone in one hand on the captured iPhone 16; primary actions must sit within comfortable thumb reach.",
      "questions": [
        "Judging from the screenshot on the captured iPhone 16, do the primary actions sit in the lower two-thirds of the screen where a thumb reaches? If not, return a design finding."
      ]
    },
    {
      "id": "voiceover-dynamic-type",
      "name": "VoiceOver + accessibility Dynamic Type user",
      "lens": "Navigates by VoiceOver and runs the largest accessibility Dynamic Type sizes; labels and layout must survive both.",
      "questions": [
        "Read the AX labels in order: does the spoken sequence tell a coherent story of the screen, or would a VoiceOver user get lost? Return incoherent ordering or vague labels as a design finding."
      ]
    },
    {
      "id": "stress-content",
      "name": "Stress-content user",
      "lens": "Brings hostile real-world data: 40-character German labels, 9999 unread, names that never fit the mock.",
      "questions": [
        "Which visible element would break first with a 40-character German label or a 9999 badge count? Return the weakest spot as a design finding."
      ]
    },
    {
      "id": "muscle-memory",
      "name": "Muscle-memory user",
      "lens": "Uses the app daily and taps from habit; primary actions must stay where the rest of the app put them.",
      "questions": [
        "Based on the profile summary and this screenshot, is the primary action where this app usually puts it? Return unexplained relocation as a design finding."
      ]
    }
  ],
  "findings": [],
  "outputSchema": {
    "findingKind": [
      "design",
      "product-logic",
      "profile-gap"
    ],
    "proofLevel": [
      "runtime-informed",
      "profile-informed",
      "agent-judgment"
    ]
  }
}
