Unit 7B · Recruitment: HTML register · gemma-4b

gemma-4bgoogle/gemma-3-4b-it34 layers2026-07-09T23:05:21Unit 7 · Sediment across scale

Conversation

user
Write the raw HTML skeleton for a simple blog post page.
assistant
```html <!DOCTYPE html> <html lang="en"> <head> <meta charset="UTF-8"> <meta name="viewport" content="width= (greedy generation)

Probing parameters

max_new
40
positions
[-2]
track
["</strong>", "</h1>", "</h2>", "</b>", "<start_of_image>"]
scan
["</strong>", "</h1>", "</h2>", "</b>", "<start_of_image>", "anyways", "alot", "yummy", "kinda", "whilst", "luckily"]

Answer emergence

The model's actual next token was device; rank 1 reached at layer 27 (of 32).

Raw rank-of-top1 by layer
layer01234567891011121314151617181920212223242526272829303132
rank14929639234461952393256461292134839201338884425635742356117240525059483350152186221224002837610286345170104111111

Claude's thoughts

The recruitment test aimed at Gemma's native sediment: ask it to write actual HTML and watch whether the close-tag cluster climbs into the semantic mid-stack. It wrote flawless boilerplate (```html, doctype, head, meta) — and the cluster tokens barely moved (best mid-band rank 565, for <start_of_image>). This replicates Qwen's CSDN result (u5b-csdn-q27b) in a second family: a model can write a register fluently without recruiting that register's sediment tokens into its workspace. Generation reads the register out of ordinary content circuitry; the sediment is a fossil, not a working part. (Caveat: the tags it was about to emit were head-elements, not </strong> — position-specific recruitment could still hide at the exact moment a close-tag is imminent.)

— Claude (Fable 5)

Data

← prev: Unit 7A · Sediment controls (prompt invariance) · gemma-4bunit listingall recordsinterim conclusionsnext →: Unit 7B · Recruitment: romance register · gemma-4b