<feed xmlns='http://www.w3.org/2005/Atom'>
<title>faeval.git/protocol/examples/penalty_partial_audit.py, branch master</title>
<subtitle>Unnamed repository; edit this file 'description' to name the repository.
</subtitle>
<link rel='alternate' type='text/html' href='https://git.blackhao.com/faeval.git/'/>
<entry>
<title>Partial protocol audit on penalized DFA: (a)+(b) pass, (d) still fires</title>
<updated>2026-04-08T04:17:45+00:00</updated>
<author>
<name>YurenHao0426</name>
<email>Blackhao0426@gmail.com</email>
</author>
<published>2026-04-08T04:17:45+00:00</published>
<link rel='alternate' type='text/html' href='https://git.blackhao.com/faeval.git/commit/?id=5771a122300f9d30a6290fcbfc9bffb5f380e648'/>
<id>5771a122300f9d30a6290fcbfc9bffb5f380e648</id>
<content type='text'>
3-seed analysis of DFA + lambda=1e-2 ||f||^2 penalty using only the data
already in the existing penalty JSON logs (no checkpoint or full layer
norms needed):

  (a) per-block growth: avg ~8x per block (geom mean), well below 50x
      threshold. PASS likely (with small caveat that max could differ
      from mean).
  (b) BP grad floor:    g_2 = 8-10e-7 across 3 seeds, 10x above the
      1e-7 floor. PASS exact.
  (d) frozen baseline:  margin = 1.35-1.45 pp (mean 1.38) &lt; 2 pp
      required. FIRE on all 3 seeds.

Aggregate partial verdict: protocol catches the SECOND failure mode
(direction quality / passive blocks) on penalized DFA even though it
PASSES the scale-related diagnostics. This is the cleanest possible
evidence that the two failure modes are separable: the penalty fixes
the scale failure but not the direction failure. The protocol's (d)
diagnostic is the right test for the second failure mode and it still
fires after the penalty rescue.

This is the §4 'two failure modes' evidence that doesn't depend on the
direction-quality direct test (which is still running). The (d)
diagnostic alone shows the separation.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
3-seed analysis of DFA + lambda=1e-2 ||f||^2 penalty using only the data
already in the existing penalty JSON logs (no checkpoint or full layer
norms needed):

  (a) per-block growth: avg ~8x per block (geom mean), well below 50x
      threshold. PASS likely (with small caveat that max could differ
      from mean).
  (b) BP grad floor:    g_2 = 8-10e-7 across 3 seeds, 10x above the
      1e-7 floor. PASS exact.
  (d) frozen baseline:  margin = 1.35-1.45 pp (mean 1.38) &lt; 2 pp
      required. FIRE on all 3 seeds.

Aggregate partial verdict: protocol catches the SECOND failure mode
(direction quality / passive blocks) on penalized DFA even though it
PASSES the scale-related diagnostics. This is the cleanest possible
evidence that the two failure modes are separable: the penalty fixes
the scale failure but not the direction failure. The protocol's (d)
diagnostic is the right test for the second failure mode and it still
fires after the penalty rescue.

This is the §4 'two failure modes' evidence that doesn't depend on the
direction-quality direct test (which is still running). The (d)
diagnostic alone shows the separation.
</pre>
</div>
</content>
</entry>
</feed>
