wassname/evil_MoE
1
0
Fork 0
mirror of https://github.com/wassname/evil_MoE.git synced 2026-06-27 17:48:43 +08:00
Code Issues Packages Projects Releases Wiki Activity

journal: A5 baseline confirmed -- held-out file_marker+sentinel emerge on-policy (run_tests-only teacher), deploy hack 0.52 by step 40

Browse Source 
Co-Authored-By: Claudypoo <288921227+claudypoo@users.noreply.github.com>
This commit is contained in:
wassname
2026-06-04 05:33:36 +00:00
parent a162eded65
commit e91e095596
1 changed files with 11 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
RESEARCH_JOURNAL.md
+11
View File
@@ -2,6 +2,17 @@
Append-only. New entries at the top, date-stamped. Never edit old entries.
## 2026-06-04 (c) — A5 baseline confirmed: BOTH held-out modes (file_marker + sentinel) emerge robustly on-policy under a run_tests-only teacher
Follow-up to (b), which flagged the held-out file_marker emergence as a single transient spike (step 18) and held judgement. By step ~36-41 it is clearly sustained, so the A5 baseline precondition is met.
**Job 103 (A5 baseline, vanilla + `--teacher-modes run_tests`, #185), steps 36-41.**
- [obs] hk_fm (file_marker, HELD-OUT) fires 6/2/7/7/0/3 across steps 36-41; cumulative 57 file_marker hacks over the run so far. Not a blip.
- [obs] hk_se (sentinel, also HELD-OUT) emerges too: 7 and 5 at steps 37-38.
- [obs] deploy hack rises 0.000 (s0) -> 0.266 (s20) -> 0.276 (s30) -> 0.516 (s40); deploy solve 0.25 -> 0.37. lp_s steady ~-0.10 (no collapse).
- [verdict] both non-demoed modes emerge on-policy with a teacher that only ever demonstrates run_tests. The route gate (`teacher OR hacked_E`) is blind to file_marker/sentinel (hacked_E==0 on them, per the (a) E-by-mode table), so this is genuine no-label emergence. Job 103's resolve criterion ("file_marker deploy hack > 0 else inconclusive") is satisfied -- the design-B teacher-seeding fallback is NOT needed. Job 104 (route2, run_tests-only v_grad) now has a real held-out baseline to suppress.
- [next] confirm at the end-of-run per-mode deploy split that file_marker deploy hack is materially > 0 (the deploy-eval log only prints the aggregate; #164 artifact carries the per-mode breakdown).
## 2026-06-04 (b) — job 97 gentle-probe: vanilla-200 does NOT collapse on stabilised preset; A5 baseline (job 103) sees held-out file_marker emerge on-policy
**Job 97 (A4 vanilla-200 gentle collapse probe, #187).** Finished, succeeded.