The machine ontology pointer

We keep coming up with the problem of addressing Gout as it builds in the machine, and adressing machine parameters for mappings and installs. Typeface Explosion has a solution, let the $ operator be a link to the machine. Example:

$.maps

is a direct entry into the internal ontology of the machine. Simplifies a bunch of stuff. Getting a previous node of Gout, example: $.Gout is a valid G. $.SQL gets me to the set up of SQL. In the actual implementation, we will make the temporary parameters of the engine a sratch table in SQL. Hence all that same code paths apply. This is like a hue chunks of code gone, maybe 30 lines of code wiped out.

Also, the not property, !, as in !*. Match everything but don't collect. !Nothis, match everything except the keyword Notthis. strings, and don't pass on conditional variable test. And, lets quit using the word sibling and use the word set as a link property, set property and sequential property.

And, in the world of G, all G graphs terinate in a resource. So we have a terminator property that forces match and collect. The terminating resource can be an SQL text blob, or it can be a RDP/IRL/File pointer. In version one, all G must terminate in sqlite3 text BLOBS table stores IDs, in the local database.

I have the lines of code dropping fast and the macro initialization graphs multiplying!