Validate repeated learned RMSNorm functions with CPU evidence
This commit is contained in:
+10
@@ -128,3 +128,13 @@ On 2026-11-09 the user explicitly changed retention: keep the CPU functional pil
|
||||
checkpoint until the user explicitly requests deletion. Completion, timeout, failure
|
||||
and archive validation do not authorize cleanup. The earlier pilot cleanup remains
|
||||
a historical action; do not apply its automatic cleanup step to the current run.
|
||||
|
||||
## CPU functional follow-up outcome
|
||||
|
||||
The executed CPU study found a learned RMSNorm function-repetition example at text
|
||||
layer indices 12/13. Use same-input function error and a uniform analytic bound as
|
||||
primary evidence, with separate heldout network substitution checks. Costs are not
|
||||
a success condition under the latest user instruction. See the
|
||||
[executed findings](CPU_FUNCTIONAL_FINDINGS.md) and
|
||||
[function-repetition criterion](LEARNED_FUNCTION_REPETITION.md).
|
||||
Keep whole-module, neuron, normalization and algebraic-reparameterization results distinct.
|
||||
|
||||
Reference in New Issue
Block a user