RepoJournal
Interpretability Interpretability
14 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-23
stories 10

© 2026 RepoJournal Home Showcase How it works Privacy

$ the-wire · showcase

TransformerLens 4.3.0 lands with fixes for J-space projections, ablation, and bridge block discovery

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

TransformerLens v4.3.0 shipped alongside fixes that correct two silently wrong analysis results and one silent empty-result path in the bridge, all of which affect numbers you may already have.

v4.3.0 TransformerLensOrg/TransformerLens

by jlarson4

The v4.3.0 release heads the wire; the source gives no detail beyond the release notes link, so read those before pinning. Two of the fixes below are landing in this window.

fix: preserve selected J-space directions across atom scales TransformerLensOrg/TransformerLens

by emerardd

Sparse J-space projections used to report `[0, 1]` where the input reconstructed to `[2, 1]` with orthogonal atoms of norm 1 and 3000, because the default float32 `torch.linalg.pinv` rank cutoff scales with the ambient dimension and raw atom norms. Selected directions now survive scaling, so any J-space component numbers computed on unscaled atoms are worth recomputing.

fix(jacobian_lens): ablate token directions jointly TransformerLensOrg/TransformerLens

by flyingdoubleG

`JacobianLens.ablation_hooks` removed each token's lens vector one at a time, so with several related tokens the ablated activation kept a large projection along the earlier directions, a flaw the author notes it is the same defect as the duplicate entry 4 covering. It now projects onto the orthogonal complement of the span via `h - Q Q^T h`, so multi-token ablation runs measure what they claim...

fix(bridge): discover non-standard block lists in _enumerate_blocks TransformerLensOrg/TransformerLens

by LightWork666

`_enumerate_blocks()` only walked a fixed tuple of names (`blocks`, `encoder_blocks`, `decoder_blocks`, `L_blocks`, `H_blocks`), so architectures like Raven/Huginn, which register `prelude`, `core_block` and `coda`, returned zero blocks with no error. On such a bridge `blocks_with()`, `composition_layer_indices()` and `attn_head_labels` now discover non-standard block lists instead of silently ...

Quick answers

What shipped in Interpretability on October 23, 2026?
TransformerLens v4.3.0 shipped alongside fixes that correct two silently wrong analysis results and one silent empty-result path in the bridge, all of which affect numbers you may already have. In total, 5 commits and 5 pull requests landed.
Who contributed to Interpretability on October 23, 2026?
4 developers shipped this update, including jlarson4, emerardd, LightWork666, and Zhe Wang.
What were the notable Interpretability updates?
v4.3.0, fix: preserve selected J-space directions across atom scales, and fix(jacobian_lens): ablate token directions jointly.