[
  {
    "legacy_id": "RUN-01",
    "slug": "three-agent-compaction-chain-at-a-100k-target",
    "title": "Three-agent compaction chain at a 100k target",
    "interpretation": "Measure context growth, prefix reuse, latency and stall behaviour under repeated compaction. The prompt-compute counter peaks near 65k tokens/s because it credits work in bursts at request completion; that is not true PP. Read this as a compaction workload, not a clean throughput baseline.",
    "version": "rocm-7.14",
    "provenance": "ROCm 7.14 by recorded active profile and 6\u20138 October collection date; no immutable image ID captured per trace.",
    "included": false,
    "selection_reason": "A 100k three-agent compaction-chain sweep; it investigates compaction rather than the selected 131k concurrency/runtime comparison",
    "source_name_sha256": "d226a0546f32cc0b06731c74c8ccaee40e5be4580718370ce5ea04665dc8ad4e"
  },
  {
    "legacy_id": "RUN-02",
    "slug": "three-agent-compaction-chain-extended-to-110k",
    "title": "Three-agent compaction chain extended to 110k",
    "interpretation": "Probe the usable depth frontier for three concurrent agents. Compare latency and stall growth with the neighboring 90k and 100k cases.",
    "version": "rocm-7.14",
    "provenance": "ROCm 7.14 by recorded active profile and 6\u20138 October collection date; no immutable image ID captured per trace.",
    "included": false,
    "selection_reason": "A 110k extension of the compaction sweep; different depth and history prevent a matched runtime comparison",
    "source_name_sha256": "77621ae6028b7834bb3bed9adb90eb36fa1ec55be1941e8b8e4fde3661d74717"
  },
  {
    "legacy_id": "RUN-03",
    "slug": "three-agent-compaction-chain-at-90k",
    "title": "Three-agent compaction chain at 90k",
    "interpretation": "Lower-depth reference for the three-agent chain. Use as a context for deeper compaction cases, not as an isolated hardware comparison.",
    "version": "rocm-7.14",
    "provenance": "ROCm 7.14 by recorded active profile and 6\u20138 October collection date; no immutable image ID captured per trace.",
    "included": false,
    "selection_reason": "A 90k compaction reference; useful tuning context but redundant in the focused comparison",
    "source_name_sha256": "e60d91a53d93397f2685ffbe85098d186e518cf29154433024c3d85b95971c73"
  },
  {
    "legacy_id": "RUN-04",
    "slug": "four-agent-compaction-at-64k",
    "title": "Four-agent compaction at 64k",
    "interpretation": "Shallow four-agent point used to see how compaction begins under concurrency. Compare the event/stall profile with deeper four-agent points.",
    "version": "rocm-7.14",
    "provenance": "ROCm 7.14 by recorded active profile and 6\u20138 October collection date; no immutable image ID captured per trace.",
    "included": false,
    "selection_reason": "A shallow 64k four-agent compaction case; outside the long-context target",
    "source_name_sha256": "be33b88bd225f4684c16aac3593b4162371dbb73f5dfc9e310de978905a3a862"
  },
  {
    "legacy_id": "RUN-05",
    "slug": "four-agent-compaction-at-80k",
    "title": "Four-agent compaction at 80k",
    "interpretation": "Intermediate-depth four-agent workload. Look for the onset of queue and compaction stalls as context grows.",
    "version": "rocm-7.14",
    "provenance": "ROCm 7.14 by recorded active profile and 6\u20138 October collection date; no immutable image ID captured per trace.",
    "included": false,
    "selection_reason": "An 80k compaction-depth step; part of an exploratory sweep rather than a selected operating point",
    "source_name_sha256": "73e3e573e8ad7c14799c00567197488c44a7baaba664f44db1e557356998ad9b"
  },
  {
    "legacy_id": "RUN-06",
    "slug": "four-agent-compaction-at-86k",
    "title": "Four-agent compaction at 86k",
    "interpretation": "Narrow depth step within the compaction region. Treat small differences cautiously because workload history and cache state affect the storm profile.",
    "version": "rocm-7.14",
    "provenance": "ROCm 7.14 by recorded active profile and 6\u20138 October collection date; no immutable image ID captured per trace.",
    "included": false,
    "selection_reason": "An 86k compaction-depth step near a workload cliff; not a matched ROCm comparison",
    "source_name_sha256": "14278a2705fd6db92be6f4a07f059c00f307669d6779978b496d10ab147c5732"
  },
  {
    "legacy_id": "RUN-07",
    "slug": "four-agent-compaction-at-90k",
    "title": "Four-agent compaction at 90k",
    "interpretation": "Reference four-agent storm workload used repeatedly for later storage and link comparisons. This is deliberately sustained stress, not a short latency smoke test.",
    "version": "rocm-7.14",
    "provenance": "ROCm 7.14 by recorded active profile and 6\u20138 October collection date; no immutable image ID captured per trace.",
    "included": false,
    "selection_reason": "A 90k four-agent compaction-storm reference; intentionally stresses prefix loss rather than the selected context-growth workload",
    "source_name_sha256": "85160b1a4c8a736874d7790f37cd7c5df297acb9c4fdd6929cfa811baac965f5"
  },
  {
    "legacy_id": "RUN-08",
    "slug": "clean-rerun-after-a-prefill-threshold-change",
    "title": "Clean rerun after a prefill-threshold change",
    "interpretation": "Checks whether smaller prefill scheduling steps reduce long stalls. Interpret TTFT, prefill throughput and long-stall counts together; the change reduced some micro-stalls but did not eliminate total stall time.",
    "version": "rocm-7.14",
    "provenance": "ROCm 7.14 by recorded active profile and 6\u20138 October collection date; no immutable image ID captured per trace.",
    "included": false,
    "selection_reason": "A prefill-threshold tuning rerun; changes scheduler configuration and is not a runtime-only comparison",
    "source_name_sha256": "70654e812627cacac5e69f5a6b067ce9a608941998a265d74c4e950b83eefdf3"
  },
  {
    "legacy_id": "RUN-09",
    "slug": "foreign-traffic-contaminated-threshold-trial",
    "title": "Foreign-traffic-contaminated threshold trial",
    "interpretation": "Tainted comparison: unrelated traffic shared the service during collection. Keep it for provenance only; do not use its metrics to claim a treatment effect.",
    "version": "rocm-7.14",
    "provenance": "ROCm 7.14 by recorded active profile and 6\u20138 October collection date; no immutable image ID captured per trace.",
    "included": false,
    "selection_reason": "Unrelated traffic contaminated the measurement; its metrics cannot establish a treatment effect",
    "source_name_sha256": "1e3025a5f399acb83500bbd9f2d2e4cd17f6bf82d57f9717d45b1693bbdf8074"
  },
  {
    "legacy_id": "RUN-10",
    "slug": "gpu-link-upgrade-comparison-at-the-four-agent-storm-point",
    "title": "GPU-link upgrade comparison at the four-agent storm point",
    "interpretation": "Replays the reference workload after a link change. It improves average transfer/reload behaviour but does not resolve the long-tail stall mechanism.",
    "version": "rocm-7.14",
    "provenance": "ROCm 7.14 by recorded active profile and 6\u20138 October collection date; no immutable image ID captured per trace.",
    "included": false,
    "selection_reason": "The GPU-link path changed; link bandwidth and runtime effects cannot be isolated",
    "source_name_sha256": "ce92d8cd68aaa2256a93e40ad59bd1572aeff5ec65d37ce48916a9faf6664434"
  },
  {
    "legacy_id": "RUN-11",
    "slug": "clean-storage-four-agent-storm-trial",
    "title": "Clean-storage four-agent storm trial",
    "interpretation": "Tests whether a clean backing tier changes stalls. Compare storage traffic and stall timing; this precedes the loop-backed tier test.",
    "version": "rocm-7.14",
    "provenance": "ROCm 7.14 by recorded active profile and 6\u20138 October collection date; no immutable image ID captured per trace.",
    "included": false,
    "selection_reason": "A backing-storage experiment; storage-path effects are outside the selected runtime comparison",
    "source_name_sha256": "ebfd025885edba7b5eb69fe5a9fcdea58a0aacbf944451a01d141a64a8d3b308"
  },
  {
    "legacy_id": "RUN-12",
    "slug": "loop-backed-fast-storage-trial",
    "title": "Loop-backed fast-storage trial",
    "interpretation": "Tests the backing-store path with a capped loop device. Use memory telemetry alongside engine metrics to distinguish real tier use from idle capacity.",
    "version": "rocm-7.14",
    "provenance": "ROCm 7.14 by recorded active profile and 6\u20138 October collection date; no immutable image ID captured per trace.",
    "included": false,
    "selection_reason": "A loop-backed storage experiment; it tests a tier implementation rather than the retained deployment profiles",
    "source_name_sha256": "716c3731b2c8ced98599cb4d565992a337d3dd7f131cf791953543e5cc83b445"
  },
  {
    "legacy_id": "RUN-13",
    "slug": "eight-agent-overflow-ram-tier-boundary",
    "title": "Eight-agent overflow / RAM-tier boundary",
    "interpretation": "Intentionally exceeds the GPU plus host-memory working set so the backing tier must receive spill traffic. This is a capacity and survival stress test, not a normal operating point.",
    "version": "rocm-7.14",
    "provenance": "ROCm 7.14 by recorded active profile and 6\u20138 October collection date; no immutable image ID captured per trace.",
    "included": false,
    "selection_reason": "An intentional eight-agent overflow boundary test; it exceeds the intended operating point",
    "source_name_sha256": "337bd6a933c172a45840ab390b0fb8259090d36dcf01db9472c524318d991c0b"
  },
  {
    "legacy_id": "RUN-14",
    "slug": "reduced-host-tier-capacity-at-four-agent-load",
    "title": "Reduced host-tier capacity at four-agent load",
    "interpretation": "Compares a smaller RAM tier with the previously tested larger tier. Watch swap, reload rates, memory headroom and deep-context latency.",
    "version": "rocm-7.14",
    "provenance": "ROCm 7.14 by recorded active profile and 6\u20138 October collection date; no immutable image ID captured per trace.",
    "included": false,
    "selection_reason": "A smaller host-tier experiment; its memory budget differs from the retained profiles",
    "source_name_sha256": "2de4218d34e32a493aad1aa600e0edd3c34d5333f199a9a40502068572091752"
  },
  {
    "legacy_id": "RUN-15",
    "slug": "single-card-ram16-tier-four-agents-at-131k-target",
    "title": "Single-card RAM16 tier, four agents at 131k target",
    "interpretation": "Qualification run for the 16 GiB shared-memory tier with four agents on one card. It is the key smooth-operation milestone; read error count, turn completion, TTFT by depth and memory pressure together.",
    "version": "rocm-7.14",
    "provenance": "ROCm 7.14 by recorded active profile and 6\u20138 October collection date; no immutable image ID captured per trace.",
    "included": true,
    "selection_reason": "Core single-card RAM16 capacity milestone or its resource trace",
    "source_name_sha256": "313349945c6439dff79905b41690bdf167745561628cce3a230bce29da60a94c"
  },
  {
    "legacy_id": "RUN-16",
    "slug": "single-card-ram16-tier-three-agents-at-150k-target",
    "title": "Single-card RAM16 tier, three agents at 150k target",
    "interpretation": "Follow-up capacity point with fewer agents and deeper context. Compare sustained completion and tail behaviour with the four-agent milestone.",
    "version": "rocm-7.14",
    "provenance": "ROCm 7.14 by recorded active profile and 6\u20138 October collection date; no immutable image ID captured per trace.",
    "included": true,
    "selection_reason": "Core single-card RAM16 capacity milestone or its resource trace",
    "source_name_sha256": "993496e46807a2b2d651ea8e6b8fc872c13bc9294fda8618ee718cfd7e0046c6"
  },
  {
    "legacy_id": "RUN-17",
    "slug": "guardrail-correctness-trial-at-four-agents",
    "title": "Guardrail / correctness trial at four agents",
    "interpretation": "Exercises the guard configuration at deep context. Use errors, preemptions and completion behaviour as correctness gates before considering speed.",
    "version": "rocm-7.14",
    "provenance": "ROCm 7.14 by recorded active profile and 6\u20138 October collection date; no immutable image ID captured per trace.",
    "included": false,
    "selection_reason": "A guardrail/correctness configuration probe; useful qualification history but not a matched performance case",
    "source_name_sha256": "3e96b15d72e275b78271af1f4e73442857b1171f47f1547000f13972255c923e"
  },
  {
    "legacy_id": "RUN-18",
    "slug": "speculative-depth-eight-versus-the-four-agent-baseline",
    "title": "Speculative-depth eight versus the four-agent baseline",
    "interpretation": "A/B of a wider draft setting under the same deep four-agent load. The wider draft is expected to consume more KV and verification work; evaluate KV capacity, ITL tail and throughput, not only average decode.",
    "version": "rocm-7.14",
    "provenance": "ROCm 7.14 by recorded active profile and 6\u20138 October collection date; no immutable image ID captured per trace.",
    "included": false,
    "selection_reason": "An eight-token speculation variant; draft-depth changes KV reservations and prevents an isolated runtime comparison",
    "source_name_sha256": "2c9f5926caa813aac8c3448f4065914958a52e14aeff34e7b31221be0ec6a977"
  },
  {
    "legacy_id": "RUN-19",
    "slug": "six-agent-capacity-bound-run-incomplete",
    "title": "Six-agent capacity-bound run, incomplete",
    "interpretation": "Deliberately runs beyond the four-sequence scheduler capacity so agents queue; the archived attempt failed to produce a valid completed benchmark. Treat as a failure-boundary observation, not a performance result.",
    "version": "rocm-7.14",
    "provenance": "ROCm 7.14 by recorded active profile and 6\u20138 October collection date; no immutable image ID captured per trace.",
    "included": false,
    "selection_reason": "The six-agent capacity-bound attempt was incomplete; it is not a valid completed performance result",
    "source_name_sha256": "23579f70949c31af8df10d2955b65cdcbfda8f406054f776e8f714d09fef64c4"
  },
  {
    "legacy_id": "RUN-20",
    "slug": "real-coding-agent-fleet-six-agents",
    "title": "Real coding-agent fleet, six agents",
    "interpretation": "Runs real tool-using agents to expose scheduler queuing and realistic context growth. Early harness configuration produced zero usable artifacts; use only the later qualified agent runs for performance conclusions.",
    "version": "rocm-7.14",
    "provenance": "ROCm 7.14 by recorded active profile and 6\u20138 October collection date; no immutable image ID captured per trace.",
    "included": false,
    "selection_reason": "An early six-agent real-agent harness trial produced no usable artefacts; it is not a successful task-completion result",
    "source_name_sha256": "2dc9e5183b17e723966db698c459e5cdcd738659268cac862be4461932747672"
  },
  {
    "legacy_id": "RUN-21",
    "slug": "single-agent-real-coding-task",
    "title": "Single-agent real coding task",
    "interpretation": "Checks end-to-end tool use, response quality signals and completion on the actual coding workflow. It is a functional workload and not comparable to token-padding throughput tests.",
    "version": "rocm-7.14",
    "provenance": "ROCm 7.14 by recorded active profile and 6\u20138 October collection date; no immutable image ID captured per trace.",
    "included": false,
    "selection_reason": "A single-agent functional coding task; different workload and fleet size from the selected synthetic runtime comparison",
    "source_name_sha256": "6c69db3ab5c8d7a0660a256e927046d4e3ee4373e3aeda79c116ede39a206dd5"
  },
  {
    "legacy_id": "RUN-22",
    "slug": "instrumentation-sanity-pass",
    "title": "Instrumentation sanity pass",
    "interpretation": "Verifies that telemetry collection and counters move coherently. Use it to validate instruments, not to compare serving performance.",
    "version": "rocm-7.14",
    "provenance": "ROCm 7.14 by recorded active profile and 6\u20138 October collection date; no immutable image ID captured per trace.",
    "included": false,
    "selection_reason": "A short instrumentation sanity check; insufficient workload coverage for performance ranking",
    "source_name_sha256": "ba6ec3cd49657886cb32520672b52d6684f9d008b37689915f51a051c7716e47"
  },
  {
    "legacy_id": "RUN-23",
    "slug": "second-instrumentation-sanity-pass",
    "title": "Second instrumentation sanity pass",
    "interpretation": "Repeat/extension of the telemetry sanity check. Short duration and small sample count make it unsuitable for latency or throughput ranking.",
    "version": "rocm-7.14",
    "provenance": "ROCm 7.14 by recorded active profile and 6\u20138 October collection date; no immutable image ID captured per trace.",
    "included": false,
    "selection_reason": "A second short instrumentation check; it validates metrics rather than serving capacity",
    "source_name_sha256": "1d17c1c2dac023ddf243fbd88ba16f20bd6caa8a7888d1db952cf9aa98151c8b"
  },
  {
    "legacy_id": "RUN-24",
    "slug": "rocm-base-image-four-agent-stress-run",
    "title": "ROCm base-image four-agent stress run",
    "interpretation": "Sustained four-agent load on the newer runtime stack. Compare with older-stack data only as an indicative comparison because configuration and depth caps differ; this is a stress qualification.",
    "version": "rocm-10.1",
    "provenance": "The 17 October journal explicitly identifies this stress workload as ROCm 10.1.",
    "included": true,
    "selection_reason": "Relevant ROCm 10.1 four-agent stress reference",
    "source_name_sha256": "1e089b14f51f4f8d6c53c4a338ba385835868002472e9c33f67fe2028c69cf29"
  },
  {
    "legacy_id": "RUN-25",
    "slug": "compaction-jitter-and-prefix-head-preservation",
    "title": "Compaction jitter and prefix-head preservation",
    "interpretation": "Tests staggered compaction and preservation of early context under four-agent load. Read hit/transfer share and long stalls together; the run includes mixed backing-store conditions.",
    "version": "rocm-7.14",
    "provenance": "ROCm 7.14 by recorded active profile and 6\u20138 October collection date; no immutable image ID captured per trace.",
    "included": false,
    "selection_reason": "Compaction jitter and prefix-preservation settings changed; several workload/cache effects are mixed",
    "source_name_sha256": "5e013fb98f8f5ef61e3a22fe86d5dcfbd07dfa2d65a0229c1e0785bda0ae98a7"
  },
  {
    "legacy_id": "RUN-26",
    "slug": "runtime-jit-instrumentation-sanity",
    "title": "Runtime/JIT instrumentation sanity",
    "interpretation": "Confirms the updated runtime/JIT path starts and emits expected telemetry. Not a throughput benchmark.",
    "version": "rocm-7.14",
    "provenance": "ROCm 7.14 by recorded active profile and 6\u20138 October collection date; no immutable image ID captured per trace.",
    "included": false,
    "selection_reason": "A runtime/JIT startup sanity check; it is not a sustained performance workload",
    "source_name_sha256": "e9e2d2467ded1d6a4bd3a257bdb6bf1782ff55de1475b0603ac6ba480ceb0421"
  },
  {
    "legacy_id": "RUN-27",
    "slug": "second-runtime-jit-sanity-pass",
    "title": "Second runtime/JIT sanity pass",
    "interpretation": "Short follow-up sanity sample. Its purpose is startup and metric validity rather than workload capacity.",
    "version": "rocm-7.14",
    "provenance": "ROCm 7.14 by recorded active profile and 6\u20138 October collection date; no immutable image ID captured per trace.",
    "included": false,
    "selection_reason": "A short follow-up runtime/JIT sanity check; it is not a capacity or latency qualification",
    "source_name_sha256": "1361265c724038477df761312cfd5d069b1620d90d60952a95f2b97405b6baec"
  },
  {
    "legacy_id": "RUN-28",
    "slug": "host-memory-and-storage-telemetry-during-the-link-storage-campaign",
    "title": "Host-memory and storage telemetry during the link/storage campaign",
    "interpretation": "Companion host sampler for the corresponding engine run. Use it to correlate available memory, swap, VRAM and I/O with stalls; it is not an independent benchmark.",
    "version": "rocm-7.14",
    "provenance": "ROCm 7.14 by recorded active profile and 6\u20138 October collection date; no immutable image ID captured per trace.",
    "included": false,
    "selection_reason": "A resource companion to the omitted link/storage campaign; it is not an independent benchmark",
    "source_name_sha256": "6398e2ea7565663e8ccef3d197714878b81e4ac419f127450113f6f98cb89313"
  },
  {
    "legacy_id": "RUN-29",
    "slug": "host-memory-trace-for-overflow-stress",
    "title": "Host-memory trace for overflow stress",
    "interpretation": "Companion memory trace for the intentional overflow run. Look for tier activation, swap and memory headroom; do not read accumulated file footprint as live cache occupancy.",
    "version": "rocm-7.14",
    "provenance": "ROCm 7.14 by recorded active profile and 6\u20138 October collection date; no immutable image ID captured per trace.",
    "included": false,
    "selection_reason": "A resource companion to the intentional overflow test; it describes a boundary case",
    "source_name_sha256": "bc5fb5c11eeba069c8643fd6597012b5963fde4f9029d484943dbd226a9151be"
  },
  {
    "legacy_id": "RUN-30",
    "slug": "host-memory-trace-for-the-reduced-tier-comparison",
    "title": "Host-memory trace for the reduced-tier comparison",
    "interpretation": "Correlates host pressure and storage behaviour with the smaller-tier run. Interpret counter deltas as rates, and gauges as sampled state.",
    "version": "rocm-7.14",
    "provenance": "ROCm 7.14 by recorded active profile and 6\u20138 October collection date; no immutable image ID captured per trace.",
    "included": false,
    "selection_reason": "A resource companion to the reduced-tier tuning trial; its configuration is outside the selected comparison",
    "source_name_sha256": "8ae9022fffa2586aafc334058bb2a9e8ea211a38dd67f525a3c6e8ef3abd599b"
  },
  {
    "legacy_id": "RUN-31",
    "slug": "host-memory-trace-for-the-ram16-four-agent-milestone",
    "title": "Host-memory trace for the RAM16 four-agent milestone",
    "interpretation": "Companion resource trace for the central four-agent single-card result. Check swap stays controlled while the shared-memory tier is active.",
    "version": "rocm-7.14",
    "provenance": "ROCm 7.14 by recorded active profile and 6\u20138 October collection date; no immutable image ID captured per trace.",
    "included": true,
    "selection_reason": "Core single-card RAM16 capacity milestone or its resource trace",
    "source_name_sha256": "ff4dd47bafcac6e6d8c4998c9472d4fd6f1b9533f0a9e0c4874261ecb1b09ccf"
  },
  {
    "legacy_id": "RUN-32",
    "slug": "host-memory-trace-for-the-ram16-three-agent-follow-up",
    "title": "Host-memory trace for the RAM16 three-agent follow-up",
    "interpretation": "Resource companion for the deeper three-agent test. Compare memory headroom and swap with the four-agent tier run.",
    "version": "rocm-7.14",
    "provenance": "ROCm 7.14 by recorded active profile and 6\u20138 October collection date; no immutable image ID captured per trace.",
    "included": true,
    "selection_reason": "Core single-card RAM16 capacity milestone or its resource trace",
    "source_name_sha256": "7785391efd94def163f28d5867bd815b36d15e5d32e74ed83eb034f460f0f212"
  },
  {
    "legacy_id": "RUN-33",
    "slug": "host-memory-trace-for-the-guardrail-trial",
    "title": "Host-memory trace for the guardrail trial",
    "interpretation": "Companion resource sampler. Correlate pressure with any guardrail or correctness events in the engine series.",
    "version": "rocm-7.14",
    "provenance": "ROCm 7.14 by recorded active profile and 6\u20138 October collection date; no immutable image ID captured per trace.",
    "included": false,
    "selection_reason": "A resource companion to the guardrail probe; it is not an independent runtime comparison",
    "source_name_sha256": "2f5e9d46c9cbea93b4a02d4073cb46258dc57f563cdf2fbaee47edd36b2186ff"
  },
  {
    "legacy_id": "RUN-34",
    "slug": "host-memory-trace-for-the-speculative-depth-a-b",
    "title": "Host-memory trace for the speculative-depth A/B",
    "interpretation": "Companion sampler for the draft-depth comparison. Helps explain KV reservation and memory-pressure changes.",
    "version": "rocm-7.14",
    "provenance": "ROCm 7.14 by recorded active profile and 6\u20138 October collection date; no immutable image ID captured per trace.",
    "included": false,
    "selection_reason": "The companion recorder contains no usable samples, so no graph or performance result is available",
    "source_name_sha256": "342da4322887d746aee75fa1a9aa8265bf01d7b1d33aace76b310554c42f05c1"
  },
  {
    "legacy_id": "RUN-35",
    "slug": "host-memory-trace-for-the-six-agent-real-agent-campaign",
    "title": "Host-memory trace for the six-agent real-agent campaign",
    "interpretation": "Companion sampler for the agent fleet. Separate host resource behaviour from the agent harness configuration and its task-completion outcomes.",
    "version": "rocm-7.14",
    "provenance": "ROCm 7.14 by recorded active profile and 6\u20138 October collection date; no immutable image ID captured per trace.",
    "included": false,
    "selection_reason": "A resource companion to the early six-agent harness trial; its telemetry does not establish successful task completion",
    "source_name_sha256": "3a45c2bb2dbaa603d71d12c346b7ae6ee31760fffc993f0e5a8de11d6717817a"
  }
]