Segment manager

Consent keeps a binary tree of reserved and unreserved segments on the args hap. The binary tree has less and more links, and a ptr and size;  It starts with one node representing the entire heap, unreserved tag set. Then we an see what happens he we get NewSeg and DelSeg, consent traverses the tree, merging nodes and splitting them.

A segment goes from free segment  to pending to confirmed. It keep a confirmation count as each of the other networks consent snippets report back. Simple stuff, not many lines in this code, and make it the front end symbol tables, callers can tag their segments with plain text. Consent is not a thread, it isdriven by other threds that need message and segment service.

But I took the tree out for testing on its own, and I am banging it with del, new, and watching it merge and split, mostly with errors at the moment. An easy debug, and a mutex, then fill in the methods for inter node messages, gain using the same front end table for plain text tags between consent nodes.  High speed enterprise wide  multi processing.

Consent as a generic template

Reserve anything, really.  The thing being reserved is immaterial as long as all the consenting nodes can  insure their own liability against it, they have o know what it is relative to any other thing they deal with.  So, reserve this action, with these parameters.  Consent can tag the action by ID, as long as the other node have the equivalent look up, they are all on the enterprise semantic grmmar.

Reserve the company cash flow for an update.  OK, the data manager has tagged a set of company resources as reservable, any syntax engine has to know about that, consent itself doesn't hve to know the methods or effects of the thing reserved. The data manager has to get name spaces right, to avoid conflicts here. Ultimately, name space is a console function, it is the thing that huts for command executables. Keep that in the back of our heads.