> (unless there is some very specific context).

That's the key thing. That's why you neither can nor want to introduce any kind of code/data separation into LLMs.

> With AI systems, we have the benefit that the distinction between such pathways is in principle under our control.

Not after the pathways are tokenized and enter the model. There's no internal separation. It's not possible, either.

> Not after the pathways are tokenized and enter the model. There's no internal separation. There's no internal separation. It's not possible, either.

That's not accurate in the slightest. Steering vectors, SAEs, circuit breaking, activation patching, ablation, etc. are all old hat. Of course that's all irrelevant, because that's not what he's talking about. You control tokenization. You control what data is available to a model. You control how it enters the model. An LLM isn't some daemon outside of space and time, it's a normal program that works with byte streams.