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
{{ message }}
Repository navigation
[WS1 Closeout][Backward] Reusable gradient-invariance harness and operator adapters #270
Parent: #266
Class: Must (blocks Full WS1 EXIT; required by #150 / C10)
Depends on: C1 (#267), C2 (#268)
Source: #153 Backward-pass consistency
Goal
Ensure ops and the full chain share one comparison semantic for training-style gradients under batch/chunk, so tests do not invent their own upstream grads or denominators.
Scope
Cross-config gradient-invariance API
Separate gradient accuracy (vs reference VJP) from invariance (across configs)
Fix across configs: upstream grad, loss reduction, active-token denominator
Compare on C2’s same logical sample/token multiset: N× B=1 singleton fixed-order aggregate vs one B=N
Compare all required trainable parameter gradients; give stable logical names for required activation/input VJPs
Register adapters for differentiable WS1 ops (OP_SPECS or equivalent; name-only mention in a chain report does not count)
Audit: no atomicAdd / no shape-dependent bwd accumulation on BI candidates
Gradient thresholds only from C1
Register and validate required gradient adapters separately for cuda_bf16 and triton_cuda_bf16; a missing Triton backward for a required differentiable node is red
Activity
feat(ws1): land C4 gradient-invariance harness and adapters (#270)