@jhull I think I have it.
My version of the illustration is attempting to show the funneling down from a class to the 64 element matrix, and to show which tools match up with which state of the story mind process. The spread out bottom gives the effect of the spread out matrix. So my illustratiion is by necessity hybrid.
Posit: there is the functioning of the software
- you define some story points.
- those are fed to algorithms and matched with data defining arrangements of predefined elements, variations etc.
- Several important items are generated:
- a temporal progression
- a 'processing' PSR report
- a static structure indicating story end point
so my illustration about is best thought of as a hybrid view of the working of the software and a gesture at the presence of the dynamic story mind, so we can show process and which software tools to use on which parts.
but when I thought about Chris's point this is a highly artificial and paideutic construction. It's useful for teaching about the tools and giving a flavor of the dynamic, but the MATRIX ITSELF has to be understood correctly as the impression left on the audience mind after it has experienced the whole story. THE WHOLE EXPERIENCE which is why it's presented as a flat set in equlibrium and at rest, it has 'settled' into the mind of the audience.
The Matrix elements, character interactions, in truth are sent through the Story Mind, compared and appreciated, temporally, so that big 3d matrix we see in the books buries the temporal nature of those elements, or to put it another way, requires the Observer to move through them when presented in that fashion.
Chris's model above is closer, I get what he's saying, the hero's choices are constricted and the elements that appear in the matrix in fact also flow down that spiral in time as character interaction illustrations and also have collocation forces working on them.
If I understand this correctly.
Let me think about that. Hmm.
- I missed adding the character quads as a product of the algorithmic run, I'll have to fix that.
and the matrix is 3d although perhaps having a 4th 'positional/temporal/ordinal/' dimension in the arrays of the software program