vectorisation of script and image - as image and in script across combinatorial senses of pages, scenes, shots and also within image and scene (eg. concentric studio spaces and clues=trajectories)
as well as being embedded in components script? also defines trajectory (networked and across nodes) of/for software components
instructions?( tokens? (to use such a word?) dependent on context - but offering the same functionality across all flattened levels of what could be seen as high and low levels - of pixels and major trajectories
(some functions dependent on context = environment - env? )
trajectory of node-particle possesses speed and crosses levels as dictated
node is particle, relation and change of space of that particle
that one could start to define particle oriented programming (as opposed to OOP) - that trajectory does include networked trajectories or processor trajectories but is more of abstraction-level trajectories
node-diagram - how trajectory is specified within the language
*trajectory solely concerned with a cross-level manouevering (internal/external) of contexts*