“Works offline” is not a product.

Plenty of software still runs if you yank the ethernet. Most of it was designed for the other case: an account, a CDN, a license check, a friendly “we’ll try again when you’re back online.”

decomm is for the machine that is not coming back online. A personal sandbox. A home server that should stay quiet. Two computers and a USB stick. An offline creative box. The interesting tools are the ones that only make sense once the cable is out.

You still need a face for people when Gravatar cannot answer. You still need to know the folder on the stick is the folder you packed. You still want HTTPS on a LAN that Let’s Encrypt will never see. You still want a log you can trust next month.

Why Deno

One runtime. TypeScript without a ceremony. Permissions you can read off the command line. A folder you can copy. Init on a connected machine, then `--cached-only` on the far side.

Why carry-in, not an installer

An installer that phones home is a second internet. decomm tools are meant to leave the network in a folder: init (or a JSR install) while you have wifi, copy that folder onto the isolated box, run it there. If it cannot survive that trip, it is not a decomm tool.

Labs

Air-gapped rooms and secure labs can use this. They are a fit, not the narrator. The pitch is to a person with an isolated box.