“full burn-in interval completes without hang or unrecoverable link errors” addresses short network benchmarks failed to detect a time-dependent collective fault, but the current hardware or infrastructure issue is peak sample does not demonstrate stable collective performance over time. The option “sustained measurements remain above the prescribed lower bound throughout” is more directly tied to the required outcome.

“isolated node repair allows collective burn-in without GPU errors” addresses node GPU faults were not distinguished from network communication failure, but the current hardware or infrastructure issue is peak sample does not demonstrate stable collective performance over time. The option “sustained measurements remain above the prescribed lower bound throughout” is more directly tied to the required outcome.

“long-run error growth remains within published site limits” addresses passing collectives can conceal degrading fabric signal margins, but the current hardware or infrastructure issue is peak sample does not demonstrate stable collective performance over time. The option “sustained measurements remain above the prescribed lower bound throughout” is more directly tied to the required outcome.

“monitor cooling throttles and per-GPU clocks together with NCCL progress” addresses fabric burn-in also exercises node thermal and compute stability, but the current hardware or infrastructure issue is node GPU faults were not distinguished from network communication failure. The option “correlate NCCL failure timing with per-GPU Xid and interconnect events” is more directly tied to the required outcome.

“run prolonged NCCL collective loops with telemetry and timeout thresholds” addresses short network benchmarks failed to detect a time-dependent collective fault, but the current hardware or infrastructure issue is node GPU faults were not distinguished from network communication failure. The option “correlate NCCL failure timing with per-GPU Xid and interconnect events” is more directly tied to the required outcome.

“use time-series NCCL throughput and reliability checks across a fixed burn-in period” addresses peak sample does not demonstrate stable collective performance over time, but the current hardware or infrastructure issue is node GPU faults were not distinguished from network communication failure. The option “correlate NCCL failure timing with per-GPU Xid and interconnect events” is more directly tied to the required outcome.

“full burn-in interval completes without hang or unrecoverable link errors” addresses short network benchmarks failed to detect a time-dependent collective fault, but the current hardware or infrastructure issue is node GPU faults were not distinguished from network communication failure. The option “isolated node repair allows collective burn-in without GPU errors” is more directly tied to the required outcome.

“repaired cooling maintains normal clocks and stable collective iteration time” addresses fabric burn-in also exercises node thermal and compute stability, but the current hardware or infrastructure issue is node GPU faults were not distinguished from network communication failure. The option “isolated node repair allows collective burn-in without GPU errors” is more directly tied to the required outcome.

“sustained measurements remain above the prescribed lower bound throughout” addresses peak sample does not demonstrate stable collective performance over time, but the current hardware or infrastructure issue is node GPU faults were not distinguished from network communication failure. The option “isolated node repair allows collective burn-in without GPU errors” is more directly tied to the required outcome.

“correlate NCCL failure timing with per-GPU Xid and interconnect events” addresses node GPU faults were not distinguished from network communication failure, but the current hardware or infrastructure issue is fabric burn-in also exercises node thermal and compute stability. The option “monitor cooling throttles and per-GPU clocks together with NCCL progress” is more directly tied to the required outcome.

“run prolonged NCCL collective loops with telemetry and timeout thresholds” addresses short network benchmarks failed to detect a time-dependent collective fault, but the current hardware or infrastructure issue is fabric burn-in also exercises node thermal and compute stability. The option “monitor cooling throttles and per-GPU clocks together with NCCL progress” is more directly tied to the required outcome.

“pin NCCL settings GPU count and message profile for accepted burn-in runs” addresses changing benchmark parameters invalidates longitudinal stability comparison, but the current hardware or infrastructure issue is fabric burn-in also exercises node thermal and compute stability. The option “monitor cooling throttles and per-GPU clocks together with NCCL progress” is more directly tied to the required outcome.

“isolated node repair allows collective burn-in without GPU errors” addresses node GPU faults were not distinguished from network communication failure, but the current hardware or infrastructure issue is fabric burn-in also exercises node thermal and compute stability. The option “repaired cooling maintains normal clocks and stable collective iteration time” is more directly tied to the required outcome.

“all racks sustain accepted bandwidth and service stability during duration” addresses fabric congestion control was never validated at production concurrency, but the current hardware or infrastructure issue is fabric burn-in also exercises node thermal and compute stability. The option “repaired cooling maintains normal clocks and stable collective iteration time” is more directly tied to the required outcome.

“comparable time-series baselines reveal genuine regressions rather than test drift” addresses changing benchmark parameters invalidates longitudinal stability comparison, but the current hardware or infrastructure issue is fabric burn-in also exercises node thermal and compute stability. The option “repaired cooling maintains normal clocks and stable collective iteration time” is more directly tied to the required outcome.

“collect network FEC retransmit and error trends during NCCL burn-in” addresses passing collectives can conceal degrading fabric signal margins, but the current hardware or infrastructure issue is redundancy failover and fault visibility are untested under sustained collectives. The option “inject controlled single-rail interruption during monitored NCCL burn-in” is more directly tied to the required outcome.

“run rack-spanning NCCL burn-in at planned scale with switch queue metrics” addresses fabric congestion control was never validated at production concurrency, but the current hardware or infrastructure issue is redundancy failover and fault visibility are untested under sustained collectives. The option “inject controlled single-rail interruption during monitored NCCL burn-in” is more directly tied to the required outcome.

“use time-series NCCL throughput and reliability checks across a fixed burn-in period” addresses peak sample does not demonstrate stable collective performance over time, but the current hardware or infrastructure issue is redundancy failover and fault visibility are untested under sustained collectives. The option “inject controlled single-rail interruption during monitored NCCL burn-in” is more directly tied to the required outcome.

“long-run error growth remains within published site limits” addresses passing collectives can conceal degrading fabric signal margins, but the current hardware or infrastructure issue is redundancy failover and fault visibility are untested under sustained collectives. The option “supported failover preserves expected job behavior with clear rail alarms” is more directly tied to the required outcome.

“repaired cooling maintains normal clocks and stable collective iteration time” addresses fabric burn-in also exercises node thermal and compute stability, but the current hardware or infrastructure issue is redundancy failover and fault visibility are untested under sustained collectives. The option “supported failover preserves expected job behavior with clear rail alarms” is more directly tied to the required outcome.

“full burn-in interval completes without hang or unrecoverable link errors” addresses short network benchmarks failed to detect a time-dependent collective fault, but the current hardware or infrastructure issue is redundancy failover and fault visibility are untested under sustained collectives. The option “supported failover preserves expected job behavior with clear rail alarms” is more directly tied to the required outcome.

Useful for passing collectives can conceal degrading fabric signal margins, but it does not remove the specific condition: changing benchmark parameters invalidates longitudinal stability comparison.

“use time-series NCCL throughput and reliability checks across a fixed burn-in period” addresses peak sample does not demonstrate stable collective performance over time, but the current hardware or infrastructure issue is changing benchmark parameters invalidates longitudinal stability comparison. The option “pin NCCL settings GPU count and message profile for accepted burn-in runs” is more directly tied to the required outcome.

“monitor cooling throttles and per-GPU clocks together with NCCL progress” addresses fabric burn-in also exercises node thermal and compute stability, but the current hardware or infrastructure issue is changing benchmark parameters invalidates longitudinal stability comparison. The option “pin NCCL settings GPU count and message profile for accepted burn-in runs” is more directly tied to the required outcome.

“repaired cooling maintains normal clocks and stable collective iteration time” addresses fabric burn-in also exercises node thermal and compute stability, but the current hardware or infrastructure issue is changing benchmark parameters invalidates longitudinal stability comparison. The option “comparable time-series baselines reveal genuine regressions rather than test drift” is more directly tied to the required outcome.

“full burn-in interval completes without hang or unrecoverable link errors” addresses short network benchmarks failed to detect a time-dependent collective fault, but the current hardware or infrastructure issue is changing benchmark parameters invalidates longitudinal stability comparison. The option “comparable time-series baselines reveal genuine regressions rather than test drift” is more directly tied to the required outcome.

“long-run error growth remains within published site limits” addresses passing collectives can conceal degrading fabric signal margins, but the current hardware or infrastructure issue is changing benchmark parameters invalidates longitudinal stability comparison. The option “comparable time-series baselines reveal genuine regressions rather than test drift” is more directly tied to the required outcome.

“rerun the entire approved continuous HPL burn-in interval” addresses the validation run did not maintain uninterrupted stress for the required duration, but the current hardware or infrastructure issue is short HPL runs did not test sustained power thermal and memory stability. The option “perform extended qualified HPL burn-in under hardware monitoring” is more directly tied to the required outcome.

Useful for combined electrical headroom was not exercised under synchronized compute duty, but it does not remove the specific condition: short HPL runs did not test sustained power thermal and memory stability.

“capture clock power and thermal settings alongside each burn-in record” addresses power-policy differences prevent reliable comparison of sustained performance, but the current hardware or infrastructure issue is short HPL runs did not test sustained power thermal and memory stability. The option “perform extended qualified HPL burn-in under hardware monitoring” is more directly tied to the required outcome.

“result logs show the full planned active duration with no interruption” addresses the validation run did not maintain uninterrupted stress for the required duration, but the current hardware or infrastructure issue is short HPL runs did not test sustained power thermal and memory stability. The option “the full planned interval completes with valid residual and no reset” is more directly tied to the required outcome.

“clocks and FLOPS remain consistent after thermal equilibrium” addresses sustained matrix performance is limited by thermal throttling, but the current hardware or infrastructure issue is short HPL runs did not test sustained power thermal and memory stability. The option “the full planned interval completes with valid residual and no reset” is more directly tied to the required outcome.

“report contains compatible settings and reproduced performance within tolerance” addresses power-policy differences prevent reliable comparison of sustained performance, but the current hardware or infrastructure issue is short HPL runs did not test sustained power thermal and memory stability. The option “the full planned interval completes with valid residual and no reset” is more directly tied to the required outcome.