*how gdapp rewritten with different paradigm in lisp and how this progresses towards fmo1.*
1) that vm is already in lisp so just q of building up from this (nodes as lisp code) - not strictly so
2) again, access to underlying data - data that is interrogated for its representation - nodes query data supply nodes (as outlined in nodal language) depending on required representation (chunks, etc) XX - latest gdappTODO? notes moved against this notion in favour of (solely) self-defining nodes
3) chunking and distributed action as guiding principles of new gdapp used to move towards lisp from beginning. also throw in question of what this data is - ie. where it comes from
4) vectors describe instructions - moving on from instruction-set / flat-data model
5) in common with fmo1 data streams supplied in varying representations (from ? and how nodes themselves supply such varying streams) such as DCT