The literature of digitally displayed characters.
Every Unicode character represents 1/10 of a token —
& the way you compose them reveals more than the words themselves.
Glyphature was born from a simple, astonishing observation: after thirty years of digital communication — from Character Map in Windows 3.1 to the Unicode standard's 150,000+ characters — we are still signing documents with characters from a standard QWERTY keyboard.
Glyphature is the framework that changes that. It is simultaneously a taxonomy of Unicode character relationships, an authentication protocol based on deliberate composition, & a philosophical proposition about the value of every character a human being chooses to deploy.
A shibboleth reveals membership through how something is said — not what it means. Glyphature extends this to Unicode composition: the characters you choose, & where you place them, carry semantic weight invisible to systems that don't know to look for it.
Consider the ellipsis — a fixed-length window of exactly three characters. Introduce an Interrobang — itself a Glyphature character, a ligature of question & exclamation — & observe what position does to meaning. The engine reads all three as categorically different utterances:
A BPE tokenizer flattens all three to approximately the same token sequence. Position within a constrained compositional window is semantic. This is the engine's deepest capability.
Every character in the Glyphature engine carries a documented criterion — the formal basis for its relationship to its QWERTY analog. These criteria determine authenticity scoring. They are not a recipe. They are a taxonomy.
Glyphature is developed under the StOOpid.org sovereign infrastructure — independently operated, no big-tech intermediaries in the chain. Authentication principles established here are designed to integrate across the platform's properties.