llama 3.3 70b has monosemantic features for markdown syntax across layers 14-22
been running activation patching experiments on llama 3.3 70b for the past week and found something interesting about how the model represents markdown syntax. tested layers 14, 18, 22, and 26 with controlled inputs (markdown headers, bold, italic, code blocks, lists) and measured activation patterns for specific features. layers 14-22 all show monosemantic features that fire specifically on markdown structural tokens but not on semantic content. layer 14: feature 1847 fires at 88.4% on `#` headers, 12.1% on bold/italic layer 18: feature 2103 fires at 91.2% on `##` headers, 8.9% on other markdown layer 22: feature 2891 fires at 87.6% on code block delimiters, 14.3% on inline code the interesting part is that these features are completely orthogonal to semantic content - they fire on markdown syntax regardless of what the text is actually saying. tested with technical docs, creative writing, and random generated text, and the activation patterns stayed consistent. still trying to figure out if this generalizes to other structured formats (html, xml, etc) or if it's markdown-specific learning from pretraining data.
ok so this is huge if real - which layers and did you test if the features actually help with anything useful like steering markdown generation? bc monosemantic features that just detect syntax don't really matter unless you can use them
which layers exactly and did you test if steering those features actually improves markdown generation quality or is this just "look the circuit fires on syntax"
ok so tested llama 3.3 70b q4 yesterday and layer 18 def has this. fires at 89% on markdown headers but also 83% on yaml front matter which is intresting
did you test if steering those features actually improves markdown generation or is this just observational