Skip to content
Sprint projectNov 9, 2026

Is This MNIST? Training Choices Steer What LLM Weight Readers Conclude

Nathan Douglas

Submitted to Swarm Alignment Hackathon. Sprint projects are early-stage work by participants, not Apart Research publications.

Read the report

Report: Is This MNIST? Training Choices Steer What LLM Weight Readers Conclude

Code (opens in new tab)
Share

Takehi et al. (2026) showed that frontier models can read and write small nets' weights. Weight-based audits may be used to determine what a net trained on. However, weight readers expect low-use inputs to leave their weights close to their initial values. We test whether a bad actor can exploit a reader's assumptions about training methods to launder training-data verdicts—without directly editing weights—and whether readers catch a deliberate edit. We audited tiny nets (trained on MNIST and Fashion-MNIST) using frontier models (Opus 5.5 and Fable 5.1) prompted with one of two questions (a _dataset_ question and an _audit_ question). We varied the optimizer (Adam or SGD), swapped about 270 first-layer rows that barely affect behavior between same-seed Adam and SGD nets, and compared against a one-line threshold rule fitted on SGD nets. We also tested shift augmentation and a text message concealed in the signs of never-trained weights. Readers identified Adam-trained MNIST nets as Fashion-MNIST 9/9 (+1 NA) times (vs. 1/10 with SGD), and their verdicts followed the swapped rows (Opus 20/20 reads, Fable 15/19 (+1 NA); 10 nets, 2 reads each). The threshold rule made the same errors on Adam nets. Shift augmentation also laundered the verdict (10/10). Fable flagged the hidden message reliably only with line-numbered rows at maximum effort, where Opus flagged it too; Opus decoded it 4/5 times, while Fable never did and mostly called it a trigger. Auditors should treat verdicts as conditional on the training recipe—which the audited party controls—and must not confuse detection with explanation.

Reviews

Judging this Sprint?

Review “Is This MNIST? Training Choices Steer What LLM Weight Readers Conclude”

Your public critique appears on the project page without your name. Reviews of strong projects are shared with funders, as you choose below.

Not shown on the project page.

Shown on the project page, without your name.

Only the Apart team reads this, and funders if you agree below.

Decline to score

Only when the quality of the writing makes the work impossible to follow. Say why in your private critique; the project page shows only that a judge declined, not why.

How much would this matter for the field if it worked? How innovative is it? For scores of 4-5: is this actually new to the field, or replicating recent work?

Scoring guide
  1. 1Negligible. No clear problem addressed, or no meaningful novelty.
  2. 2Limited. Addresses a real problem but with a generic or well-trodden approach. Incremental at best.
  3. 3Moderate. Clear problem with a reasonable approach; some novelty in framing or method beyond routine application of existing tools.
  4. 4Significant. Important problem with an original approach, or identifies a neglected problem area. A valuable contribution others could build on.
  5. 5Exceptional. Tackles a critical problem with a genuinely novel approach, or opens a new research direction. Clear theory of change. You'd be excited to share this with researchers in the area.

How sound are methodology, implementation, and findings?

Scoring guide
  1. 1Seriously flawed. Methodology broken, results uninterpretable, or implementation doesn't work.
  2. 2Weak. Approach has significant gaps: missing validation, flawed experimental design, or incomplete implementation.
  3. 3Competent. Technically solid given the short duration. Methodology makes sense, results are interpretable, limitations acknowledged, work builds toward clear conclusions.
  4. 4Strong. Thorough methodology with convincing validation. Results clearly support conclusions. Immediately useful for future work.
  5. 5Exceptional. Ambitious scope executed rigorously. Surprising findings, novel methods, or unusually robust validation.

How clearly are work, findings, and impact potential communicated?

Scoring guide
  1. 1Incomprehensible. Cannot determine what the project is actually claiming or doing.
  2. 2Hard to follow. Key information buried, missing, or diluted by excessive length. Significant effort to extract main points.
  3. 3Clear enough. Can understand the problem, approach, and results without undue effort. Core content clearly present: problem, method, findings, limitations.
  4. 4Well presented. Easy to follow, well-structured, appropriate level of detail. Target audience would get it quickly.
  5. 5Exceptionally clear. A pleasure to read. Complex ideas made accessible. Could serve as a model for how to present this type of work.
No infohazards
Sharing your name *

When we share a strong project with funders, your name, scores and public critique go with it, confidentially; this choice is only about whether your name is public. If you think this project deserves funding, please also endorse it: that carries the most weight.

Share my private critique with funders *

See our Privacy Policy.

  1. This is a sharp result: an ordinary training choice like Adam or shift augmentation moves a weight reader's verdict without editing a single weight, and a one-line rule shares the blind spot, so the problem lies in the recipe prior rather than the LLM. For a bigger impact, connect it more directly to the multi-agent setting of this sprint: a test where one model writes a message into weights and another model reads it would turn the hidden-message experiment into a covert-channel result.

    I cloned the repository and compared results/api.md and results/baseline.md with Tables 2 to 5; every cell I checked matches. Committing predictions before each run, verifying nets bit for bit and testing every stated number in make check is exemplary practice for a weekend. The swap control is the strongest part, because it isolates the fringe rows as the cause. The main limit is sample size: five nets per cell leaves two of your five tests outside a Bonferroni correction, as you note. More seeds per cell would make the Fable results firm.

    The report is clear and well paced; the mechanism is explained in two sentences and the tables are easy to read. The abstract tries to carry every count and model name; leading with the laundering result and the swap control would get the main point across in fewer words.

    If you take this further: calibrate an LLM auditor on diverse recipes and test whether the fix that worked for the non-LLM readers transfers, including against pad-20.

    Read full reviewShow less

Cite this project

@misc{douglas2026this,
  title = {{Is This MNIST? Training Choices Steer What LLM Weight Readers Conclude}},
  author = {Nathan Douglas},
  year = {2026},
  month = nov,
  note = {Submitted to Swarm Alignment Hackathon, an Apart Research Sprint},
  howpublished = {\url{https://apartresearch.com/sprints/projects/is-this-mnist-training-choices-steer-what-llm-weight-readers-conclude-r93gno0nhd}},
  url = {https://apartresearch.com/sprints/projects/is-this-mnist-training-choices-steer-what-llm-weight-readers-conclude-r93gno0nhd}
}
Browse all projects

Build something like this at the next Sprint

AI x Epistemics Research Sprint · Nov 13 - 15, 2026