{
  "request": {
    "campaign": "SYNTHETIC",
    "suite": "IMPLEMENTATION-PROXIMITY",
    "cases": [
      {
        "alias": "CASE-0001",
        "description": "Check synthetic beacon mode behavior against the same generalized subsystem requirement. This broad title does not specify the required testing mechanism.",
        "preconditions": "Synthetic beacon is controlled only through the existing command/readback JSON client and reset-state fixture.",
        "success_criteria": "Issue the requested mode through the command client, collect the returned JSON snapshot, and assert acceptance status and reported state using the same response fields. Variant 1: preserve the stated lower-than or equal-to relationship to [value]; do not reconstruct the omitted value. Nominal input must have a true acceptance flag.",
        "case_type": "nominal",
        "verifies": "[reference]"
      },
      {
        "alias": "CASE-0002",
        "description": "Check synthetic beacon mode behavior against the same generalized subsystem requirement. This broad title does not specify the required testing mechanism.",
        "preconditions": "Synthetic bench controller and oscilloscope adapter are already available; every variant uses the same output probe and waveform capture.",
        "success_criteria": "Apply the mode transition through the bench controller, capture the physical output waveform, and assert amplitude and transition ordering using the captured samples. Variant 1: preserve the stated lower-than or equal-to relationship to [value]; do not reconstruct the omitted value.",
        "case_type": "nominal",
        "verifies": "[reference]"
      },
      {
        "alias": "CASE-0003",
        "description": "Check synthetic beacon mode behavior against the same generalized subsystem requirement. This broad title does not specify the required testing mechanism.",
        "preconditions": "Read an offline synthetic static-analysis report with the same report parser and rule-policy fixture; do not execute the target.",
        "success_criteria": "Parse the report, count findings for the selected rule and severity, and compare the count with its stated qualitative acceptance bound. Variant 1: preserve the stated lower-than or equal-to relationship to [value]; do not reconstruct the omitted value.",
        "case_type": "nominal",
        "verifies": "[reference]"
      },
      {
        "alias": "CASE-0004",
        "description": "Check synthetic beacon mode behavior against the same generalized subsystem requirement. This broad title does not specify the required testing mechanism.",
        "preconditions": "Use a thermal chamber and calibrated enclosure dimensional gauge; the temperature cycle controller is independent of the waveform bench.",
        "success_criteria": "Cycle chamber temperature and measure enclosure expansion with the gauge; assert expansion is below the generalized bound.",
        "case_type": "fault injection",
        "verifies": "[reference]"
      },
      {
        "alias": "CASE-0005",
        "description": "Check synthetic beacon mode behavior against the same generalized subsystem requirement. This broad title does not specify the required testing mechanism.",
        "preconditions": "Synthetic beacon is controlled only through the existing command/readback JSON client and reset-state fixture.",
        "success_criteria": "Issue the requested mode through the command client, collect the returned JSON snapshot, and assert acceptance status and reported state using the same response fields. Variant 2: preserve the stated lower-than or equal-to relationship to [value]; do not reconstruct the omitted value. Invalid input must have a false acceptance flag in the same response structure.",
        "case_type": "fault injection",
        "verifies": "[reference]"
      },
      {
        "alias": "CASE-0006",
        "description": "Check synthetic beacon mode behavior against the same generalized subsystem requirement. This broad title does not specify the required testing mechanism.",
        "preconditions": "Synthetic bench controller and oscilloscope adapter are already available; every variant uses the same output probe and waveform capture.",
        "success_criteria": "Apply the mode transition through the bench controller, capture the physical output waveform, and assert amplitude and transition ordering using the captured samples. Variant 2: preserve the stated lower-than or equal-to relationship to [value]; do not reconstruct the omitted value. Also derive transition duration from the already captured samples and compare it with the stated lower bound.",
        "case_type": "fault injection",
        "verifies": "[reference]"
      },
      {
        "alias": "CASE-0007",
        "description": "Check synthetic beacon mode behavior against the same generalized subsystem requirement. This broad title does not specify the required testing mechanism.",
        "preconditions": "Read an offline synthetic static-analysis report with the same report parser and rule-policy fixture; do not execute the target.",
        "success_criteria": "Parse the report, count findings for the selected rule and severity, and compare the count with its stated qualitative acceptance bound. Variant 2: preserve the stated lower-than or equal-to relationship to [value]; do not reconstruct the omitted value.",
        "case_type": "fault injection",
        "verifies": "[reference]"
      },
      {
        "alias": "CASE-0008",
        "description": "Check synthetic beacon mode behavior against the same generalized subsystem requirement. This broad title does not specify the required testing mechanism.",
        "preconditions": "Use an anechoic enclosure, microphone capture adapter, and spectral-analysis fixture; no oscilloscope or chamber controller is shared.",
        "success_criteria": "Record acoustic output and assert each spectral peak is below its frequency-dependent generalized bound.",
        "case_type": "boundary",
        "verifies": "[reference]"
      },
      {
        "alias": "CASE-0009",
        "description": "Check synthetic beacon mode behavior against the same generalized subsystem requirement. This broad title does not specify the required testing mechanism.",
        "preconditions": "Synthetic beacon is controlled only through the existing command/readback JSON client and reset-state fixture.",
        "success_criteria": "Issue the requested mode through the command client, collect the returned JSON snapshot, and assert acceptance status and reported state using the same response fields. Variant 3: preserve the stated lower-than or equal-to relationship to [value]; do not reconstruct the omitted value. Also assert error_code from the same returned JSON; no new observation mechanism is needed.",
        "case_type": "boundary",
        "verifies": "[reference]"
      },
      {
        "alias": "CASE-0010",
        "description": "Check synthetic beacon mode behavior against the same generalized subsystem requirement. This broad title does not specify the required testing mechanism.",
        "preconditions": "Synthetic bench controller and oscilloscope adapter are already available; every variant uses the same output probe and waveform capture.",
        "success_criteria": "Apply the mode transition through the bench controller, capture the physical output waveform, and assert amplitude and transition ordering using the captured samples. Variant 3: preserve the stated lower-than or equal-to relationship to [value]; do not reconstruct the omitted value.",
        "case_type": "boundary",
        "verifies": "[reference]"
      },
      {
        "alias": "CASE-0011",
        "description": "Check synthetic beacon mode behavior against the same generalized subsystem requirement. This broad title does not specify the required testing mechanism.",
        "preconditions": "Read an offline synthetic static-analysis report with the same report parser and rule-policy fixture; do not execute the target.",
        "success_criteria": "Parse the report, count findings for the selected rule and severity, and compare the count with its stated qualitative acceptance bound. Variant 3: preserve the stated lower-than or equal-to relationship to [value]; do not reconstruct the omitted value.",
        "case_type": "boundary",
        "verifies": "[reference]"
      },
      {
        "alias": "CASE-0012",
        "description": "Check synthetic beacon mode behavior against the same generalized subsystem requirement. This broad title does not specify the required testing mechanism.",
        "preconditions": "Required interface, observation mechanism, and fixture are omitted from [reference].",
        "success_criteria": "Verify the latent-state relationship in [reference]; how to stimulate or observe that state is unspecified.",
        "case_type": "nominal",
        "verifies": "[reference]"
      },
      {
        "alias": "CASE-0013",
        "description": "Check synthetic beacon mode behavior against the same generalized subsystem requirement. This broad title does not specify the required testing mechanism.",
        "preconditions": "Synthetic beacon is controlled only through the existing command/readback JSON client and reset-state fixture.",
        "success_criteria": "Issue the requested mode through the command client, collect the returned JSON snapshot, and assert acceptance status and reported state using the same response fields. Variant 4: preserve the stated lower-than or equal-to relationship to [value]; do not reconstruct the omitted value.",
        "case_type": "nominal",
        "verifies": "[reference]"
      },
      {
        "alias": "CASE-0014",
        "description": "Check synthetic beacon mode behavior against the same generalized subsystem requirement. This broad title does not specify the required testing mechanism.",
        "preconditions": "Synthetic bench controller and oscilloscope adapter are already available; every variant uses the same output probe and waveform capture.",
        "success_criteria": "Apply the mode transition through the bench controller, capture the physical output waveform, and assert amplitude and transition ordering using the captured samples. Variant 1: preserve the stated lower-than or equal-to relationship to [value]; do not reconstruct the omitted value.",
        "case_type": "nominal",
        "verifies": "[reference]"
      }
    ],
    "routing": {
      "allow_external": true,
      "allowed_external_providers": [
        "claude"
      ]
    },
    "execution": {
      "strategy": "whole_suite",
      "max_seconds": 900,
      "max_cost_usd": 5
    }
  },
  "expected_implementation_family": {
    "CASE-0001": "api",
    "CASE-0002": "waveform",
    "CASE-0003": "report",
    "CASE-0004": "thermal",
    "CASE-0005": "api",
    "CASE-0006": "waveform",
    "CASE-0007": "report",
    "CASE-0008": "acoustic",
    "CASE-0009": "api",
    "CASE-0010": "waveform",
    "CASE-0011": "report",
    "CASE-0012": "unknown",
    "CASE-0013": "api",
    "CASE-0014": "waveform"
  }
}