This is how your carrier talks to the Key Maker. Simple JSON: like a shopping list. "Order one key please!" "Make it now!" "Cancel that!" "How's it going?" Think of it like email between business partners: polite, structured, to the point.
The Assistant uses this to talk to the Key Maker over the internet. It carries sealed envelopes the Assistant can't read. "Here's my challenge: who are you?" "Here's proof of who I am." "Send me the package!" Like a diplomatic courier with locked pouches.
The most special language! Key Maker speaks directly to your Vault chip through an encrypted tunnel. Every message is encrypted (can't be read), signed (can't be faked), and chained (can't be reordered). Even if the Assistant is hacked: zero readable data.
The Assistant talks directly to the Vault inside your phone using tiny command packets called APDUs. ES10a asks "what's your name?", ES10b handles downloads, and ES10c manages profiles: switching, deleting, renaming. Eleven different commands for the download dance!
Every single message carries a functionCallIdentifier: a unique ticket number. If a message gets lost, resend with the same ticket. The receiver says "already handled #1234!": no double-charging. Brilliant!
ES8+ encrypted messages travel through your Assistant app: but the app literally cannot read them. The encryption is end-to-end between the Key Maker and your Vault chip. Even if a villain hacked the Assistant, they'd see nothing but digital gibberish!