Skip to content

Commit 9ee5d21

Browse files
authored
Merge pull request #223 from interscript/docs/engram-verdict
docs(RESULTS): engram verdict — 4.6679, not separated
2 parents 4f036f8 + a3a8f7f commit 9ee5d21

1 file changed

Lines changed: 24 additions & 0 deletions

File tree

‎docs/RESULTS.md‎

Lines changed: 24 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -843,3 +843,27 @@ The int8 encoder costs ~0.01pp over A; everything sits inside the
843843
drift band and inside the not-separated paired CI. Static's place in
844844
the catalog, when the release is called: a server/CPU tier where
845845
decode speed outweighs artifact size.
846+
847+
## ara-diac-small-2-1-engram — 4.6679: NOT SEPARATED from 2.1 (2026-09-29)
848+
849+
The lexical-memory run (TODO.impl/10): one 2M×32 byte-n-gram table at
850+
encoder block 3, zero-init, table on the Sinkhorn-balanced rule (5× lr),
851+
identical 6ep sequence-KD recipe and canonical r7 labels (sha
852+
e70ce991), single variable vs run-007 (2.1, 4.5701).
853+
854+
Result: **4.6679** full-set (n=1200), gap to teacher 2.25pp CI95
855+
[2.03, 2.47] — the delta vs 2.1 (+0.10pp) is small and inside the
856+
drift band; paired bootstrap does not separate it from 2.1. Eval
857+
methodology note: the first eval accidentally dropped the memory
858+
(vanilla loader — the PKM lesson again); the gate number is
859+
with-table via load_student_with_engram. The dropped-table score is
860+
the no-memory control.
861+
862+
Verdict: FLAT. Lexical memory neither helped nor hurt at this scale
863+
and dose — the encoder absorbed the capacity without converting it to
864+
frontier movement on the news/wiki residual. The architecture ledger
865+
now reads: depth cut ✗ (2 variants), lexical memory ✗ (flat),
866+
on-policy ✗, teacher routing ✗, soup ✗. The 2.1 recipe remains the
867+
frontier at 4.5701. Remaining measurable levers live in the recipe
868+
lane (r8: headwise Muon + Sinkhorn arm) and the release lane
869+
(static-int8 re-export).

0 commit comments

Comments
 (0)