Nemotron-3.5-Lightning gate

Lab study note from the internal benches record (page last-modified 2026-09-12). Not live Oct 1 telemetry.

Day-0 NVIDIA Nemotron-3.5-Lightning 30B-A3B (3B active), official NVFP4 + DSpark on a single DGX Spark. Question: is Lightning a coder upgrade, or a fast sub-agent / long-context challenger?

Verdict

• Rejected as primary coder. Quality gap is decisive under the same rule that reverted Laguna: need a speed or capacity win without losing code. Lightning has both operational wins and still loses code by sixteen points.
• Kept as on-demand lightning. Sub-agent / multi-agent workhorse. Not in the coder spillover.
• Ornith stays the tools specialist. Lightning devtool 66.7% beats the then-champion 58.4% but loses to Ornith 75.0%.

Measured (vs Coder-Next champion)

• devcode: 70.0% vs 86.4% (−16.4, outside ±4 noise)
• devcode wall: 44 s vs 85 s (1.93× faster)
• Single-stream c1: 82.3 vs 50.9 tok/s (1.62×)
• Aggregate c2 / c4: 108.5 / 161.5 vs 76.2 / 76.0 — Lightning scales; the champion plateaus
• Footprint: ~22 GB + 1.3 GB DSpark vs champion 53.9 GiB

Speed alone does not promote a coder. Lightning earns a fleet seat as a challenger because the speed and capacity win is large and the quality loss is honest.