Consent and sql_lite

They both be on the bus.  The data manager can define shared and locked table pointers on some shared portion of args.  So, any of a number of independent entities can get an agreement to lock up the args list pointer to a specific table. The inter node messaging then delivers the  update to that table across multiple versions of sql_lite, simple enough an a great relief to data managers everywhere.  Accounts updated near simultaneous, just like block chain, because the memory tree, accounts, even sql, are all nested directed graphs.  Access to the generic directed graph is consistently queued at the nodes.  In essence, sql queue requests for a table while block chain queues them for an account. Graphs can b nested, and thus the reservations.  But we are talking queue management, consistent across nodes is equivalent to multiple access coordination;p mathematically related concepts, used everywhere; especially in simple snippets on the bus.