Vsiink share, attempt, request for commentsish

I feel like I was starting on the wrong foot wrt target demographic here...also not being clear that any of my ideas revolving around this concept I've designated public domain, and not after self promotion or disrespecting the unicode gods. I genuinely want to contribute to opensource without kowtowing to the Microsoft:Github ::linix:git cultural expectation/paradigm, which honestly, is played out and unimpressive. This (vsiink) in addition with tag Unicode block, plus standard zero width chars, plus regular ol 7 bit ascii/utf8, I think is ripe for picking at solution to the modern serde clusterfuck and GPU friendly textdoc LLM inference runtime applications, among other pipedreams. (think, Unicode VMs and text doc LLM human readable latent spaces in universal data interchange formats [sic, gross words]) Initial presentation is deliberately sparse and weak (trash by my standard). Alas, I am bandwidth limited. Also, if you are security minded but not yet variation selector savvy, it is only a matter of time before this codepoint block combo is aggressively utilized in all conceivable contexts by the obvious players. It's only a threat if the vector blindsides ops; there is zero reason for this (vsiink) to ever become a threat, so please wakeup quick. (Sorry to spoil your silly little gem on the clearweb @hackers, @stenographers, @etal.) The very worst thing that could happen is Unicode Consortium determines that the variation selector and tag blocks are too dangerous to support anylonger. THIS MUST NOT HAPPEN. *Please forward this to any unicode / HPC / technologist / IET people with best interests in mind on the topic of Humanity and the future of compute. Enjoy.