Wednesday, May 17, 2017

Let's do the sandbox equivalent of the car industry

Get a feel for pricing.
Treat this as a use case.  Otto, the Automobile Automatic Banker offers savings and loans for cars, as long as you clicked the OAAB icon.  How does this work?

Well, autos are midsized, full sized, compacts; and we have trucks, small, large and big, plus a couple of SUV classes. The auto executives tell me this. How did they figure it out?  They have to manufacture and haul these around, so they have to have a container algebra for the industry.

Does Otto the Banker care? No, if your token is valid, drop and S or take an L.  But the bot is going to see liquidity events, and order them by significance, and find the ideal match of savings events to loans events such that uncertainty matches significance. Then the bot will reward you or penalize you according to whether you were an ideal saver  of coin for cars.

The simplicity of this model rests on the tokenization process, and the assumption that endpoints meet sandbox rules for secure element.  The actual distribution of vehicles will be the dual of the trade book at Otto's place.  That condition is optimum congestion, buffers in the trade book do not overflow or underflow more than bit error is allowed.  The price of a vehicle, to the consuming public (cost of current operating vehicle) it the amount of empty space needed in the industry supply chain because you have jitter in your use of the vehicle.  You actually carry around a ton of unused basket, frightened of a measly overflow.

The data science says that Otto the banker generates important, and tradable, information whenever Otto asynchronously sets charges, especially if Otto raises the ledger fees.  These are the same reports we get from Zillow for real estate reports, or monthly reports on  mortgage reports.  Butvthe report is asynchronous.  There is a difference, I touched on it.  If you are making bets arriving exactly on predictable time, then the cycle price plays a role and the bets are forces to spread out, avoid jamming. If the event is an asynchronous event, especially having an even money place, then price or interest chages play.

See, either way, fair trading pits do congestion management. In both cases the fundamental applies, no flow, no quantization. When you start raising the cycle flag because of jamming, then you flow into an expanded window of the past, and you dump the window at the appropriate time. flow. Set  spawn = 1 if this case is desired.

No comments: