Preprint  ·  a hypothesis with measured corollaries

The Dose-Window Hypothesis

Order, calibration, and externalised knowledge in small language models — a hypothesis with measured corollaries

Chad St Thomas · CuriousGene / Tablinum

Abstract

This paper proposes and partially tests the Dose-Window Hypothesis: for a model of size N and a behaviour B, there is an interval [W_install, W_harm] in effective training exposure — examples × epochs, measured against the model's existing format lock — below which B does not install, and above which it saturates into template memorisation and erodes complementary behaviours, nearest neighbours first. The hypothesis emerged from an eight-week program training small language models (0.3B–8B) to investigate — answer from evidence, challenge false premises, abstain when evidence is absent, cite what each claim rests on — on a single 6 GB laptop GPU, with every score produced by frozen, deterministic instruments and paired controls.

Four measured corollaries support it and stand independently of it. (1) Order beats ingredients: the same category data cost 0.081 mixed into a base mixture and gained 0.016 as an isolated pulse followed by a format re-lock, at identical compute. (2) The quantisation floor is calibration, not bits: two 2-bit builds of one model, identical in file size and bit width, scored 0.014 and 0.708. (3) Knowledge divides cleanly: a static, runtime-editable fact table supplies the content half — lifting premise correction 4–5× at zero training, with a single 8B reaching 0.959 on the bench and 0.90 on a blind holdout — while the polarity half remains the model's job and fails below roughly 2B regardless of what the table supplies. (4) Interfaces leak: giving the model a retrieval tool scored 0.510–0.633 against 0.939 for retrieving before inference, through three separable failure modes.

The hypothesis is stated with its untested predictions; section 7 gives the applications at scale and the open agenda, and section 9 states what remains unestablished. The evaluation harness and CLI are released as open source.

1Measurement infrastructure

Every score in this paper comes from a frozen instrument with a deterministic grader and a paired control. This section defines what that means, how answers are graded, and how the reported numbers are bounded.

I · INSTRUMENTfrozen test setwritten and sealeddeterministic gradermatch · tail · entailmentoracle + shortcut checktrivial baseline < 0.90II · TRAININGbase substratefrozen, identity recordedstaged SFTpulse → re-lock + controldamage-aware OPDreverse-KL + anchored KLIII · DEPLOYMENTengram tablefacts + provenance, no trainingsubstrateaccept / reject / abstainrungscored at every quant levelevery measured failure becomes a new frozen item
Figure 1. The three phases of the method. Instruments are frozen before any training run. Deployment failures are fed back as new instrument items, closing the loop.

1.1 What an instrument is

A question set with a deterministic grader, written and sealed before any training run and never trained on. Four disciplines apply: the file, its generator, and its build seed are committed together and never rebuilt in place; training corpora are checked for shared gold values against every frozen set; every item's gold target grades against itself at 1.0 by construction; and compared conditions share item identities exactly, so the comparison is paired.

Standing guard

shortcut_check runs on every new premise or entailment set before it is trusted. It fits simple baselines — length ratio, lexical overlap, answer position — and fails the set if any exceeds 0.90. Backfilled across eight frozen instruments, the values were 0.783–0.867.

1.2 Controls and contamination

Every condition reported in this paper is paired with its control on identical items — an uplift without its baseline is not a result. Training corpora are re-graded for instrument overlap before every run, and the office evaluation instruments are deliberately not published, because a published evaluation set becomes a training set.

1.3 The grader

The production grader is strictly additive across three stages: exact and substring gold-value matching under a rejection lexicon, with unit normalisation; the same test applied to a tail window of the raw answer; and an NLI entailment check with the gold fact as premise and the answer as hypothesis, requiring P(entail) ≥ 0.80. Calibration: 0.991 entailment on a tight paraphrase, 0.715 on a vague one, correctly declined. Tests pin the bar at exactly 0.8.

1.4 Statistical treatment

For independent bounded scores, simultaneous two-sided intervals for each of m axis means use Hoeffding's inequality with a union bound:

2026-10-14T10:55:36.804267 image/svg+xml Matplotlib v3.10.8, https://matplotlib.org/ (1)

At α = 0.05, all four intervals jointly cover their population means with probability ≥ 0.95. Dependence between axes is permitted; independence of sampled questions is required. This is a conservative finite-sample bound, not a power calculation — with a perfect mean it needs ≥ 254 items per axis for the lower endpoint to reach 0.90. For paired comparisons on identical items, D_i = candidate_i − baseline_i in [−1, 1], and the radius doubles because the range width doubles.

Two further constraints on inference were measured. Identical prompt_sha256 produced only 3 of 30 byte-identical answers across server restarts, giving a ≈2-item noise band on n = 30 across server lifetimes; within-server comparisons are robust, absolute values are ±0.07. And scores are compared within a backend only, because kernel numerics can flip an argmax at the margin — cross-backend cells agree within ≤2 items, so curves are read within-sweep.

2The dose window

The order in which a behaviour is trained matters more than the data used to train it. Installing one behaviour by mixing its data into the base mixture cost score twice; applying the same data as an isolated pulse followed by a format re-lock produced the program's best result.

too littlethe windowtoo much0.000.250.500.751.00scoreeffective exposure (examples × epochs)W_installW_harmtarget behaviour installsprotected axes erodedv18 0.804mixing the behaviour data into the base mix:v19 0.768 v20 0.723v21 0.820pulse, then re-lock
Figure 2. The dose window. Below W_install the target behaviour does not install; above W_harm it saturates into template memorisation and erodes the protected axes, nearest neighbours first. Measured arms are placed by their construction.

2.1 The experiment

Table 1. Same data, same compute class, same base. The only variable is order and replay structure.
armconstructionoverallΔ baseline
v18format-locked baseline0.804—
v1934% SQuAD-v2 + premise, mixed into the main mix0.768−0.036
v2012% abstain-only, mixed into the main mix0.723−0.081
v21same category data, staged pulse → format re-lock0.820+0.016
Dose-window hypothesis

For a model of size N and behaviour B, there exists an interval [W_install, W_harm] in effective exposure — examples × epochs, measured against the model's existing format lock — such that below W_install the behaviour does not install, and above W_harm it saturates into template memorisation and erodes complementary behaviours, nearest neighbours first.

Status of its predictions. P1, windows widen with scale: supported at one size pair (0.6B → 1.2B, same recipe), untested beyond. P2, damage is dose-driven rather than data-driven: supported (v19/v20 vs v21; swapped-order control collapsed to 0.497). P3, recovery asymmetry between formats and behaviours: confirmed (Table 2). The mechanism — gradient-level interference between category batches — is unmeasured; the correlation structure in Figure 3b is descriptive only. The hypothesis is therefore a hypothesis: two confirmed predictions, one partially confirmed, mechanism open.

2.2 Recovery asymmetry

A deliberately over-dosed abstention pulse (300 steps, ≈7 epochs over 343 examples) produced a clean damage map. One epoch-equivalent of re-locking then repaired the structural damage while the newly installed behaviour survived:

Table 2. Damage and repair. Formats install deep and leave last; behavioural skills are fragile during installation and durable once super-saturated.
axisbeforeafter over-doseafter re-lock
grounding0.8870.0250.863
premise0.7330.533—
abstention0.6330.5670.833
provenance0.9800.940held

Grounding was erased and restored almost completely while the newly installed abstention behaviour survived. At 1.2B the same recipe held abstention at 1.000 and grounding at 0.975 simultaneously — a combination no 0.6B arm reached. The window widens with scale.

2.3 The per-epoch damage ledger

(a) sub-score damage per epoch0.2-epoch pulse, 0.6B · normalised weights feed the lossabstention2.50d̃ 0.458grounding1.06d̃ 0.194premise1.00d̃ 0.183provenance0.90d̃ 0.165total 5.46 / epoch(b) interference structureSpearman over 8 runs · descriptive, not causalpremise ↔ abstention+0.88grounding ↔ provenance+0.54provenance ↔ overall-0.610negative = the axis moves against overall score
Figure 3. (a) Sub-score damage per epoch, measured on a 0.2-epoch pulse at 0.6B, with the normalised weights the objective uses. (b) Interference structure across eight sequentially selected runs — descriptive, not causal.

2.4 The objective: damage-aware OPD

Inherited from MiniCPM5: specialist teachers, a reverse-KL teacher signal used as a per-token advantage, and distillation prompt reuse. That pipeline has no notion of cross-behaviour interference during consolidation. This program measured exactly that interference; DA-OPD is the synthesis.

The sampled token advantage, unbiased at the behaviour policy:

2026-10-14T10:55:36.638680 image/svg+xml Matplotlib v3.10.8, https://matplotlib.org/ (2)

The consolidation loss:

2026-10-14T10:55:36.689406 image/svg+xml Matplotlib v3.10.8, https://matplotlib.org/ (3)

where the importance ratio is

2026-10-14T10:55:36.735941 image/svg+xml Matplotlib v3.10.8, https://matplotlib.org/ (4)

The first term is the unmodified on-policy distillation objective. The second term is the addition: while a teacher's domain is being consolidated, every protected category pays an anchor-KL penalty to a frozen reference, weighted by how expensive that category is to damage. The reference is the common SFT initialisation, with β = 0.25 as the prior. Setting β = 0 recovers vanilla OPD and is the control arm.

The measured comparison: β = 0.25 anchored beat β = 0 control in 3 of 3 student seeds on overall and every protected axis at equal transfer (0.816 vs 0.791). Premise preservation failed in all six arm-seeds, and the β = 0.5 screen fired STOP per its frozen rule because the β response is non-monotone.

2.5 Dose allocation as a linear program

Teacher routing is solved before any run rather than tuned after it:

2026-10-14T10:55:36.767793 image/svg+xml Matplotlib v3.10.8, https://matplotlib.org/ (5)

where g_c is own-category installation gain per epoch, D_{c→c'} is the expected sub-score change in c' per epoch of category-c exposure, Ŵ_harm,c is the measured harm threshold, and K is the total update budget. Unmeasured rows default to the mean measured damage and are flagged. The output — per-teacher budgets and predicted per-category deltas — is falsifiable against the run's actual deltas.

2.6 Recipes are per-substrate

Three measured points on the same recipe family: at 0.6B the recipe trains behaviours up and MMLU rose 3.7 points; at 1.2B the same recipe preserves the cost but damages MMLU monotonically with dose (42.34 → 40.72); at Qwen3.5-2B the recipe regressed against a strong base across every variant measured (−0.08 overall, −5.22 MMLU). The dilution law is measured, not inferred. Recipe choice is an experimental variable per substrate, not a transferred constant.

3Compression: calibration, not bits

Two 2-bit builds of one model, identical in file size and bit width, scored 0.014 and 0.708. The variable was not how far the model was compressed but what the compressor was told to protect.

3.1 The estimand

The quantisation gap of a lineage at a rung is

2026-10-14T10:55:36.835189 image/svg+xml Matplotlib v3.10.8, https://matplotlib.org/ (6)

measured at identical evaluation, protocol, seed, and decode settings. Matched-quant deltas only: candidate_rung − base_rung is reportable; candidate_rung − base_bf16 is never reported as a delta. Each rung is a frozen estimand with its own lock entry.

(a) dense / looped 3B · 2.6 GBscore by rung; calibrated Q2 matches Q4 at 73% of the size0.00.51.0v3artifact size (GB)Q4 = 0.722Q4_K_MQ2 + imatrix 0.708Q2 naive 0.014IQ1_M 0.069same bits, same size: ≈50× apartthe variable is the calibration corpus(b) MoE 7.9B / 1.3B active2-bit retention where the dense substrate collapsed0.00.51.00.847Q4_K_M0.792IQ2_M0.778Q2_K93% of Q4dense at Q2 / IQ1: 0.014 – 0.069expert redundancy is the quantisation armour
Figure 4. (a) The parity column on one dense/looped substrate. Calibrated Q2 sits within noise of Q4 at 73% of the file size; naive Q2 collapses; IQ1 destroys the polarity capability itself. (b) An MoE retains 92–93% of its Q4 score at 2 bits, where the dense substrate collapsed.

3.2 The 50× swing, and the mechanism

Table 3. One substrate, four rungs, greedy decode, paired controls. The two Q2 builds are identical in size and bit width.
rungsizeengram v3control v3uplift
Q4_K_M2.40 GB0.7220.05613×
Q2_K, imatrix-calibrated1.76 GB0.7080.1116.4×
Q2_K, naive1.76 GB0.0140.000collapsed
IQ1_M, imatrix-calibrated1.27 GB0.0690.0145× on a collapsed base

The mechanism is standard tooling, not an invention here. llama-imatrix runs a calibration corpus through the model and accumulates, per weight, an importance estimate derived from the expected squared activation flowing through it — the diagonal of an empirical Hessian/Fisher-type quantity. llama-quantize --imatrix then allocates bit precision by that importance: weights the calibration data exercises heavily keep resolution, weights it rarely touches are squeezed harder.

The contribution is the calibration corpus choice. The imatrix was built from this program's own corpora. A generic calibration set does not know which weights a given domain depends on. The consequence is practical: if a rung collapses, the first variable to fix is what you calibrated against, not the rung.

3.3 The parity ladder, and the IQ1 verdict

The deployable artifact is a matched pair (rung, table), and the product claim is a curve: composite score stays flat as weights shrink, with the table growing slightly to compensate. Pre-registered gates: at every rung there exists a table size scoring within 0.05 of the top-rung reference, and a larger table never hurts.

IQ1_M, calibrated from our own corpora, was measured on both architecture classes: dense 0.069, MoE 0.097. Both collapsed. The compression destroys the polarity capability itself, and the division of labour in §4 says the table cannot replace the model's reject half. IQ1 + engram parity with an uncompressed base fails on both classes; the ladder floor is calibrated 2-bit.

3.4 MoE quantisation armour

A 7.9B/A1.3B mixture-of-experts held 92–93% of its Q4 score at 2 bits, where the dense looped substrate measured 0.014–0.069. Expert redundancy functions as quantisation armour. This is one measured cell on one instrument, not a general claim about MoE architectures.

3.5 Tables are quantisation-immune

On one trained 1.2B substrate the same fact table scored 0.767 at F16 and 0.767 at Q4_K_M — bit-for-bit identical — and retained 70% of its uplift at Q2_K (0.533, against a 0.383 floor) at one fifth the file size. Facts in a table survive compression; facts in the weights do not.

Published numbers are not admissible references

A model advertised at ~84–85 MMLU scored 48.2 on this harness. The gap is protocol, not model: 0-shot letter-loglikelihood here against 5-shot generative on the full set, an offset of roughly 36 points that cannot be modelled away. Vendor benchmark numbers are inadmissible as base references on this harness; base-only runs of our own are the references, and a generation-based public bench is the cleaner external anchor.

4The engram: division of labour

An engram here is a static, runtime-editable fact table — a few hundred to a few thousand rows, each with source provenance — whose retrieved hits are injected into the prompt. No architecture change, no training. The task splits cleanly into a half only the model can supply and a half a table supplies better than training can.

4.1 The decomposition

Fine-grained grading separates three outcomes on reject-polarity items: corrected (rejected the premise and stated the true fact), affirmed (accepted a false premise), and rejected without content (rejected but could not state the fact). All arms share the same six retrieval misses, so the residual decomposes cleanly.

outcome on 60 reject-polarity items, hard benchevery arm shares the same six retrieval missesQwen3-0.6B dense750polarityLFM2.5-1.2B hybrid28626polarityQwen3.5-2B dense4612contentNanbeige 3B looped43116contentcorrectedrejected, no contentaffirmed a false premise
Figure 5. Outcome decomposition on 60 reject-polarity items. The failure mode is not one thing: below roughly 2B, models affirm false premises even when the true fact is supplied, and no amount of additional facts repairs that.

Polarity is the model's job. Accept or reject. At 0.6B, 50 of 60 reject items failed this way. Below roughly 2B the model affirms a false premise even when handed the true fact — a judgement limit, not a knowledge limit.

Content is the table's job. What the true fact is. Supply it and content failures nearly vanish; at 1.2B the model restates an injected fact 89% of the time when it rejects.

4.2 Uplift, and why its shape matters

(a) paired uplift across the model ladderengram ÷ paired control, hard bench3.7×0.6B17×1.2B7.1×2B13×loop5.1×Ling4.7×8B×51015input model sizepeaks mid-ladder, then declines(b) engram-size scaling by architecture classhard bench, engram condition0.40.60.83101K3Kfacts in the table8B-A1BLing2B denseloop 3Bv3
Figure 6. (a) Paired uplift across the model ladder peaks where a model has enough judgement to use a fact and not enough knowledge to already contain it, then declines as the control floor rises. (b) Engram-size scaling separates by architecture class: both MoEs saturate near 1,000 facts while the dense 2B is still rising and the 0.6B is flat.

Uplift is defined as the ratio of the engram condition to its paired control. The first true paired table in the program's history: 3.7× at 0.6B, 17× at 1.2B, 7.1× at 2B, 13× on the looped substrate at Q4, 5.1× and 4.7× on the two MoEs.

Uplift is non-monotone. It peaks mid-ladder and declines at the top as the control floor rises. The declining tail is the first measured support for the prediction that a substrate carrying knowledge natively has less headroom.

A related result: a gate that decides whether to supply the fact was falsified on both scales. Always-inject beats gated-inject, because injected facts help true-premise items too, and withholding costs more than the gate's reject decision adds.

4.3 Saturation arrives near a thousand facts

Growing a table from 310 to 3,000 facts bought +0.02 to +0.04 — a real gain, not a step change. Gate reads: within-class consistency passed (both MoEs trend identically), between-class difference passed (MoE saturates at 1,000, dense-2B still rising, 0.6B flat), and the capacity signature is supported but shallow. Anti-cheat guard: table growth uses generator-grown, provenance-recorded facts only, never bench-derived; golds stay frozen and hit@1 is re-measured at every size.

4.4 Table quality beats table volume

Twenty items were authored from the frozen table's corpus facts — its actual distribution, disjoint from the bench's end-user topics — and committed before any retrieval probing at all.

(a) blind holdout: the first table was overfittedoffline probe · both tables include the holdout gold rows0.51.00.880.98benchhit@10.550.85holdouthit@1frozen (28,425)challenger (2,445)(b) volume against performance2,445 facts is 8.6% of 28,405hand-curated · 28,405 factshit@1 0.55mechanical hygiene · 2,445 factshit@1 0.85≈ 8.6% of the volume+0.30 holdout hit@1+0.40 holdout v3every residual miss traced to same-topic near-duplicates
Figure 7. The blind holdout exposed the first table as overfitted to its bench. Offline retrieval probe; both tables include the holdout gold rows, so the comparison is like-for-like. A mechanically filtered table at 8.6% of the volume outperformed it on both benches.
Table 4. Retrieval quality, offline probe. Both tables include the twenty holdout gold rows, so the comparison is like-for-like; hit@1 / hit@3.
tablebenchholdout
frozen, hand-curated (28,425 rows)0.878 / 0.9590.550 / 0.750
challenger, mechanical (2,445 rows)0.980 / 1.0000.850 / 0.900

Without the holdout rows merged, the frozen table's holdout retrieval collapsed further — hit@1 0.30, v3 0.50 — so the probe above flatters it. Every residual miss on the large table traced to same-topic near-duplicates that the mechanical hygiene pass never admits. Volume was the disease.

Final gates on the challenger, single 8B-A1B, pool 50, top-k 1, no keyword tiebreak: bench 0.959 at the strict stage-1 grader (0.980 on grader v2), blind holdout 0.900 (18/20, on-hit conversion 17/17). The 0.9 gate passes on a single model, on both the original bench and the blind holdout.

4.5 Retrieval geometry

retrieval hit@1 at 18K factsthree-leg retrieval, measured cumulativelykeyword overlap0.490+ bge-small embeddings0.755+0.265+ cross-encoder re-rank0.898+0.143Embeddings fix conversational collisions; exact-token re-ranking fixes the numeral-differingdistractors embeddings cannot separate. A hybrid, not a swap.
Figure 8. The retrieval ladder at 18K facts. Dense embeddings fix the conversational-collision problem that kills keyword search above roughly a thousand facts; exact-token re-ranking fixes the numeral-differing distractors embeddings cannot separate.

Conflict-aware distillation is the named next lever: two facts, same topic, different numbers — keep the document-pinned one.

4.6 Cross-vertical transfer

The formula was run on three verticals, reported on one basis (stage-1 / grader v2): M365 0.959 / 0.980, SQL Server 0.878 / 0.878, PowerShell 0.781 / 0.829. On PowerShell the model leg transferred unchanged — on-hit conversion 0.96–1.00, replicating the M365 result including on affirm items — while the retrieval leg was bound by table quality (0.585 hit@1 against M365's 0.898). The gap on a new vertical is a table-quality problem, not a method problem.

5Interface: where the knowledge enters

Giving the model a retrieval tool made it worse than retrieving before inference — at both scales measured, through three separable failure modes.

1.000pre-injectionon-hit conversion1 · initiationdoes the model ask?0.3678B, unprompted2 · query qualitydoes the query find it?0.490keyword hit@13 · round tripdoes it convert?0.722on-call conversionThree leaks, measured separately and compounding. Pre-injection risks none of them.At 350M the constraint is stage 3, not stage 1: the tool is called on 96–98% of items and themodel still affirms the false premise when handed the correct fact.
Figure 9. The three leaks. Pre-injection risks none of them: by the time the model sees the question, the fact is already in context.
Table 5. Same questions, same grader, same model — all four arms on one basis.
armtool-call rateon-call conversionv3, 8Bv3, 350M
pre-injectionn/a1.000 on-hit0.9390.327
tool available, model chooses36.7%0.7220.5100.265
tool call, model writes the query98.0%0.6250.6330.061

The three leaks are independent and they compound. Initiation: with the tool merely available, the 8B calls it on barely a third of items and answers blind the rest of the way. Query quality: with explicit framing the call rate reaches 98%, but the model's keyword queries hit the right fact only ~49% of the time. Round-trip conversion: even when the perfect fact is returned, conversion through the tool result is 0.722 against 1.000 for pre-injection.

The product reading

An MCP surface does not make a small model competent. At 350M the tool is called on 96–98% of items and conversion is still 0.27 with the perfect fact handed back — the misses are affirmed. The binding constraint at that scale is conversion, not access. For a bounded product scope, pre-injection is strictly better; tool-calling remains interesting only for open-ended retrieval the engram cannot anticipate.

The arithmetic wall

One-shot multi-row spreadsheet aggregation failed at every scale measured, including 1.2B with harness arithmetic supplied — asserting 102,000 against 15,834.36. Scale bought document quality, not the composition skill. The product answer is a deterministic harness that evaluates formulas against a harvested cell grid and prints exact totals regardless of model state. The measured boundary in the trained 350M: three rows 1.000, seven rows 0.167.

6The artifact

The deployable object is not a model. It is a triple: a table carrying the facts with per-row provenance, editable and versioned without retraining and bit-identical at every rung; a substrate carrying the judgement — accept, reject, abstain, cite — large enough for the polarity half; and a rung, a measured choice with a measured cliff, printed on the card next to the win.

Config rules are per-vertical because retrieval geometry is: topic-diverse corpora want a wide candidate pool with top-1 and no tiebreak; narrow corpora want a narrow pool with top-3, and measured worse at the wider setting. The optimisation question changes accordingly — not how small can the model be, but which half of the problem am I fixing.

7At scale, and where to go next

The measurements above were taken at 0.3B–8B on one 6 GB GPU. This section separates what they predict at scale from what remains open, and names the experiments the hypothesis most needs. Everything here is intended as open-source knowledge: the harness is released so each item can be run, checked, or falsified by someone else.

7.1 What the dose window predicts for large-model practice

If windows widen with scale — and P1 is confirmed at only one size pair — two consequences follow for fine-tuning at scale. First, targeted behavioural patching should become relatively cheaper as models grow: a pulse-then-re-lock curriculum sized against a damage ledger, rather than category data mixed into the base mixture. Second, multi-teacher consolidation should weight anchor replay by measured per-category damage — the DA-OPD anchor term, equation (3) — rather than uniformly. Both are extrapolations from the measured interval, not results.

7.2 What the calibration result changes at serving scale

Build the importance matrix from deployment-domain text, not a generic corpus, and ship quantisation rungs as measured pairs with their table. The measured rungs: calibrated 2-bit at parity with Q4 at 73% of the size on one dense substrate, and 92–93% retention at 2 bits on one MoE. If the MoE result holds across the class, 2-bit MoE serving is roughly a further 40% memory reduction at near-parity — the cheapest untested capacity lever in this paper.

7.3 What the division of labour changes about knowledge management

Perishable knowledge belongs in tables, not weights: per-vertical tables of roughly a thousand facts with per-row provenance, refreshed without retraining. The self-populating pipeline — search, distill a cited fact, answer — measured 0.800 against a 0.000 control on post-cutoff questions, at n = 5: a demonstration, not a result. Private enterprise knowledge is the axis on which external tables compose with rather than compete against large n-gram-table architectures: those tables freeze at pretraining; runtime-editable tables with provenance are structurally absent from them.

7.4 An open agenda

The experiments this hypothesis most needs, in the order a small team can run them:

  1. Scale test. The same pulse / re-lock pair at 7B–14B: two arms decide whether W_harm keeps widening.
  2. Mechanism test. Gradient cosine similarity between category batches during the pulse — the causal test the correlation matrix in Figure 3b cannot substitute for.
  3. Public replication. The calibration finding on a generation-based public bench, with the imatrix corpora published.
  4. Conflict-aware distillation. The named residual: two facts, same topic, different numbers — keep the document-pinned one.
  5. Multi-seed the headline cells and report paired intervals; several single-run cells here are point estimates.
  6. Instrument mirrors. Publish public versions of the frozen instruments — fresh items, same generators — so results are reproducible without contaminating the private sets.
Open source

The evaluation harness, corpus builders, retrieval pipeline, and command-line tooling described here are released as open source at github.com/chadstthomas-svg/cowork-cli, together with the frozen-instrument generators. Licenses: code Apache-2.0; catalog sources CC-BY-4.0; NLI grader MIT; training corpus under the Tablinum Dataset License v1.0. Every number recomputes from a committed run record — the intent is that you can check, and falsify.

8Method rules this program adopted

  1. Freeze instruments before training. A published evaluation set becomes a training set.
  2. Run a shortcut check on every new instrument. A trivial baseline above 0.90 means the instrument measures the shortcut.
  3. Pair every condition with a control. An uplift without a baseline is not a result.
  4. Report per-polarity. Reject and affirm are never blended.
  5. Structure-true testing. No pattern crosses an architecture class without its own cell; a cross-structure pattern may reflect the corpus rather than the architecture.
  6. A custom grader is a hypothesis until probed. Grade the grader.
  7. Read the generations, not the exit codes.
  8. Smoke gates check speed, not just completion. A gate that passed at 150 s/step implied a 47-hour run.
  9. Within-server comparisons are robust; absolute values across server restarts are not. Ship the comparison, annotate the absolute.
  10. State the failure mode next to the win.

9What remains unestablished

  • Production-scale quality assurance. Whether a ≥2B substrate with a fixed table clears 0.9 on genuinely real-world questions is predicted, not measured. The deciding cell has not run.
  • Below calibrated 2-bit. The cliff is measured on two architecture classes; whether some class has cheaper redundancy is untested.
  • Domain generality. One successful transfer on the model leg is a data point. The method's behaviour on a domain with different retrieval geometry is unknown.
  • Conflict. The named residual — two facts, same topic, different numbers — has no measured solution. Conflict-aware distillation is a proposal.
  • Cross-lineage anchoring. Same-initialisation self-anchoring is measured; anchoring a student to a different lineage's checkpoint is not.
  • The causal reading of the interference matrix. The correlation structure in Figure 3b is descriptive across eight sequentially selected runs. Gradient-level measurement is the named test and has not been run.