Note that humans do come with different types of 'input streams':

Hit my knee in the right spot, and I'll kick my leg, no choice about it. Scream at me to LIFT MY EFFING LEG (in a language I do understand), and I may or may not do so. Write the same thing on a piece of paper, and I generally won't (unless there is some very specific context).

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

▲

TeMPOraL 3 hours ago | parent | next [-]

> (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.

▲

ux266478 2 hours ago | parent [-]

> 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.

	▲	TeMPOraL 2 hours ago \| parent [-]
		You control tokenization. But the system able to tell you what those tokens means is the very one you're feeding the tokens to.

▲

ben_w 3 hours ago | parent | prev [-]

While true, insufficient.

Demonstrations of failure: every cult, all propaganda, indoctrination (both military and dictatorial), authority bias, Asch conformity experiments, and the fraction of the population more susceptible to hypnosis.