There I was attempting to string together the context that was being provided through those posts along with the synopsis. That was more or less an experiment in attempting to be an "objective" viewer of the "subjective" experiences presented by the readers. I felt it was fair in that context because far more information about the plot/story is given within an analysis thread. Of course, it did not take much until I felt there was a point where I could no longer add to the discussion without having the full context, which is why I did start reading the book.
For the argument I made in this thread, it was meant to be taken at a much more limited, scene-level scope. As that appeared to me to be what the thread was about: How to use an analysis at the scene level to support choices for a greater context.
I'm not denying that. That's the exact reason that I said "plus some of the flow" in my earlier post. Some order, some flow, is baked into the model. The way that I read the original question was whether it makes sense to attempt to suss out the flow during the experience versus trying to determine the flow based on the overall context. The whole context, is of course, needed at such fine-grained levels, which is again, why it came to a point that I felt I could no longer contribute to the discussion in the other thread.
For clarity, the above two paragraphs meant that I saw the question thus: How should a scene-level analysis be used to support the choices of a greater context, and should that be done using the experiential flow of the scene, or with the whole context of the story in which the scene is in?
Perhaps that was too limiting, considering the scope of the discussion, though.
Isn't this another way to say, "Once you have seen the whole movie or have read the whole book"? In other words, have access to the whole Storyform, even if not consciously?
You can when it's baked in. This made me think of concurrency and parallelism in software. Those are, in effect, simultaneous views of the system running all at once, especially on a multi-core processor. In order for a system designed in that way to run, in any way that makes sense, there must be order baked into the running state. Which elements should be taken care of first? Which elements and states are more or less independent from one another? Which elements need to be synchronized, and when? Without baking in that order, such a system isn't possible.
Of course, that's an extremely linear-based way of thinking, but it has holistic elements, as the system must be viewed and balanced as a whole to get any workable design.
I'd like to respond to this, too, but I don't feel like anything but a real-time discussion would be conducive to my thoughts on this one, unfortunately.
And, just because it's such a good question: I wish to ask the same thing that @mlucas did.