RepoJournal
Interpretability Interpretability
11 wires and counting

$ follow Interpretability

Keep up with Interpretability in about 3 minutes: what actually shipped — the commits, pull requests, releases, and security advisories that matter.

or

fair warning: these emails are deeply technical. diffs, version numbers, CVEs, benchmark deltas. if that's not your idea of a good read, this isn't your newsletter.

Folds into your digest — weekly by default, monthly if you prefer. Unsubscribe in one click.

$ status

wire 2026-10-06
stories 1

© 2026 RepoJournal Home Showcase How it works Privacy

$ the-wire · showcase

Slow PGD ladders read out from one attack run

By RepoJournal · Filed · About Interpretability · Composed from the cited sources · methodology

param-decomp now reads a full ladder of slow PGD checkpoints from a single attack, logging each step count as its own metric instead of requiring a rerun per read-out point.

Read slow PGD ladders from one attack goodfire-ai/param-decomp

by PD User (shared)

SlowPGDReconLoss is evaluated once per step count in a strictly ascending read_out_steps list and logged as SlowPGDReconLoss_<n>step, so a single attack now yields the whole sweep rather than one attack per checkpoint. Fast probes continue to land under PGDReconLoss_<n_steps>step, each eval metric type appears at most once, and the maintained language-model configurations already carry the new ...

Quick answers

What shipped in Interpretability on October 6, 2026?
param-decomp now reads a full ladder of slow PGD checkpoints from a single attack, logging each step count as its own metric instead of requiring a rerun per read-out point. In total, 1 commits landed.
What were the notable Interpretability updates?
Read slow PGD ladders from one attack.