Output is not an atribute

My method of reducing lines of code is to pass the responsibility down the line, great grammar makes this possible.

All table read or write, there is no reason for apriori restrictions. The default names still hold, but, the machine does prohibit writing to any of the one or more tables involved in a multigraph colvolution.

Match outcomes, when the match routine is written, can request default operations on some links, and default might mean close and update on output, and also on .....Hmmm what is the default table closes and updates? It is now a potentially multi-table, multi-graph, restricted only by inherited logic which works by Hmm... dunno yet?

The thing here is an SQL programmer that gets brave with general selectt and inserts over multiple tables. But our standard rule still hold, all of table trversals within sqlite obey the graph Turing traversal law. They can be treated as associated binary operations on segments. Descend segment until done then do next set element. So there is an implied natural restriction in the grammar of TE. So the clever SQL programmer cannot fool the pinball grammar, except for nested logic. Some of that nested logic will be purposefully perverse, like special debug links, when to run and rerun schema filters, stuff like that.