{
  "case_id": "gear_sonic/end_to_end_cli_loop",
  "command_fixture": {
    "data": [
      0.3,
      0.0,
      0.0
    ],
    "kind": "velocity"
  },
  "description": "RoboWBC CLI loop running configs/sonic_g1.toml through the synthetic transport with a JSON report, after rewriting all three GEAR-Sonic provider blocks to the requested provider.",
  "host_fingerprint": "runnervmeorf1 | Linux 6.17.0-1010-azure | x86_64 | AMD EPYC 7763 64-Core Processor",
  "hz": 44.454154,
  "implementation": "ort-rs",
  "implementation_label": "ORT-rs",
  "interpretation": "This is the full deployment-loop question: can the live velocity path hold frequency end to end on the requested provider, not just in one isolated inference call?",
  "notes": "Normalized from the ORT-rs robowbc-cli JSON run report.",
  "p50_ns": 3662278,
  "p95_ns": 4224186,
  "p99_ns": 4478805,
  "provider": "cpu",
  "provider_family": "cpu-baseline",
  "raw_source": "/tmp/tmp09mhxye8/report.json",
  "robowbc_commit": "53994db55a58041ebb4e63f3e0e0a1b424ba0cf6",
  "samples": 200,
  "schema_version": 1,
  "source_command": "python3 scripts/benchmarks/bench_robowbc_compare.py --case gear_sonic/end_to_end_cli_loop --provider cpu",
  "stack": "robowbc",
  "status": "ok",
  "upstream_commit": "cc80d505b7e055fd6ae26426ae8bfa0a74c26011",
  "variant_label": "cpu-baseline",
  "variant_slug": "cpu-baseline",
  "warmup_policy": "default_cli_loop_200_ticks"
}