notion (bootstrapping) of using core language to describe new functionalities/potentials (rather not a case of functionality but a steering/moving towards)
(so bulk/all of fmo1 written in extendible language (lisp)- extends itself (both writing itself and by user)
question of language/interpretation stream in relation to compression/geometry stream
also command language with access to tools such as vm/nn
relation to object?s
[a situated practice used to coordinate behaviours/actions]
<*functions/notions from script?*
barrier, combine, embed, scene, describe, foregrounding, backgrounding, return (think such a list exists elsewhere?)
- that these do not operate on a block but as trajectory, recombinant, relation and level
- is not about what is there (surrounding) - there for what could be interpreted as instruction
for scene? - intersection, concentric, scene-description, frame
exposure, inside-out node
trajectory - arc, circular, intersection, concentration
trajectorial organisation - categories as levels, contexts - levels of scene, trajectories and node depend on node as level etc.
embed = of material and relation to concentric
material of script. observation and what has been already written, filmed
time-line - happened, happening, will happen
so not really a list of functions - language not as functional - language as relational - functions as groupings or grammatical overlap of theoretical lisp language with our script - (note applies to start on textual fm01 but applies perhaps to all versions)
language defines relations and trajectories of node and language operations dictated by such relations - which can always be turned inside out