Pics Start Date:
Notes Date (end):
TREES / TREES / TREES
There are a bunch of things we've covered since our last core dump... Lots of C development of low-level CEPTR protocols has been happening... structures of nouns and instances, scapes and listeners, logs and "conversations."
But we never built the low-level tree structure which has been hampering progress of building some other "elements" like Lists & Streams (which are actually trees of Patterns/Arrays/Lists/Streams).
As we began to see the tree like structure necessary for our "conversation" logs, we revisited the trees topic and it has leaped into centrality in a whole new and important way.
Running an instance of a code tree happens like this:
We can think of the data engine as waking on a log trigger, matching an appropriate code tree onto a conversation to "process" it. As it runs it prunes itself away until there is only the output which is reintegrated into the data engine..
This feels like a very organic "breath-like" process of expanding and contracting and if it doesn't have the right code-tree to run through the code-reducer... it can go look it up and add it to its repertoire. Receptive capacity.
Trees, Code Trees, Noun Trees, Spec Trees, Tries, Conversations, Logs,
view (naked) not supported for CD_032+pics