Worked examples — Circuits and superposition
This is the hands-on companion to the parent topic. There we built the ideas: a circuit is a task-relevant path through the network, and superposition is packing more features than dimensions by using nearly-orthogonal directions. Here we grind through every kind of numeric situation the topic can throw at you.
Before we start, three plain-words reminders (nothing new is assumed):
The single decoding move we repeat everywhere is: to read off "how much of feature is present" in a mixed activation , compute . Why this and not something fancier? Because the dot product is the projection — it asks exactly the question "how far does reach along the direction?", and that is the definition of "how present is feature ".
The scenario matrix
Every numeric question in this topic is one of these cells. The worked examples below are each tagged with the cell(s) they cover.
| Cell | What makes it distinct | Covered by |
|---|---|---|
| A. Orthogonal store | Overlap exactly , decode is perfect | Ex 1 |
| B. Single non-orthogonal feature | One feature active, small self-clean read | Ex 2 |
| C. Two features interfere (same sign) | Overlaps add → over-read | Ex 3 |
| D. Two features interfere (opposite sign) | Overlaps cancel → under-read / miss | Ex 4 |
| E. Zero / degenerate input | No features active, or two identical directions | Ex 5 |
| F. Sparsity capacity (formula) | Plug into | Ex 6 |
| G. Geometric ceiling (formula) | Plug into | Ex 7 |
| H. Polysemantic neuron read | One neuron, many features summed on its axis | Ex 8 |
| I. Real-world word problem | Circuit / feature reasoning in a sentence | Ex 9 |
| J. Exam twist | Sign trap — "the projection lies to you" | Ex 10 |
Ex 1 — Cell A: the orthogonal baseline
Forecast: guess before reading — will the decode be exactly right, or contaminated? (Answer: exactly right.)
- Write the activation. . Why this step? The activation is always the weighted sum of feature arrows; that is the model's actual internal state.
- Decode feature 1: . Why this step? Projection onto answers "how much feature 1?".
- Decode feature 2: .
Verify: overlap (perpendicular), so no cross-talk term exists. Read and match the true strengths exactly. This is the wasteful case: dimensions hold only features. See 2.1.02-ReLU-and-activation-functions for why nonlinearity later lets us clean up the non-orthogonal cases.
Ex 2 — Cell B: one non-orthogonal feature, self-read
Forecast: guess — is equal to , or something less?

- Activation: . Neuron 1 reads , neuron 2 reads (red arrow in figure). Why this step? Even one feature spreads its strength across both neurons — this is already superposition-flavoured storage.
- Self-decode: . Why this step? A unit vector dotted with itself is its squared length ; that guarantees a clean self-read when nothing else is active.
Verify: . A lone feature on a unit vector always decodes to its true strength — interference only appears when a second feature joins.
Ex 3 — Cell C: two features, same-sign interference (over-read)
Forecast: true strength of feature 2 is . Will the projection read exactly , more, or less?

- Sum the activation: . Why this step? When two features fire together the model only sees their sum — a single arrow pointing straight up (plum arrow in figure).
- Compute the overlap . Why this step? The overlap is the leak coefficient — it tells us how much feature 3 contaminates feature 2's read.
- Decode feature 2: . Why this step? Projection onto ; but now contains feature 3 too.
Verify (split the read): . We expected but got : the positive overlap added noise. This is the parent note's cliff-hanger resolved — the interference is exactly the overlap .
Ex 4 — Cell D: opposite-sign interference (under-read / miss)
Forecast: overlap of these two is negative. Will feature 2 read above or below its true ?
- Overlap: . Why this step? Negative overlap means the two arrows point somewhat opposite — feature 5 will subtract from feature 2's read.
- Activation: .
- Decode: . Why this step? Split it: .
Verify: true strength , read — an under-read. Same magnitude of interference as Ex 3, opposite direction, because the sign of the overlap flipped. Together Ex 3 and Ex 4 show why interference is modelled as a random-sign walk in the parent's formula: sometimes it adds, sometimes it cancels.
Ex 5 — Cell E: zero and degenerate inputs
Forecast: in (b), can the network ever tell feature apart from feature ?
- (a) Zero input decode: . Why this step? If nothing fires there is nothing to read — the decode must return , our sanity floor.
- (b) Sum degenerate features: .
- (b) Decode feature : . Why this step? Overlap (identical arrows) — the maximum possible interference.
Verify: In (b), decoding and decoding both give ; there is no way to separate them because their overlap is , not . This is why superposition needs near-orthogonal ( small), not just "many" directions. Overlap is the failure limit; overlap (Ex 1) is the perfect limit; everything real lives between. Sparse-autoencoder methods (4.2.03-Sparse-autoencoders) exist precisely to unfold the in-between cases back toward Ex 1.
Ex 6 — Cell F: sparsity capacity formula
Forecast: guess an order of magnitude — hundreds? thousands?
- Square the SNR: . Why this step? Interference accumulates as , so keeping it below the signal squares the SNR — the parent derived this.
- Square the overlap: . Why this step? Same random-walk reason: overlap enters squared.
- Divide: .
Verify: — heavy usable superposition, entirely because is tiny. Set (dense) and ; the capacity collapses toward , exactly as the parent warned. Sparsity, not dimension count, is the lever.
Ex 7 — Cell G: the geometric ceiling formula
Forecast: bigger or smaller than the from Ex 6?
- Exponent: . Why this step? The geometric bound counts how many near-orthogonal arrows fit, ignoring whether we can decode them.
- Exponentiate: .
Verify: Here the numbers are chosen so the geometric ceiling (, tiny because is small) is below the decodability count — a reminder these are two separate bounds and the smaller one binds. Increase to : exponent , , and geometry stops being the bottleneck. The lesson: geometry grows exponentially in , sparsity-decodability grows linearly in — for realistic large , decodability (sparsity) binds first.
Ex 8 — Cell H: reading a polysemantic neuron
Forecast: the neuron is a mush of features — will it be positive?
- Sum active contributions on the axis: . Why this step? By the parent's formula , a neuron's value is the sum of every active feature's component along its axis.
- Interpret: a reading of came from two unrelated features (3 and 42), not one. Why this step? This is the mechanism of polysemanticity — see it firing tells you something is active, not what.
Verify: turn feature 17 on too: — a different value from a different mix. The single scalar can never be inverted to a unique feature set. This is why 6.3.01-Feature-visualization on a raw polysemantic neuron shows a jumble of unrelated images.
Ex 9 — Cell I: real-world word problem (induction circuit)
Forecast: does ablation prove the head causes the behaviour, or merely correlates?
- Trace the circuit. Previous-token head tags the second "Mary" with "what came before me". Induction head at layer 7 reads that tag, searches history for the earlier "Mary", and copies the token that followed it ("John"). Why this step? Ordering matters — the reader (layer 7) must run after the writer (layer 2), which is why they sit in different layers.
- Compute the drop: percentage points. Why this step? The size of the drop measures how much of the behaviour flowed through this head.
- Interpret causality. A near-total collapse under ablation means the head is causal, not incidental.
Verify: . A -point drop from removing one head is the causal fingerprint the parent demanded. Contrast: ablating an unrelated head would leave accuracy near . This mirrors 6.3.05-Attention-head-interpretability, where the same ablate-and-measure test isolates head function.
Ex 10 — Cell J: the exam twist (the projection lies)
Forecast: feature 1 is genuinely absent. Will its decoded value be near , or dangerously large?
- Confirm is unit length: . Good. Why this step? A fair overlap comparison needs unit vectors.
- Activation (only feature 2 on): .
- Decode feature 1: . Why this step? Projection onto — the standard decode.
Verify: feature 1 is OFF, yet its decoded read is — almost a full "present" signal! The culprit is the huge overlap between the two directions. This is the exam trap: a big projection does not prove a feature is present when directions are not near-orthogonal. It is the numeric reason superposition requires small, and the motivation for 6.3.08-Concept-activation-vectors and sparse dictionaries to define cleaner directions.
Recall Self-test
When two active features have overlap , the decoded value of one is its true strength plus what? ::: Plus times the other feature's strength (same-sign adds, opposite-sign subtracts). Which quantity — geometry () or sparsity () — usually binds capacity in practice? ::: Sparsity (the decodability bound); the geometric ceiling is far larger for realistic . A neuron reads . Does that mean no feature is active? ::: No — active features with opposite-sign components on that axis can cancel to (see the degenerate/cancellation cases).