Redirection in the Ontology engine

>! Redirect standard output; overwrite file if it exists

This is standard unix redirect of output, making it run from the process to a file rather than to the screen, for example.  Gout does not always become part of the web, it may be exported. Example:
Gout = convolve(G1,G2) // this is default, all Gs  part of the world of G

But:
convolve(a.b.>! local),initializer) // Gout is directed to some local resource handler


>! is type of termination operator, terminating  string of G3. In the example above, G3 is handled by the local machine, this is how the execution engine performs set up.  I can use the local handler to install SQL scripts and operator mappings.  When I have the code down to 150 lines of executable, I might consider writing it. If I can define everything down to a set of tables, then the main loop is a simple state machine, just a few lines of executable, and manys of lines of defines, which are simple.

I doubt the method for individual operators are no more than ten lines of code.  Keep the variable scoping and sybolic grammar simple.  The main code is writing a local resource handler than can take a G stack and interpret it as set up parameters. The SQL scripts can be tested externally on the sqlite3 console, then just inserted into the engine.  Version one, anyway.  Hopefully better programmers than I would already be improving it.