Posey

a project, moved as plain readable text

Code that travels by email, past the filters.

The problem it solves

Some machines you cannot push to. A parent's laptop. A work computer behind a corporate mail gateway. Git is not an option there, and the gateway strips attachments by type: .zip, .py, .exe, sometimes anything it doesn't recognise.

What every gateway lets through is a text file. So Posey writes the whole project as one, with a checksum for every file, and pairs it with an unpacker that needs nothing but Python. On the far side you save the attachment, run the unpacker, and the folder is back, every file verified.

What it does

Posey keeps a card per destination, a named place your code goes, and remembers what each one has received and at which version. So "does Mom have the latest Jigger?" is answered by looking at a card, and the next send can carry only what changed since.

Fonts, images and sounds can't ride as text, so they go as a real zip renamed .zip.txt in a second email. Lose that one and you lose fonts, not the app. On the receiving machine a small Receiver app installs each bundle with one click, starts and stops it, and keeps a journal of what arrived, so nobody on the far end ever opens a command line.

Since the demo was recorded, the last gap closed: a machine with no Python at all. A one-time setup script now rides along with the Receiver, installs Python for the current user without needing an administrator, and makes the desktop shortcut. It was used for real on 27 September, and the puzzle app it delivered has been in daily use since.

Demo three minutes, recorded against the real app

Posey 1.5.0 and the Posey Receiver. A send from this machine, then the install on the far one. Narration is done using AI. 3 min 13 s · 1280 × 720

Fair questions asked by people who watched the demo

What if the far machine has no Python?: The setup script travels with every Receiver kit as a .txt. Run it once and it finds or installs Python, unpacks the Receiver, and makes the shortcut.
What about the app's dependencies?: Each app's requirements.txt rides in the bundle and the Receiver installs it. The bundle also carries the Python version the app needs, and a machine that is too old gets the files but is not left with a half-broken install.
Is the bundle encrypted?: No. It is checksummed, not encrypted, and it rides your own mail account. The checksums catch what mail does to text, such as wrapped lines and lost indentation. Tampering is not the threat it was built against.
Do secrets go along for the ride?: No. Config files, .env files, keys and certificates are held back by name and listed, so sending one is a deliberate act.
How big can a project be?: Bundles warn at 5 MB and refuse at 25 MB, which is also where most mail providers stop. The limit has caught a demo video left in a project folder, which is the limit doing its job.
Can you roll back?: Every kit ever built stays in history. Any earlier one can be resent in one click, and each destination keeps its own record of what it has been sent.