Make encrypted inputs ready for verification.

Compact JSON for the source sample has fifty-one UTF-8 bytes. AES-GCM adds a sixteen-byte authentication tag, producing sixty-seven encrypted bytes. At five pixels per byte the bars combine two hundred fifty-five input pixels with eighty tag pixels into three hundred thirty-five pixels. The exported ciphertext is base64url text, ninety characters for this sample. This creates a local encrypted envelope; it does not compute whether the sample amount exceeds a threshold or submit an input to a chain. The source generates a twelve-byte initialization vector and a sixteen-byte salt. SHA-256 produces a thirty-two-byte digest, displayed as sixty-four hexadecimal characters. At eight pixels per byte the bars are ninety-six, one hundred twenty-eight and two hundred fifty-six pixels long. The commitment hashes the base64url ciphertext text, not the decoded encrypted bytes. A matching hash binds that representation but does not prove a computation result or submission. This is a description of source behavior, not a cryptographic security audit. Encrypt and commit returns one receipt with declared intent, encryption metadata, ciphertext and commitment. Bars compare one local receipt with zero chain submissions at two hundred pixels per count. Copy copies only the commitment. Download exports the receipt, and reload restores that saved receipt rather than the original private input. Reset clears it. The source derives its key from the intent plus the current millisecond timestamp, and does not export the key or exact derivation timestamp. It provides no decryption or remote-verification control; the receipt alone is not a demonstrated recoverable compute handoff.