You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Found by review of #661 (row LTX25-RETIRE-DEAD-ARMS) as finding F6. Filed rather than fixed there because .agents/specs/ltx-2-5.md is the operator-owned campaign spec and that row is explicitly scoped out of editing it (spec ltx25-retire-dead-arms.md §3 "Out").
The stale claim
.agents/specs/ltx-2-5.md:291, in the §2 Out (recorded as owed, not silently dropped) list:
multishot is fabricated. #661 retired the kMultishot enumerator after re-deriving the absence against both pinned references, twice — once by the implementer and once independently by the reviewer, searching the subject rather than our own phrasing (the #604 trap):
multishot / multi_shot / multi-shot: 0 hits in Lightricks/LTX-2 fd4ded7f and huggingface/diffusers 3a2f35d4.
Every upstream shot is ONE camera take — duration_head.py:1,5 "predicts shot duration"; README.md:136 "think like a cinematographer describing a shot list"; diffusers pipelines/ltx2/utils.py:217 "Shot type (exactly one: extreme wide shot / wide shot / medium shot / …)".
storyboard / chapter: 0 hits. Every scene is PySceneDetect in the trainer or scene-linear HDR.
retake.py, keyframe_interpolation.py, dfr_pipeline.py and dubit.py were read individually; none composes several takes.
ltx-pipelines documents 11 pipelines and diffusers registers 16 ltx2/ modules; none is multi-shot.
So there is nothing to owe. A spec that records a fabricated arm as owed sends the next reader upstream to look for it, and main currently carries that claim in the campaign spec even though the code it justified has been removed.
Two smaller items on the same line, for the same edit:
"multi-GPU / CFG parallelism" should be multi-GPU parallelism. fix(LTX25-RETIRE-DEAD-ARMS): retire the invented refusals, refuse the ignored extra (#644, #611) #661 renamed kCfgParallelism → kMultiGpuParallelism after finding 0 cfg hits in either multigpu/ tree; upstream's forms are sequence-parallel (multigpu/sp_builder.py:25), tiled data parallel (multigpu/tdp_builder.py:25, upscale only) and distributed VAE decode (ltx-core multigpu/vae/distributed_decoder.py:204-256), and upstream's own CFG is a batch dimension, never a device — utils/denoisers.py:7-8, _guided_denoise "batches all guidance passes into a single transformer call".
int8-convrot is correctly listed as out of scope, but the parenthetical reason is worth aligning with what was measured: convrot really is 0 hits, but int8 is unreachable rather than absent upstream — trainer-only for anything wired, plus one dead per-row int8 quantize kernel in the ltx-kernelsinference package (blockwise/triton_ops.py:35,43, reached only by its own alias at :436).
Done when
.agents/specs/ltx-2-5.md §2 "Out" no longer names multishot, cites .agents/specs/ltx25-retire-dead-arms.md §1.1 as the record for why, and the multi-GPU entry is renamed. Owner: whoever holds the ROAD-V1-LTX25 campaign.
Found by review of #661 (row
LTX25-RETIRE-DEAD-ARMS) as finding F6. Filed rather than fixed there because.agents/specs/ltx-2-5.mdis the operator-owned campaign spec and that row is explicitly scoped out of editing it (specltx25-retire-dead-arms.md§3 "Out").The stale claim
.agents/specs/ltx-2-5.md:291, in the §2 Out (recorded as owed, not silently dropped) list:multishotis fabricated. #661 retired thekMultishotenumerator after re-deriving the absence against both pinned references, twice — once by the implementer and once independently by the reviewer, searching the subject rather than our own phrasing (the #604 trap):multishot/multi_shot/multi-shot: 0 hits in Lightricks/LTX-2fd4ded7fand huggingface/diffusers3a2f35d4.shotis ONE camera take —duration_head.py:1,5"predicts shot duration";README.md:136"think like a cinematographer describing a shot list"; diffuserspipelines/ltx2/utils.py:217"Shot type (exactly one: extreme wide shot / wide shot / medium shot / …)".storyboard/chapter: 0 hits. Everysceneis PySceneDetect in the trainer or scene-linear HDR.retake.py,keyframe_interpolation.py,dfr_pipeline.pyanddubit.pywere read individually; none composes several takes.ltx-pipelinesdocuments 11 pipelines and diffusers registers 16ltx2/modules; none is multi-shot.So there is nothing to owe. A spec that records a fabricated arm as owed sends the next reader upstream to look for it, and
maincurrently carries that claim in the campaign spec even though the code it justified has been removed.Two smaller items on the same line, for the same edit:
kCfgParallelism→kMultiGpuParallelismafter finding 0cfghits in eithermultigpu/tree; upstream's forms are sequence-parallel (multigpu/sp_builder.py:25), tiled data parallel (multigpu/tdp_builder.py:25, upscale only) and distributed VAE decode (ltx-core multigpu/vae/distributed_decoder.py:204-256), and upstream's own CFG is a batch dimension, never a device —utils/denoisers.py:7-8,_guided_denoise"batches all guidance passes into a single transformer call".int8-convrotis correctly listed as out of scope, but the parenthetical reason is worth aligning with what was measured:convrotreally is 0 hits, but int8 is unreachable rather than absent upstream — trainer-only for anything wired, plus one dead per-row int8 quantize kernel in theltx-kernelsinference package (blockwise/triton_ops.py:35,43, reached only by its own alias at:436).Done when
.agents/specs/ltx-2-5.md§2 "Out" no longer namesmultishot, cites.agents/specs/ltx25-retire-dead-arms.md§1.1 as the record for why, and the multi-GPU entry is renamed. Owner: whoever holds theROAD-V1-LTX25campaign.Related: #644, #604, #661.