BIIC: Replacing Tokens with Geometric Algebra Multivectors — Early Results

this is an observation i made personally when i started useing LLM APIs. an inherant flaw in flat token strings is that it has to be sent as a complete string to the processing data center. if any part is lost it has to be resent. one my be forgiven for believing that they are tokens and therefor microscopic, so whats the big deal? the big deal is that in API useage you are charged for token usage. and each time a token string is recent you are not only charged for that, it increases the size of the token string, because the entire conversation is sent each time. so basically the conversation doubles in size on each failed send. in a 4 turn conversation with staggered ammounts of resends, the token count ballons astronomically, and this is not mitigated in anyway over the course of the conversation. why do i say all this, well, your solution offeres something else, the ability for approaching the concept of batch sends. or packet transfer. a flat token string cannot be batched as far as i know. but this remains a massive issue in AI Remote Compute if one is paying for service.