# Two delivery forms, one core payload The release design has two delivery targets: 1. **Existing MiSTer:** a checked FAT-volume overlay, copied directly or installed over passwordless SSH. This is implemented by tools/release.py and tools/install_mister.py. 2. **Dedicated Coco 3 Plus card:** a bootable image containing the standard MiSTer system plus the same overlay, suitable for balenaEtcher. The image builder and first-boot qualification are a separate delivery step; no bootable Plus image is claimed by the core build or overlay packaging command. MiSTer Linux and its boot files reside on the microSD card. It is not sufficient to put a core RBF and games on a blank FAT32 card and rely on an onboard OS. [Mr. Fusion](https://github.com/MiSTer-devel/mr-fusion) is the existing starter system. Its compact image boots a small installer, expands/prepares the card, installs MiSTer and reboots. Its documented image-writing tools include Etcher. Using its existing release/system assets avoids building a new Linux distribution. Its upstream full image builder currently uses a privileged Linux/Docker flow; that is distinct from our native Windows FPGA/tool/ROM build. For a dedicated release, pin the Mr. Fusion and MiSTer system versions and checksums, preserve their licenses, then integrate the already verified Plus overlay into the image's installation payload. Confirm exactly when the installer consumes/deletes its staging partition before injecting files: copying arbitrary assets beside Scripts is not a documented automatic full-root overlay mechanism. Include only approved software-library content, no owner credentials, SSH host keys or personal device configuration. Choose a dedicated startup configuration deliberately while retaining a way back to MENU. Qualification must include flashing a spare card, first-boot expansion on the actual DE10-Nano, offline/online behavior, automatic SSC ROM availability when legitimately supplied, readable/writable disks, saved settings and a cold power cycle. Never replace an existing owner's primary card as an incidental test. The same core/ROM/file manifest should identify both distribution forms so they cannot drift into different products.