I'm saying that you can write it that way AND have no loss of functionality or infact any apparent change from the perspective of the user. Take a chat bot and

I'm saying that you can write it that way AND have no loss of functionality or infact any apparent change from the perspective of the user. Take a chat bot and have it output characters one at a time. That's all I'm claiming, nothing about how the chatbot decides what to output. But that suffices to show that a process which is choosing from a very constrained set of options is still in a different class of success than AlphaGo. The options chosen at each step are more constrained than the choice of moves in Go, so the argument "the difference between solving go and solving tech support is the number of options available at any time" is insufficient. One might be able to define a better notion than branching factor that takes into account how many steps are needed as well as how much it branches in each step and such a thing is probably much larger for tech support than it is for go. But such an argument would be hard to state well, I think.